On 02/18/2016 09:04 PM, Jordan Hargrave wrote: > The VPD-R is a readonly area of the PCI Vital Product Data region. > There are some standard keywords for serial number, manufacturer, > and vendor-specific values. Dell Servers use a vendor-specific > tag to store number of ports and port mapping of partitioned NICs. > > info = VPD-Info string > PN = Part Number > SN = Serial Number > MN = Manufacturer ID > Vx = Vendor-specific (x=0..9 A..Z) > > This creates a sysfs subdirectory in the pci device: vpdattr with > 'info', 'EC', 'SN', 'V0', etc. files containing the tag values. > > Signed-off-by: Jordan Hargrave <Jordan_Hargrave@xxxxxxxx> Hmm. Can we first get an agreement on the PCI VPD parsing patches I've posted earlier? VPD parsing is really tricky, and we should aim on making the read_vpd function robust enough before we begin putting things into sysfs. Also, I'm not utterly keen on this patchset. The sysfs space is blown up with tiny pieces of information, which can easily gotten via lspci, too. Also, to my knowledge it's perfectly valid to _write_ to the VPD, in which case the entire sysfs attribute setup would be invalided. How do you propose to handle that? Cheers, Hannes -- Dr. Hannes Reinecke Teamlead Storage & Networking hare@xxxxxxx +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
