PCI Device IDs problem

Martin Owens doctormo at gmail.com
Thu Mar 22 13:04:04 PDT 2007


Hello all,

When researching how to tie up dmidecode and more importantly
biosdecode programs into my hardware app I notice that it tells me
that I have a pci device on 01:00 (on-board) but in hal this device id
does not exist, instead I have a device I presume is the same one
00:00.

Are these the same device and is hal lobbing off the first byte my
mistake? or is it that the sysfs_path isn't comparable to the PCI
Interrupt ID?

Hal Version 0.5.7.1-0ubuntu17 - No if you have fixed this bug then I
will work around it rather than require a much newer version of HAL, I
just need to know what the implications are.

PCI Interrupt Routing 1.0 present.
        Router ID: 00:11.0
        Exclusive IRQs: None
        Compatible Router: 1106:3227
        Slot Entry 1: ID 00:01, on-board
+        Slot Entry 2: ID 01:00, on-board
        Slot Entry 3: ID 00:11, on-board
        Slot Entry 4: ID 00:10, on-board
        Slot Entry 5: ID 00:12, on-board
        Slot Entry 6: ID 00:0f, on-board
        Slot Entry 7: ID 00:09, slot number 1
        Slot Entry 8: ID 00:0a, slot number 2
        Slot Entry 9: ID 00:0b, slot number 3

HAL:
-        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:00.0
-        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:00.1
-        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:00.2
-        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:00.3
-        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:00.4
-        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:00.7
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:01.0
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:09.0
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:09.1
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:09.2
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:09.3
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:09.4
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:0b.0
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:0f.0
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:0f.1
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:10.0
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:10.1
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:10.2
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:10.3
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:10.4
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:11.0
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:11.5
        pci.linux.sysfs_path  /sys/devices/pci0000:00/0000:00:12.0

P.S. It would be more interesting is hal it's self used the dmi
information to set a flag against the pci devices that indicated they
where on board or infact what slot they were plugged into.

Best Regards, Martin Owens


More information about the hal mailing list