Hi Cindi,
This is using the SMBIOS and/or ACPI for fru topology information. The
"PRI like structure" only becomes intermediate data that then can be
walked by a common back end walker. All FRU information (serial number,
part number, etc...) is retrieved from (mostly) SMBIOS and then placed
into a PRI like structure for the topology to be generated.
There is no "firmware" generated PRI like entity, and we're not
proposing one. We're generating the x86 PRI only so we could reuse the
sun4pi walker (to generate the FMA topology). Otherwise we'd have to
come up with an entirely x86 specific data format and walker...
Does this make more sense?
thx,
-t
On 03/03/09 15:04, Cynthia McGuire wrote:
Tom Pothier wrote:
------------------------------------------------------------------------
_______________________________________________
fm-discuss mailing list
fm-discuss@opensolaris.org
While I'm happy to see some convergence between x86 and SPARC, this
project moves in the wrong direction. If I understand correctly, you
are adopting the SPARC PRI for modeling the FMA topology on x86. This
has been discussed before and it was decided that a better approach
for all Sun platforms is to move toward adopting SMBIOS. SMBIOS (plus
whatever you glean from ACPI) then becomes the source of FRU and other
FMA topology information for things like libtopo and fmd(1M).
Further, Sun needs to draft a SMBIOS standard for platform vendors
wishing to participate in fault management and diagnosis for their
platforms. Included in the standard should be the required records for
the Sun FMA. If a vendor conforms (including Sun SPARC), diagnosis
and FRU location and replacement is then guaranteed.
Cindi
_______________________________________________
fm-discuss mailing list
fm-discuss@opensolaris.org
