hi...
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
aaron - looks good. did you manage to register on elinux.org? i put this straight here: http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68/EEPROM_Data_For...
On Tue, Nov 5, 2013 at 9:59 AM, Aaron J. Seigo aseigo@kde.org wrote:
hi...
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
-- Aaron J. Seigo
arm-netbook mailing list arm-netbook@lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook@files.phcomp.co.uk
On Wednesday, November 6, 2013 08:50:42 luke.leighton wrote:
aaron - looks good. did you manage to register on elinux.org?
yep :)
great to see the page for this up there; i’ll do some wikification of it when i get some down-time moments.
the next step will be to write something that can read/write said image files. we can then play around with that a bit and hopefully move this from theory to practice.
cheers.
On Wed, Nov 6, 2013 at 11:36 AM, Aaron J. Seigo aseigo@kde.org wrote:
On Wednesday, November 6, 2013 08:50:42 luke.leighton wrote:
aaron - looks good. did you manage to register on elinux.org?
yep :)
oh good! elinux.org on the ball, then.
great to see the page for this up there; i’ll do some wikification of it when i get some down-time moments.
the next step will be to write something that can read/write said image files. we can then play around with that a bit and hopefully move this from theory to practice.
awesome.
cheers.
-- Aaron J. Seigo
arm-netbook mailing list arm-netbook@lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook@files.phcomp.co.uk
arm-netbook@lists.phcomp.co.uk
-
Aaron J. Seigo -
luke.leighton