On Tue, 2009-03-03 at 13:21 -0800, Scott Davenport wrote: > On Tue, 2009-03-03 at 12:34 -0800, Cynthia McGuire wrote: > > Tom Pothier wrote: > > > 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? > > > > No. libtopo should be getting its SMBIOS information directly from > > libsmbios. I see no motivation in your spec for an intermediate > layer. > > Several months ago when the project was first conceived, there was > motivation for reusing and leveraging code from sun4v. As the project > scoping has progressed, the amount of leverage has decreased. I had > a quick chat with Tom just now, and at this point there's no driving > need for an interim structure between libsmbios and a topo enumerator. > > The implementation approach aside, is there a general disagreement > with the project concept - enumerate from an industry standard source?
Oh yeah... +1 _______________________________________________ fm-discuss mailing list fm-discuss@opensolaris.org
