in reply to pci.ids to a complex data structure

I am trying to set up a data structure to hold the information in /usr/share/misc/pci.ids.

I gather this is a linux-on-intel kind of thing (on a laptop with pci slots?) -- alas, those of us who don't have this sort of setup are clueless about what the "pci.ids" file contains or how it's organized. (My macosx has a /usr/share/misc directory, but no pci.ids file.) Could you post a sample of the data, and/or some reference info about the file format?

And can you show us your code that attempted to read the file into a hash structure? I'm sure you would rather read from the file, instead of having to hard-code the file contents into a perl script...

  • Comment on Re: pci.ids to a complex data structure

Replies are listed 'Best First'.
Re^2: pci.ids to a complex data structure
by McDarren (Abbot) on Aug 21, 2006 at 01:38 UTC
    From /usr/share/misc/pci.ids on my (Debian) Linux box: 
    # Vendors, devices and subsystems. Please keep sorted.

# Syntax:
# vendor  vendor_name
#       device  device_name                             <-- single tab
#               subvendor subdevice  subsystem_name     <-- two tabs

    [download]
    And some sample data: 
    # Formerly NCR
1000  LSI Logic / Symbios Logic
        0001  53c810
                1000 1000  LSI53C810AE PCI to SCSI I/O Processor
        0002  53c820
        0003  53c825
                1000 1000  LSI53C825AE PCI to SCSI I/O Processor (Ultr
+a Wide)
        0004  53c815
        0005  53c810AP
        0006  53c860
                1000 1000  LSI53C860E PCI to Ultra SCSI I/O Processor
        000a  53c1510
                1000 1000  LSI53C1510 PCI to Dual Channel Wide Ultra2 
+SCSI Controller (Nonintelligent mode)
        000b  53C896/897
                1000 1000  LSI53C896/7 PCI to Dual Channel Ultra2 SCSI
+ Multifunction Controller
                1000 1010  LSI22910 PCI to Dual Channel Ultra2 SCSI ho
+st adapter
                1000 1020  LSI21002 PCI to Dual Channel Ultra2 SCSI ho
+st adapter
# multifunction PCI card: Dual U2W SCSI, dual 10/100TX, graphics
                13e9 1000  6221L-4U
        000c  53c895
                1000 1010  LSI8951U PCI to Ultra2 SCSI host adapter
                1000 1020  LSI8952U PCI to Ultra2 SCSI host adapter
                1de1 3906  DC-390U2B SCSI adapter
                1de1 3907  DC-390U2W
        000d  53c885
        000f  53c875
                0e11 7004  Embedded Ultra Wide SCSI Controller
                1000 1000  LSI53C876/E PCI to Dual Channel SCSI Contro
+ller
                1000 1010  LSI22801 PCI to Dual Channel Ultra SCSI hos
+t adapter
                1000 1020  LSI22802 PCI to Dual Channel Ultra SCSI hos
+t adapter
                1092 8760  FirePort 40 Dual SCSI Controller
                1de1 3904  DC390F/U Ultra Wide SCSI Adapter
                4c53 1000  CC7/CR7/CP7/VC7/VP7/VR7 mainboard
                4c53 1050  CT7 mainboard

    [download]

    I started to have a play around with this earlier this morning, but I'm afraid that I'm a bit busy at work now. If I get time to have another go at it later I'll update.

[reply]
[d/l]
[select]
      The following might not be exactly the structure that you really want, but it does store all the pci.id file content without loss of information or structure. It differs from the OP layout (which maybe wasn't what you really wanted either) in that here, the various ID field values from the file are used as hash keys.

      It's a bit clunky, because the "descriptive" fields are held as values of "special" hash keys ("vendor_name" and "device_name"), and these keys are siblings to the hash keys that happen to be ID fields. But the structure is both adequate and fairly simple.

      (I had to make sure the data sample contained tab characters as described.)

      Read more... (4 kB)
[reply]
[d/l]

In Section Seekers of Perl Wisdom