GET https://dev.normadoc.fr/products/ieee-iso-iec-15205-2000-ieee00002384-241119

Response
200 OK
IP
216.73.216.116
Profiled on
Token
7f62a1

Components

4 Twig Components
8 Render Count
10 ms Render Time
350.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		3 0.75ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		3 2.28ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.24ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		1 7.17ms

Render calls

ProductState App\Twig\Components\ProductState 350.0 MiB 0.37 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 9467
    #code: "IEEE00002384"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038287 {#7274
      date: 2025-06-27 17:31:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 32877
        #name: "IEEE/ISO/IEC 15205:2000"
        #slug: "ieee-iso-iec-15205-2000-ieee00002384-241119"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          An input/output expansion bus with a 32-or 64-bit width is described in this standard.The SBus is designed for systems requiring a small number of expansion ports.SBus Cards may be connected to a standard SBus Connector mounted on the motherreboard.SBus Devices may also be attached to the SBus directly on the system's motherreboard.The dimensions of the SBus Card are 83.8 mm by 146.7 mm,making the cards appropriate for small computer systems that make extensive use of highly integrated circuits.The SBus Cards are designed to be installed in a plane parallel to the system's motherreboard as mezzanine cards. They are designed to provide connections for devices external to the computer system through an exposed back panel.The form factor is useful in Futurebus+,VMEbus,desktop computers,and similar applications. The SBus has the capability of transferring data at rates up to 168 Mbytes/s,depending on the implementation options selected. SBus Cards may either serve as Masters on the bus,providing all virtual address information as well as the data to be transferred,or they may serve as Slaves on the bus,providing data transfer according to the require- ments of some other SBus Master.The SBus Master for a data transfer is selected by an arbitration process managed by the single SBus Controller on the SBus.The SBus Controller provides a virtual to physical ad- dress translation service.<br />\n
          \t\t\t\t<br />\n
          SBus is a high performance computer I/O interface for connecting integrated circuits and SBus Cards to a computer system motherreboard. This standard defines the mechanical, electrical, environmental, and protocol requirements for the design of SBus Cards and the computer system motherreboard that supports those cards.<br />\n
          Every SBus Card shall implement appropriate self-descriptive and initialization firmware using<br />\n
          FCode, which is similar to the Forth programming language. The details of this firmware standard are beyond the scope of this standard.1) In addition, other software interfaces may be used for communication with SBus Cards.<br />\n
          SBus is intended to provide a high performance I/O bus interface with a small mechanical form factor. The small size, high levels of integration, and low power usage of SBus Cards enable them to be used in laptop computers, compact desktop computers, and other applications requiring similar characteristics. SBus Cards are mounted in a plane parallel to the motherreboard of the computer system, allowing the computer system to have a low profile. SBus is not designed as a general purpose backplane bus.<br />\n
          SBus allows transfers to be in units of 8, 16, 32, or 64 bits. Burst transfers are allowed to further improve performance. SBus allows a number of SBus Master devices to arbitrate for access to the bus. The chosen SBus Master provides a 32-bit virtual address which the SBus Controller maps to the selection of the proper SBus Slave and the development of the 28-bit physical address for that Slave. The selected SBus Slave then performs the data transfers requested by the SBus Master. Simple SBus Cards may be designed to operate solely as Slaves on the SBus.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC 15205:2000 (IEEE Std 1496-1993) SBus -- Chip and Module Interconnect Bus"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @991173600 {#7318
      date: 2001-05-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15205"
    -bookCollection: ""
    -pageCount: 108
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#93007
  +product: App\Entity\Product\Product {#7310
    #id: 9467
    #code: "IEEE00002384"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038287 {#7274
      date: 2025-06-27 17:31:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 32877
        #name: "IEEE/ISO/IEC 15205:2000"
        #slug: "ieee-iso-iec-15205-2000-ieee00002384-241119"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          An input/output expansion bus with a 32-or 64-bit width is described in this standard.The SBus is designed for systems requiring a small number of expansion ports.SBus Cards may be connected to a standard SBus Connector mounted on the motherreboard.SBus Devices may also be attached to the SBus directly on the system's motherreboard.The dimensions of the SBus Card are 83.8 mm by 146.7 mm,making the cards appropriate for small computer systems that make extensive use of highly integrated circuits.The SBus Cards are designed to be installed in a plane parallel to the system's motherreboard as mezzanine cards. They are designed to provide connections for devices external to the computer system through an exposed back panel.The form factor is useful in Futurebus+,VMEbus,desktop computers,and similar applications. The SBus has the capability of transferring data at rates up to 168 Mbytes/s,depending on the implementation options selected. SBus Cards may either serve as Masters on the bus,providing all virtual address information as well as the data to be transferred,or they may serve as Slaves on the bus,providing data transfer according to the require- ments of some other SBus Master.The SBus Master for a data transfer is selected by an arbitration process managed by the single SBus Controller on the SBus.The SBus Controller provides a virtual to physical ad- dress translation service.<br />\n
          \t\t\t\t<br />\n
          SBus is a high performance computer I/O interface for connecting integrated circuits and SBus Cards to a computer system motherreboard. This standard defines the mechanical, electrical, environmental, and protocol requirements for the design of SBus Cards and the computer system motherreboard that supports those cards.<br />\n
          Every SBus Card shall implement appropriate self-descriptive and initialization firmware using<br />\n
          FCode, which is similar to the Forth programming language. The details of this firmware standard are beyond the scope of this standard.1) In addition, other software interfaces may be used for communication with SBus Cards.<br />\n
          SBus is intended to provide a high performance I/O bus interface with a small mechanical form factor. The small size, high levels of integration, and low power usage of SBus Cards enable them to be used in laptop computers, compact desktop computers, and other applications requiring similar characteristics. SBus Cards are mounted in a plane parallel to the motherreboard of the computer system, allowing the computer system to have a low profile. SBus is not designed as a general purpose backplane bus.<br />\n
          SBus allows transfers to be in units of 8, 16, 32, or 64 bits. Burst transfers are allowed to further improve performance. SBus allows a number of SBus Master devices to arbitrate for access to the bus. The chosen SBus Master provides a 32-bit virtual address which the SBus Controller maps to the selection of the proper SBus Slave and the development of the 28-bit physical address for that Slave. The selected SBus Slave then performs the data transfers requested by the SBus Master. Simple SBus Cards may be designed to operate solely as Slaves on the SBus.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC 15205:2000 (IEEE Std 1496-1993) SBus -- Chip and Module Interconnect Bus"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @991173600 {#7318
      date: 2001-05-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15205"
    -bookCollection: ""
    -pageCount: 108
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 350.0 MiB 0.24 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 9467
    #code: "IEEE00002384"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038287 {#7274
      date: 2025-06-27 17:31:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 32877
        #name: "IEEE/ISO/IEC 15205:2000"
        #slug: "ieee-iso-iec-15205-2000-ieee00002384-241119"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          An input/output expansion bus with a 32-or 64-bit width is described in this standard.The SBus is designed for systems requiring a small number of expansion ports.SBus Cards may be connected to a standard SBus Connector mounted on the motherreboard.SBus Devices may also be attached to the SBus directly on the system's motherreboard.The dimensions of the SBus Card are 83.8 mm by 146.7 mm,making the cards appropriate for small computer systems that make extensive use of highly integrated circuits.The SBus Cards are designed to be installed in a plane parallel to the system's motherreboard as mezzanine cards. They are designed to provide connections for devices external to the computer system through an exposed back panel.The form factor is useful in Futurebus+,VMEbus,desktop computers,and similar applications. The SBus has the capability of transferring data at rates up to 168 Mbytes/s,depending on the implementation options selected. SBus Cards may either serve as Masters on the bus,providing all virtual address information as well as the data to be transferred,or they may serve as Slaves on the bus,providing data transfer according to the require- ments of some other SBus Master.The SBus Master for a data transfer is selected by an arbitration process managed by the single SBus Controller on the SBus.The SBus Controller provides a virtual to physical ad- dress translation service.<br />\n
          \t\t\t\t<br />\n
          SBus is a high performance computer I/O interface for connecting integrated circuits and SBus Cards to a computer system motherreboard. This standard defines the mechanical, electrical, environmental, and protocol requirements for the design of SBus Cards and the computer system motherreboard that supports those cards.<br />\n
          Every SBus Card shall implement appropriate self-descriptive and initialization firmware using<br />\n
          FCode, which is similar to the Forth programming language. The details of this firmware standard are beyond the scope of this standard.1) In addition, other software interfaces may be used for communication with SBus Cards.<br />\n
          SBus is intended to provide a high performance I/O bus interface with a small mechanical form factor. The small size, high levels of integration, and low power usage of SBus Cards enable them to be used in laptop computers, compact desktop computers, and other applications requiring similar characteristics. SBus Cards are mounted in a plane parallel to the motherreboard of the computer system, allowing the computer system to have a low profile. SBus is not designed as a general purpose backplane bus.<br />\n
          SBus allows transfers to be in units of 8, 16, 32, or 64 bits. Burst transfers are allowed to further improve performance. SBus allows a number of SBus Master devices to arbitrate for access to the bus. The chosen SBus Master provides a 32-bit virtual address which the SBus Controller maps to the selection of the proper SBus Slave and the development of the 28-bit physical address for that Slave. The selected SBus Slave then performs the data transfers requested by the SBus Master. Simple SBus Cards may be designed to operate solely as Slaves on the SBus.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC 15205:2000 (IEEE Std 1496-1993) SBus -- Chip and Module Interconnect Bus"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @991173600 {#7318
      date: 2001-05-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15205"
    -bookCollection: ""
    -pageCount: 108
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93187
  +product: App\Entity\Product\Product {#7310
    #id: 9467
    #code: "IEEE00002384"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038287 {#7274
      date: 2025-06-27 17:31:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 32877
        #name: "IEEE/ISO/IEC 15205:2000"
        #slug: "ieee-iso-iec-15205-2000-ieee00002384-241119"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          An input/output expansion bus with a 32-or 64-bit width is described in this standard.The SBus is designed for systems requiring a small number of expansion ports.SBus Cards may be connected to a standard SBus Connector mounted on the motherreboard.SBus Devices may also be attached to the SBus directly on the system's motherreboard.The dimensions of the SBus Card are 83.8 mm by 146.7 mm,making the cards appropriate for small computer systems that make extensive use of highly integrated circuits.The SBus Cards are designed to be installed in a plane parallel to the system's motherreboard as mezzanine cards. They are designed to provide connections for devices external to the computer system through an exposed back panel.The form factor is useful in Futurebus+,VMEbus,desktop computers,and similar applications. The SBus has the capability of transferring data at rates up to 168 Mbytes/s,depending on the implementation options selected. SBus Cards may either serve as Masters on the bus,providing all virtual address information as well as the data to be transferred,or they may serve as Slaves on the bus,providing data transfer according to the require- ments of some other SBus Master.The SBus Master for a data transfer is selected by an arbitration process managed by the single SBus Controller on the SBus.The SBus Controller provides a virtual to physical ad- dress translation service.<br />\n
          \t\t\t\t<br />\n
          SBus is a high performance computer I/O interface for connecting integrated circuits and SBus Cards to a computer system motherreboard. This standard defines the mechanical, electrical, environmental, and protocol requirements for the design of SBus Cards and the computer system motherreboard that supports those cards.<br />\n
          Every SBus Card shall implement appropriate self-descriptive and initialization firmware using<br />\n
          FCode, which is similar to the Forth programming language. The details of this firmware standard are beyond the scope of this standard.1) In addition, other software interfaces may be used for communication with SBus Cards.<br />\n
          SBus is intended to provide a high performance I/O bus interface with a small mechanical form factor. The small size, high levels of integration, and low power usage of SBus Cards enable them to be used in laptop computers, compact desktop computers, and other applications requiring similar characteristics. SBus Cards are mounted in a plane parallel to the motherreboard of the computer system, allowing the computer system to have a low profile. SBus is not designed as a general purpose backplane bus.<br />\n
          SBus allows transfers to be in units of 8, 16, 32, or 64 bits. Burst transfers are allowed to further improve performance. SBus allows a number of SBus Master devices to arbitrate for access to the bus. The chosen SBus Master provides a 32-bit virtual address which the SBus Controller maps to the selection of the proper SBus Slave and the development of the 28-bit physical address for that Slave. The selected SBus Slave then performs the data transfers requested by the SBus Master. Simple SBus Cards may be designed to operate solely as Slaves on the SBus.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC 15205:2000 (IEEE Std 1496-1993) SBus -- Chip and Module Interconnect Bus"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @991173600 {#7318
      date: 2001-05-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15205"
    -bookCollection: ""
    -pageCount: 108
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 350.0 MiB 0.86 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 9467
    #code: "IEEE00002384"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038287 {#7274
      date: 2025-06-27 17:31:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 32877
        #name: "IEEE/ISO/IEC 15205:2000"
        #slug: "ieee-iso-iec-15205-2000-ieee00002384-241119"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          An input/output expansion bus with a 32-or 64-bit width is described in this standard.The SBus is designed for systems requiring a small number of expansion ports.SBus Cards may be connected to a standard SBus Connector mounted on the motherreboard.SBus Devices may also be attached to the SBus directly on the system's motherreboard.The dimensions of the SBus Card are 83.8 mm by 146.7 mm,making the cards appropriate for small computer systems that make extensive use of highly integrated circuits.The SBus Cards are designed to be installed in a plane parallel to the system's motherreboard as mezzanine cards. They are designed to provide connections for devices external to the computer system through an exposed back panel.The form factor is useful in Futurebus+,VMEbus,desktop computers,and similar applications. The SBus has the capability of transferring data at rates up to 168 Mbytes/s,depending on the implementation options selected. SBus Cards may either serve as Masters on the bus,providing all virtual address information as well as the data to be transferred,or they may serve as Slaves on the bus,providing data transfer according to the require- ments of some other SBus Master.The SBus Master for a data transfer is selected by an arbitration process managed by the single SBus Controller on the SBus.The SBus Controller provides a virtual to physical ad- dress translation service.<br />\n
          \t\t\t\t<br />\n
          SBus is a high performance computer I/O interface for connecting integrated circuits and SBus Cards to a computer system motherreboard. This standard defines the mechanical, electrical, environmental, and protocol requirements for the design of SBus Cards and the computer system motherreboard that supports those cards.<br />\n
          Every SBus Card shall implement appropriate self-descriptive and initialization firmware using<br />\n
          FCode, which is similar to the Forth programming language. The details of this firmware standard are beyond the scope of this standard.1) In addition, other software interfaces may be used for communication with SBus Cards.<br />\n
          SBus is intended to provide a high performance I/O bus interface with a small mechanical form factor. The small size, high levels of integration, and low power usage of SBus Cards enable them to be used in laptop computers, compact desktop computers, and other applications requiring similar characteristics. SBus Cards are mounted in a plane parallel to the motherreboard of the computer system, allowing the computer system to have a low profile. SBus is not designed as a general purpose backplane bus.<br />\n
          SBus allows transfers to be in units of 8, 16, 32, or 64 bits. Burst transfers are allowed to further improve performance. SBus allows a number of SBus Master devices to arbitrate for access to the bus. The chosen SBus Master provides a 32-bit virtual address which the SBus Controller maps to the selection of the proper SBus Slave and the development of the 28-bit physical address for that Slave. The selected SBus Slave then performs the data transfers requested by the SBus Master. Simple SBus Cards may be designed to operate solely as Slaves on the SBus.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC 15205:2000 (IEEE Std 1496-1993) SBus -- Chip and Module Interconnect Bus"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @991173600 {#7318
      date: 2001-05-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15205"
    -bookCollection: ""
    -pageCount: 108
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93262
  +product: App\Entity\Product\Product {#7310
    #id: 9467
    #code: "IEEE00002384"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038287 {#7274
      date: 2025-06-27 17:31:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 32877
        #name: "IEEE/ISO/IEC 15205:2000"
        #slug: "ieee-iso-iec-15205-2000-ieee00002384-241119"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          An input/output expansion bus with a 32-or 64-bit width is described in this standard.The SBus is designed for systems requiring a small number of expansion ports.SBus Cards may be connected to a standard SBus Connector mounted on the motherreboard.SBus Devices may also be attached to the SBus directly on the system's motherreboard.The dimensions of the SBus Card are 83.8 mm by 146.7 mm,making the cards appropriate for small computer systems that make extensive use of highly integrated circuits.The SBus Cards are designed to be installed in a plane parallel to the system's motherreboard as mezzanine cards. They are designed to provide connections for devices external to the computer system through an exposed back panel.The form factor is useful in Futurebus+,VMEbus,desktop computers,and similar applications. The SBus has the capability of transferring data at rates up to 168 Mbytes/s,depending on the implementation options selected. SBus Cards may either serve as Masters on the bus,providing all virtual address information as well as the data to be transferred,or they may serve as Slaves on the bus,providing data transfer according to the require- ments of some other SBus Master.The SBus Master for a data transfer is selected by an arbitration process managed by the single SBus Controller on the SBus.The SBus Controller provides a virtual to physical ad- dress translation service.<br />\n
          \t\t\t\t<br />\n
          SBus is a high performance computer I/O interface for connecting integrated circuits and SBus Cards to a computer system motherreboard. This standard defines the mechanical, electrical, environmental, and protocol requirements for the design of SBus Cards and the computer system motherreboard that supports those cards.<br />\n
          Every SBus Card shall implement appropriate self-descriptive and initialization firmware using<br />\n
          FCode, which is similar to the Forth programming language. The details of this firmware standard are beyond the scope of this standard.1) In addition, other software interfaces may be used for communication with SBus Cards.<br />\n
          SBus is intended to provide a high performance I/O bus interface with a small mechanical form factor. The small size, high levels of integration, and low power usage of SBus Cards enable them to be used in laptop computers, compact desktop computers, and other applications requiring similar characteristics. SBus Cards are mounted in a plane parallel to the motherreboard of the computer system, allowing the computer system to have a low profile. SBus is not designed as a general purpose backplane bus.<br />\n
          SBus allows transfers to be in units of 8, 16, 32, or 64 bits. Burst transfers are allowed to further improve performance. SBus allows a number of SBus Master devices to arbitrate for access to the bus. The chosen SBus Master provides a 32-bit virtual address which the SBus Controller maps to the selection of the proper SBus Slave and the development of the 28-bit physical address for that Slave. The selected SBus Slave then performs the data transfers requested by the SBus Master. Simple SBus Cards may be designed to operate solely as Slaves on the SBus.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC 15205:2000 (IEEE Std 1496-1993) SBus -- Chip and Module Interconnect Bus"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @991173600 {#7318
      date: 2001-05-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15205"
    -bookCollection: ""
    -pageCount: 108
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 350.0 MiB 0.20 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 9467
    #code: "IEEE00002384"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038287 {#7274
      date: 2025-06-27 17:31:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 32877
        #name: "IEEE/ISO/IEC 15205:2000"
        #slug: "ieee-iso-iec-15205-2000-ieee00002384-241119"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          An input/output expansion bus with a 32-or 64-bit width is described in this standard.The SBus is designed for systems requiring a small number of expansion ports.SBus Cards may be connected to a standard SBus Connector mounted on the motherreboard.SBus Devices may also be attached to the SBus directly on the system's motherreboard.The dimensions of the SBus Card are 83.8 mm by 146.7 mm,making the cards appropriate for small computer systems that make extensive use of highly integrated circuits.The SBus Cards are designed to be installed in a plane parallel to the system's motherreboard as mezzanine cards. They are designed to provide connections for devices external to the computer system through an exposed back panel.The form factor is useful in Futurebus+,VMEbus,desktop computers,and similar applications. The SBus has the capability of transferring data at rates up to 168 Mbytes/s,depending on the implementation options selected. SBus Cards may either serve as Masters on the bus,providing all virtual address information as well as the data to be transferred,or they may serve as Slaves on the bus,providing data transfer according to the require- ments of some other SBus Master.The SBus Master for a data transfer is selected by an arbitration process managed by the single SBus Controller on the SBus.The SBus Controller provides a virtual to physical ad- dress translation service.<br />\n
          \t\t\t\t<br />\n
          SBus is a high performance computer I/O interface for connecting integrated circuits and SBus Cards to a computer system motherreboard. This standard defines the mechanical, electrical, environmental, and protocol requirements for the design of SBus Cards and the computer system motherreboard that supports those cards.<br />\n
          Every SBus Card shall implement appropriate self-descriptive and initialization firmware using<br />\n
          FCode, which is similar to the Forth programming language. The details of this firmware standard are beyond the scope of this standard.1) In addition, other software interfaces may be used for communication with SBus Cards.<br />\n
          SBus is intended to provide a high performance I/O bus interface with a small mechanical form factor. The small size, high levels of integration, and low power usage of SBus Cards enable them to be used in laptop computers, compact desktop computers, and other applications requiring similar characteristics. SBus Cards are mounted in a plane parallel to the motherreboard of the computer system, allowing the computer system to have a low profile. SBus is not designed as a general purpose backplane bus.<br />\n
          SBus allows transfers to be in units of 8, 16, 32, or 64 bits. Burst transfers are allowed to further improve performance. SBus allows a number of SBus Master devices to arbitrate for access to the bus. The chosen SBus Master provides a 32-bit virtual address which the SBus Controller maps to the selection of the proper SBus Slave and the development of the 28-bit physical address for that Slave. The selected SBus Slave then performs the data transfers requested by the SBus Master. Simple SBus Cards may be designed to operate solely as Slaves on the SBus.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC 15205:2000 (IEEE Std 1496-1993) SBus -- Chip and Module Interconnect Bus"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @991173600 {#7318
      date: 2001-05-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15205"
    -bookCollection: ""
    -pageCount: 108
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100215
  +product: App\Entity\Product\Product {#7310
    #id: 9467
    #code: "IEEE00002384"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038287 {#7274
      date: 2025-06-27 17:31:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 32877
        #name: "IEEE/ISO/IEC 15205:2000"
        #slug: "ieee-iso-iec-15205-2000-ieee00002384-241119"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          An input/output expansion bus with a 32-or 64-bit width is described in this standard.The SBus is designed for systems requiring a small number of expansion ports.SBus Cards may be connected to a standard SBus Connector mounted on the motherreboard.SBus Devices may also be attached to the SBus directly on the system's motherreboard.The dimensions of the SBus Card are 83.8 mm by 146.7 mm,making the cards appropriate for small computer systems that make extensive use of highly integrated circuits.The SBus Cards are designed to be installed in a plane parallel to the system's motherreboard as mezzanine cards. They are designed to provide connections for devices external to the computer system through an exposed back panel.The form factor is useful in Futurebus+,VMEbus,desktop computers,and similar applications. The SBus has the capability of transferring data at rates up to 168 Mbytes/s,depending on the implementation options selected. SBus Cards may either serve as Masters on the bus,providing all virtual address information as well as the data to be transferred,or they may serve as Slaves on the bus,providing data transfer according to the require- ments of some other SBus Master.The SBus Master for a data transfer is selected by an arbitration process managed by the single SBus Controller on the SBus.The SBus Controller provides a virtual to physical ad- dress translation service.<br />\n
          \t\t\t\t<br />\n
          SBus is a high performance computer I/O interface for connecting integrated circuits and SBus Cards to a computer system motherreboard. This standard defines the mechanical, electrical, environmental, and protocol requirements for the design of SBus Cards and the computer system motherreboard that supports those cards.<br />\n
          Every SBus Card shall implement appropriate self-descriptive and initialization firmware using<br />\n
          FCode, which is similar to the Forth programming language. The details of this firmware standard are beyond the scope of this standard.1) In addition, other software interfaces may be used for communication with SBus Cards.<br />\n
          SBus is intended to provide a high performance I/O bus interface with a small mechanical form factor. The small size, high levels of integration, and low power usage of SBus Cards enable them to be used in laptop computers, compact desktop computers, and other applications requiring similar characteristics. SBus Cards are mounted in a plane parallel to the motherreboard of the computer system, allowing the computer system to have a low profile. SBus is not designed as a general purpose backplane bus.<br />\n
          SBus allows transfers to be in units of 8, 16, 32, or 64 bits. Burst transfers are allowed to further improve performance. SBus allows a number of SBus Master devices to arbitrate for access to the bus. The chosen SBus Master provides a 32-bit virtual address which the SBus Controller maps to the selection of the proper SBus Slave and the development of the 28-bit physical address for that Slave. The selected SBus Slave then performs the data transfers requested by the SBus Master. Simple SBus Cards may be designed to operate solely as Slaves on the SBus.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC 15205:2000 (IEEE Std 1496-1993) SBus -- Chip and Module Interconnect Bus"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @991173600 {#7318
      date: 2001-05-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15205"
    -bookCollection: ""
    -pageCount: 108
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 350.0 MiB 0.74 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 9467
    #code: "IEEE00002384"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038287 {#7274
      date: 2025-06-27 17:31:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 32877
        #name: "IEEE/ISO/IEC 15205:2000"
        #slug: "ieee-iso-iec-15205-2000-ieee00002384-241119"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          An input/output expansion bus with a 32-or 64-bit width is described in this standard.The SBus is designed for systems requiring a small number of expansion ports.SBus Cards may be connected to a standard SBus Connector mounted on the motherreboard.SBus Devices may also be attached to the SBus directly on the system's motherreboard.The dimensions of the SBus Card are 83.8 mm by 146.7 mm,making the cards appropriate for small computer systems that make extensive use of highly integrated circuits.The SBus Cards are designed to be installed in a plane parallel to the system's motherreboard as mezzanine cards. They are designed to provide connections for devices external to the computer system through an exposed back panel.The form factor is useful in Futurebus+,VMEbus,desktop computers,and similar applications. The SBus has the capability of transferring data at rates up to 168 Mbytes/s,depending on the implementation options selected. SBus Cards may either serve as Masters on the bus,providing all virtual address information as well as the data to be transferred,or they may serve as Slaves on the bus,providing data transfer according to the require- ments of some other SBus Master.The SBus Master for a data transfer is selected by an arbitration process managed by the single SBus Controller on the SBus.The SBus Controller provides a virtual to physical ad- dress translation service.<br />\n
          \t\t\t\t<br />\n
          SBus is a high performance computer I/O interface for connecting integrated circuits and SBus Cards to a computer system motherreboard. This standard defines the mechanical, electrical, environmental, and protocol requirements for the design of SBus Cards and the computer system motherreboard that supports those cards.<br />\n
          Every SBus Card shall implement appropriate self-descriptive and initialization firmware using<br />\n
          FCode, which is similar to the Forth programming language. The details of this firmware standard are beyond the scope of this standard.1) In addition, other software interfaces may be used for communication with SBus Cards.<br />\n
          SBus is intended to provide a high performance I/O bus interface with a small mechanical form factor. The small size, high levels of integration, and low power usage of SBus Cards enable them to be used in laptop computers, compact desktop computers, and other applications requiring similar characteristics. SBus Cards are mounted in a plane parallel to the motherreboard of the computer system, allowing the computer system to have a low profile. SBus is not designed as a general purpose backplane bus.<br />\n
          SBus allows transfers to be in units of 8, 16, 32, or 64 bits. Burst transfers are allowed to further improve performance. SBus allows a number of SBus Master devices to arbitrate for access to the bus. The chosen SBus Master provides a 32-bit virtual address which the SBus Controller maps to the selection of the proper SBus Slave and the development of the 28-bit physical address for that Slave. The selected SBus Slave then performs the data transfers requested by the SBus Master. Simple SBus Cards may be designed to operate solely as Slaves on the SBus.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC 15205:2000 (IEEE Std 1496-1993) SBus -- Chip and Module Interconnect Bus"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @991173600 {#7318
      date: 2001-05-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15205"
    -bookCollection: ""
    -pageCount: 108
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100299
  +product: App\Entity\Product\Product {#7310
    #id: 9467
    #code: "IEEE00002384"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038287 {#7274
      date: 2025-06-27 17:31:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 32877
        #name: "IEEE/ISO/IEC 15205:2000"
        #slug: "ieee-iso-iec-15205-2000-ieee00002384-241119"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          An input/output expansion bus with a 32-or 64-bit width is described in this standard.The SBus is designed for systems requiring a small number of expansion ports.SBus Cards may be connected to a standard SBus Connector mounted on the motherreboard.SBus Devices may also be attached to the SBus directly on the system's motherreboard.The dimensions of the SBus Card are 83.8 mm by 146.7 mm,making the cards appropriate for small computer systems that make extensive use of highly integrated circuits.The SBus Cards are designed to be installed in a plane parallel to the system's motherreboard as mezzanine cards. They are designed to provide connections for devices external to the computer system through an exposed back panel.The form factor is useful in Futurebus+,VMEbus,desktop computers,and similar applications. The SBus has the capability of transferring data at rates up to 168 Mbytes/s,depending on the implementation options selected. SBus Cards may either serve as Masters on the bus,providing all virtual address information as well as the data to be transferred,or they may serve as Slaves on the bus,providing data transfer according to the require- ments of some other SBus Master.The SBus Master for a data transfer is selected by an arbitration process managed by the single SBus Controller on the SBus.The SBus Controller provides a virtual to physical ad- dress translation service.<br />\n
          \t\t\t\t<br />\n
          SBus is a high performance computer I/O interface for connecting integrated circuits and SBus Cards to a computer system motherreboard. This standard defines the mechanical, electrical, environmental, and protocol requirements for the design of SBus Cards and the computer system motherreboard that supports those cards.<br />\n
          Every SBus Card shall implement appropriate self-descriptive and initialization firmware using<br />\n
          FCode, which is similar to the Forth programming language. The details of this firmware standard are beyond the scope of this standard.1) In addition, other software interfaces may be used for communication with SBus Cards.<br />\n
          SBus is intended to provide a high performance I/O bus interface with a small mechanical form factor. The small size, high levels of integration, and low power usage of SBus Cards enable them to be used in laptop computers, compact desktop computers, and other applications requiring similar characteristics. SBus Cards are mounted in a plane parallel to the motherreboard of the computer system, allowing the computer system to have a low profile. SBus is not designed as a general purpose backplane bus.<br />\n
          SBus allows transfers to be in units of 8, 16, 32, or 64 bits. Burst transfers are allowed to further improve performance. SBus allows a number of SBus Master devices to arbitrate for access to the bus. The chosen SBus Master provides a 32-bit virtual address which the SBus Controller maps to the selection of the proper SBus Slave and the development of the 28-bit physical address for that Slave. The selected SBus Slave then performs the data transfers requested by the SBus Master. Simple SBus Cards may be designed to operate solely as Slaves on the SBus.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC 15205:2000 (IEEE Std 1496-1993) SBus -- Chip and Module Interconnect Bus"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @991173600 {#7318
      date: 2001-05-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15205"
    -bookCollection: ""
    -pageCount: 108
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 350.0 MiB 7.17 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121553
    #id: 9248
    #code: "IEEE00001932"
    #attributes: Doctrine\ORM\PersistentCollection {#121536 …}
    #variants: Doctrine\ORM\PersistentCollection {#121534 …}
    #options: Doctrine\ORM\PersistentCollection {#121529 …}
    #associations: Doctrine\ORM\PersistentCollection {#121531 …}
    #createdAt: DateTime @1751038096 {#121526
      date: 2025-06-27 17:28:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#121519
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121647
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121553}
        #id: 32001
        #name: "IEEE 1275:1994"
        #slug: "ieee-1275-1994-ieee00001932-240900"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Firmware is the read-only-memory (ROM)-based software that controls a computer between the time it is turned on and the time the primary operating system takes control of the machine. Open Firmware provides the following: a mechanism for loading and executing programs (such as operating systems) from disks, tapes, network interfaces, and other devices; an ISA-independent method for identifying devices plugged in to expansion buses and for providing firmware and diagnostics drivers for these devices; an extensible and programmable command language based on the Forth programming language; methods for managing user-configurable options stored in nonvolatile memory; a call back interface allowing other programs to make use of Open Firmware services; and debugging tools for hardware, firmware, firmware drivers, and system software.<br />\n
          \t\t\t\t<br />\n
          This document describes a software architecture for the firmware that controls a computer before the operating system has begun execution. Typically, firmware is stored in read-only memory (ROM) or programmable read-only memory (PROM), so that it may be executed immediately after the computer is turned on.<br />\n
          The main jobs of the firmware are to test the machine hardware and to boot the operating system, usually from a mass storage device or a network. The operating system may also require other services from the firmware. Finally, firmware often provides some support for interactive hardware and software debugging. In addition to the main operating system, other programs, such as diagnostic operating systems, may utilize firmware services. This standard uses OpenBoot PROM Architecture Specification [B6]1 as a starting point, and is bus, vendor, operating system (OS), and instruction-set-architecture (ISA)-independent. Supplements (numbered 1275. x) include specifications for this standard’s application to particular ISAs and buses.<br />\n
          This document specifies firmware that controls the operation of a computer system before the primary operating system has taken control of the machine. The material specified includes facilities for determining the hardware configuration; testing, identification, and use of plug-in devices prior to primary OS control; reporting the hardware configuration to the operating system; the user interface for controlling these operations; and debugging facilities for hardware and system software.<br />\n
          Additional introductory material can be found in annex F.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Boot (Initialization Configuration) Firmware: Core Requirements and Practices"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121545 …}
    #channels: Doctrine\ORM\PersistentCollection {#121538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121555 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121512
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121561
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @783298800 {#121532
      date: 1994-10-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @957132000 {#121513
      date: 2000-05-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1275"
    -bookCollection: ""
    -pageCount: 262
    -documents: Doctrine\ORM\PersistentCollection {#121551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121549 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#121609
  +product: App\Entity\Product\Product {#121553
    #id: 9248
    #code: "IEEE00001932"
    #attributes: Doctrine\ORM\PersistentCollection {#121536 …}
    #variants: Doctrine\ORM\PersistentCollection {#121534 …}
    #options: Doctrine\ORM\PersistentCollection {#121529 …}
    #associations: Doctrine\ORM\PersistentCollection {#121531 …}
    #createdAt: DateTime @1751038096 {#121526
      date: 2025-06-27 17:28:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#121519
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121647
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121553}
        #id: 32001
        #name: "IEEE 1275:1994"
        #slug: "ieee-1275-1994-ieee00001932-240900"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Firmware is the read-only-memory (ROM)-based software that controls a computer between the time it is turned on and the time the primary operating system takes control of the machine. Open Firmware provides the following: a mechanism for loading and executing programs (such as operating systems) from disks, tapes, network interfaces, and other devices; an ISA-independent method for identifying devices plugged in to expansion buses and for providing firmware and diagnostics drivers for these devices; an extensible and programmable command language based on the Forth programming language; methods for managing user-configurable options stored in nonvolatile memory; a call back interface allowing other programs to make use of Open Firmware services; and debugging tools for hardware, firmware, firmware drivers, and system software.<br />\n
          \t\t\t\t<br />\n
          This document describes a software architecture for the firmware that controls a computer before the operating system has begun execution. Typically, firmware is stored in read-only memory (ROM) or programmable read-only memory (PROM), so that it may be executed immediately after the computer is turned on.<br />\n
          The main jobs of the firmware are to test the machine hardware and to boot the operating system, usually from a mass storage device or a network. The operating system may also require other services from the firmware. Finally, firmware often provides some support for interactive hardware and software debugging. In addition to the main operating system, other programs, such as diagnostic operating systems, may utilize firmware services. This standard uses OpenBoot PROM Architecture Specification [B6]1 as a starting point, and is bus, vendor, operating system (OS), and instruction-set-architecture (ISA)-independent. Supplements (numbered 1275. x) include specifications for this standard’s application to particular ISAs and buses.<br />\n
          This document specifies firmware that controls the operation of a computer system before the primary operating system has taken control of the machine. The material specified includes facilities for determining the hardware configuration; testing, identification, and use of plug-in devices prior to primary OS control; reporting the hardware configuration to the operating system; the user interface for controlling these operations; and debugging facilities for hardware and system software.<br />\n
          Additional introductory material can be found in annex F.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Boot (Initialization Configuration) Firmware: Core Requirements and Practices"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121545 …}
    #channels: Doctrine\ORM\PersistentCollection {#121538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121555 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121512
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121561
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @783298800 {#121532
      date: 1994-10-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @957132000 {#121513
      date: 2000-05-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1275"
    -bookCollection: ""
    -pageCount: 262
    -documents: Doctrine\ORM\PersistentCollection {#121551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121549 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}
ProductState App\Twig\Components\ProductState 350.0 MiB 0.19 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121553
    #id: 9248
    #code: "IEEE00001932"
    #attributes: Doctrine\ORM\PersistentCollection {#121536 …}
    #variants: Doctrine\ORM\PersistentCollection {#121534 …}
    #options: Doctrine\ORM\PersistentCollection {#121529 …}
    #associations: Doctrine\ORM\PersistentCollection {#121531 …}
    #createdAt: DateTime @1751038096 {#121526
      date: 2025-06-27 17:28:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#121519
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121647
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121553}
        #id: 32001
        #name: "IEEE 1275:1994"
        #slug: "ieee-1275-1994-ieee00001932-240900"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Firmware is the read-only-memory (ROM)-based software that controls a computer between the time it is turned on and the time the primary operating system takes control of the machine. Open Firmware provides the following: a mechanism for loading and executing programs (such as operating systems) from disks, tapes, network interfaces, and other devices; an ISA-independent method for identifying devices plugged in to expansion buses and for providing firmware and diagnostics drivers for these devices; an extensible and programmable command language based on the Forth programming language; methods for managing user-configurable options stored in nonvolatile memory; a call back interface allowing other programs to make use of Open Firmware services; and debugging tools for hardware, firmware, firmware drivers, and system software.<br />\n
          \t\t\t\t<br />\n
          This document describes a software architecture for the firmware that controls a computer before the operating system has begun execution. Typically, firmware is stored in read-only memory (ROM) or programmable read-only memory (PROM), so that it may be executed immediately after the computer is turned on.<br />\n
          The main jobs of the firmware are to test the machine hardware and to boot the operating system, usually from a mass storage device or a network. The operating system may also require other services from the firmware. Finally, firmware often provides some support for interactive hardware and software debugging. In addition to the main operating system, other programs, such as diagnostic operating systems, may utilize firmware services. This standard uses OpenBoot PROM Architecture Specification [B6]1 as a starting point, and is bus, vendor, operating system (OS), and instruction-set-architecture (ISA)-independent. Supplements (numbered 1275. x) include specifications for this standard’s application to particular ISAs and buses.<br />\n
          This document specifies firmware that controls the operation of a computer system before the primary operating system has taken control of the machine. The material specified includes facilities for determining the hardware configuration; testing, identification, and use of plug-in devices prior to primary OS control; reporting the hardware configuration to the operating system; the user interface for controlling these operations; and debugging facilities for hardware and system software.<br />\n
          Additional introductory material can be found in annex F.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Boot (Initialization Configuration) Firmware: Core Requirements and Practices"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121545 …}
    #channels: Doctrine\ORM\PersistentCollection {#121538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121555 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121512
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121561
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @783298800 {#121532
      date: 1994-10-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @957132000 {#121513
      date: 2000-05-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1275"
    -bookCollection: ""
    -pageCount: 262
    -documents: Doctrine\ORM\PersistentCollection {#121551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121549 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#121649
  +product: App\Entity\Product\Product {#121553
    #id: 9248
    #code: "IEEE00001932"
    #attributes: Doctrine\ORM\PersistentCollection {#121536 …}
    #variants: Doctrine\ORM\PersistentCollection {#121534 …}
    #options: Doctrine\ORM\PersistentCollection {#121529 …}
    #associations: Doctrine\ORM\PersistentCollection {#121531 …}
    #createdAt: DateTime @1751038096 {#121526
      date: 2025-06-27 17:28:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#121519
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121647
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121553}
        #id: 32001
        #name: "IEEE 1275:1994"
        #slug: "ieee-1275-1994-ieee00001932-240900"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Firmware is the read-only-memory (ROM)-based software that controls a computer between the time it is turned on and the time the primary operating system takes control of the machine. Open Firmware provides the following: a mechanism for loading and executing programs (such as operating systems) from disks, tapes, network interfaces, and other devices; an ISA-independent method for identifying devices plugged in to expansion buses and for providing firmware and diagnostics drivers for these devices; an extensible and programmable command language based on the Forth programming language; methods for managing user-configurable options stored in nonvolatile memory; a call back interface allowing other programs to make use of Open Firmware services; and debugging tools for hardware, firmware, firmware drivers, and system software.<br />\n
          \t\t\t\t<br />\n
          This document describes a software architecture for the firmware that controls a computer before the operating system has begun execution. Typically, firmware is stored in read-only memory (ROM) or programmable read-only memory (PROM), so that it may be executed immediately after the computer is turned on.<br />\n
          The main jobs of the firmware are to test the machine hardware and to boot the operating system, usually from a mass storage device or a network. The operating system may also require other services from the firmware. Finally, firmware often provides some support for interactive hardware and software debugging. In addition to the main operating system, other programs, such as diagnostic operating systems, may utilize firmware services. This standard uses OpenBoot PROM Architecture Specification [B6]1 as a starting point, and is bus, vendor, operating system (OS), and instruction-set-architecture (ISA)-independent. Supplements (numbered 1275. x) include specifications for this standard’s application to particular ISAs and buses.<br />\n
          This document specifies firmware that controls the operation of a computer system before the primary operating system has taken control of the machine. The material specified includes facilities for determining the hardware configuration; testing, identification, and use of plug-in devices prior to primary OS control; reporting the hardware configuration to the operating system; the user interface for controlling these operations; and debugging facilities for hardware and system software.<br />\n
          Additional introductory material can be found in annex F.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Boot (Initialization Configuration) Firmware: Core Requirements and Practices"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121545 …}
    #channels: Doctrine\ORM\PersistentCollection {#121538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121555 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121512
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121561
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @783298800 {#121532
      date: 1994-10-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @957132000 {#121513
      date: 2000-05-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1275"
    -bookCollection: ""
    -pageCount: 262
    -documents: Doctrine\ORM\PersistentCollection {#121551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121549 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 350.0 MiB 0.69 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121553
    #id: 9248
    #code: "IEEE00001932"
    #attributes: Doctrine\ORM\PersistentCollection {#121536 …}
    #variants: Doctrine\ORM\PersistentCollection {#121534 …}
    #options: Doctrine\ORM\PersistentCollection {#121529 …}
    #associations: Doctrine\ORM\PersistentCollection {#121531 …}
    #createdAt: DateTime @1751038096 {#121526
      date: 2025-06-27 17:28:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#121519
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121647
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121553}
        #id: 32001
        #name: "IEEE 1275:1994"
        #slug: "ieee-1275-1994-ieee00001932-240900"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Firmware is the read-only-memory (ROM)-based software that controls a computer between the time it is turned on and the time the primary operating system takes control of the machine. Open Firmware provides the following: a mechanism for loading and executing programs (such as operating systems) from disks, tapes, network interfaces, and other devices; an ISA-independent method for identifying devices plugged in to expansion buses and for providing firmware and diagnostics drivers for these devices; an extensible and programmable command language based on the Forth programming language; methods for managing user-configurable options stored in nonvolatile memory; a call back interface allowing other programs to make use of Open Firmware services; and debugging tools for hardware, firmware, firmware drivers, and system software.<br />\n
          \t\t\t\t<br />\n
          This document describes a software architecture for the firmware that controls a computer before the operating system has begun execution. Typically, firmware is stored in read-only memory (ROM) or programmable read-only memory (PROM), so that it may be executed immediately after the computer is turned on.<br />\n
          The main jobs of the firmware are to test the machine hardware and to boot the operating system, usually from a mass storage device or a network. The operating system may also require other services from the firmware. Finally, firmware often provides some support for interactive hardware and software debugging. In addition to the main operating system, other programs, such as diagnostic operating systems, may utilize firmware services. This standard uses OpenBoot PROM Architecture Specification [B6]1 as a starting point, and is bus, vendor, operating system (OS), and instruction-set-architecture (ISA)-independent. Supplements (numbered 1275. x) include specifications for this standard’s application to particular ISAs and buses.<br />\n
          This document specifies firmware that controls the operation of a computer system before the primary operating system has taken control of the machine. The material specified includes facilities for determining the hardware configuration; testing, identification, and use of plug-in devices prior to primary OS control; reporting the hardware configuration to the operating system; the user interface for controlling these operations; and debugging facilities for hardware and system software.<br />\n
          Additional introductory material can be found in annex F.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Boot (Initialization Configuration) Firmware: Core Requirements and Practices"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121545 …}
    #channels: Doctrine\ORM\PersistentCollection {#121538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121555 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121512
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121561
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @783298800 {#121532
      date: 1994-10-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @957132000 {#121513
      date: 2000-05-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1275"
    -bookCollection: ""
    -pageCount: 262
    -documents: Doctrine\ORM\PersistentCollection {#121551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121549 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#121726
  +product: App\Entity\Product\Product {#121553
    #id: 9248
    #code: "IEEE00001932"
    #attributes: Doctrine\ORM\PersistentCollection {#121536 …}
    #variants: Doctrine\ORM\PersistentCollection {#121534 …}
    #options: Doctrine\ORM\PersistentCollection {#121529 …}
    #associations: Doctrine\ORM\PersistentCollection {#121531 …}
    #createdAt: DateTime @1751038096 {#121526
      date: 2025-06-27 17:28:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#121519
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121647
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121553}
        #id: 32001
        #name: "IEEE 1275:1994"
        #slug: "ieee-1275-1994-ieee00001932-240900"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Firmware is the read-only-memory (ROM)-based software that controls a computer between the time it is turned on and the time the primary operating system takes control of the machine. Open Firmware provides the following: a mechanism for loading and executing programs (such as operating systems) from disks, tapes, network interfaces, and other devices; an ISA-independent method for identifying devices plugged in to expansion buses and for providing firmware and diagnostics drivers for these devices; an extensible and programmable command language based on the Forth programming language; methods for managing user-configurable options stored in nonvolatile memory; a call back interface allowing other programs to make use of Open Firmware services; and debugging tools for hardware, firmware, firmware drivers, and system software.<br />\n
          \t\t\t\t<br />\n
          This document describes a software architecture for the firmware that controls a computer before the operating system has begun execution. Typically, firmware is stored in read-only memory (ROM) or programmable read-only memory (PROM), so that it may be executed immediately after the computer is turned on.<br />\n
          The main jobs of the firmware are to test the machine hardware and to boot the operating system, usually from a mass storage device or a network. The operating system may also require other services from the firmware. Finally, firmware often provides some support for interactive hardware and software debugging. In addition to the main operating system, other programs, such as diagnostic operating systems, may utilize firmware services. This standard uses OpenBoot PROM Architecture Specification [B6]1 as a starting point, and is bus, vendor, operating system (OS), and instruction-set-architecture (ISA)-independent. Supplements (numbered 1275. x) include specifications for this standard’s application to particular ISAs and buses.<br />\n
          This document specifies firmware that controls the operation of a computer system before the primary operating system has taken control of the machine. The material specified includes facilities for determining the hardware configuration; testing, identification, and use of plug-in devices prior to primary OS control; reporting the hardware configuration to the operating system; the user interface for controlling these operations; and debugging facilities for hardware and system software.<br />\n
          Additional introductory material can be found in annex F.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Boot (Initialization Configuration) Firmware: Core Requirements and Practices"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121545 …}
    #channels: Doctrine\ORM\PersistentCollection {#121538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121555 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121512
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121561
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @783298800 {#121532
      date: 1994-10-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @957132000 {#121513
      date: 2000-05-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1275"
    -bookCollection: ""
    -pageCount: 262
    -documents: Doctrine\ORM\PersistentCollection {#121551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121549 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}