Embedded Open Modular Architecture/EOMA68/EEPROM Data Format

From eLinux.org
< Embedded Open Modular Architecture‎ | EOMA68
Revision as of 16:59, 7 September 2016 by Jbn (talk | contribs) (Jbn moved page Embedded Open Modular Architecture/EOMA-68/EEPROM Data Format to Embedded Open Modular Architecture/EOMA68/EEPROM Data Format: Corrected "EOMA-68" name to "EOMA68".)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Purpose

assuming agreement on the DIDS layout, below is a proposed definition for the two pages we currently know we must have:

  • a device ID page
  • a device tree page


Goals

To standardize the process of identifying a chassis (or any hardware device, for that matter?) and the components/devices on the chassis which can not be discovered reliably through probing.


Proposal

Define two DIDS conforming pages, one for identification information and the other for device tree information, and assign them Page Identifiers (PID).


Implementation

  • Name: Device Identification
  • PID: 0x01

Page data layout

Byte(s)                         Value

====              ================

2                                       Device type (assigned centrally)
2                                       Device revision
4                                       Vendor ID (assigned centrally)
4                                       Product ID (vendor generated,
registered centrally)
N                                       Manufacturer cstring
N                                       Product cstring
N                                       Serial number cstring


* Name: Device tree
* PID: 0x02

Page data consists of a standard “dtb” blob as generated by a device tree
compiler (dtc) compliant with the Device Tree standard defined at
http://devicetree.org
Retrieved from "https://elinux.org/index.php?title=Embedded_Open_Modular_Architecture/EOMA68/EEPROM_Data_Format&oldid=418676"