How could PCI device driver get to know device ID?

How could PCI device driver get to know device ID?

Post by Sergei Vla » Mon, 17 Oct 2005 12:34:21


Hello.
PCI devices are enumerated by their VID/FID identifiers.
What is the easiest way for the driver to find these IDs?

Is there a more friendly way than parsing that cumbersome
Registry string ?
(r41_pci,PCI\VEN_5555&DEV_3333)

Or maybe there is known correct way for driver
to destinguish devices one from another?
(Single driver handles several very like devices with different
capabilities. For now, the only visible through the interface
difference between devices is FID. Any more good solutions?)

Thanks.
 
 
 

1. [v1 PATCH 1/1] PCI: Add AMD8111 PCI Bridge PCI Device ID

2. Device/device driver to use with PCI-SyncClock32Univ

I have some trouble setting up a Brandywine Communications PCI-
SyncClock32Univ as a reference clock in a Linux computer.

refclock_gpsvme.c seems to support the Brandywine Communications PCI-
SyncClock32Univ. The memory map in struct psc_regs do match.

ntp.conf I have added:
server 127.127.21.0

What I do not know is what device driver to use.

The PCI-SyncClock32Univ features a PLX Technology PCI 9030 device to
interface with the PCI bus. The Linux driver can be downloaded from
here http://www.yqcomputer.com/

I installed this driver (I tried both v4.40 and v5.10 of the SDK), and
I make a link like this
ln -s /dev/plx/pci9030-0 /dev/refclock0

This makes ntpd exit with a segmentation fault. refclock_gpsvme has an
ioctl uses PSC_REGS as shown here:
#define PSC_REGS _IOR('K', 0, long) /* ioctl
argument */
But this does not result in the base address needed for the memory
map, so a read result ofcourse in a segmentation fault.

The PLX SDK uses the 'P' as magic, so it seems that refclock_gpsvme.c
is designed to use a different device driver than the one provided in
the PLX SDK.

Is there somebody how knows more about this?

Thanks in advance.

Rodebiet.

3. Device manager Unknown Device & PCI Device (yellow warning)

4. [patch 4/5] x86: Add PCI IDs for AMD Barcelona PCI devices

5. [PATCH] PCI: Add PCI device ID for new Mellanox HCA

6. [PATCH] Add PCI device ID for IT8152 RISC-to-PCI chip

7. Getting name of device which is bind to raw device if i have raw device name

8. How to access second PCI card with same signature ( Vendor Id and Device Id)

9. NTKERN.VXD Device loaders for this device could not load the device drivers (code 2.)

10. NTKERN.VXD device loader(s) for device,Processor, could not load device drivers

11. NTKERN.VXD Device loaders for this device could not load the device drivers (code 2.)

12. US-TX-Austin: Win Device Driver Developer, 8+yrs exp. , 5+yrs. Win Device Driver (45348714449)

13. US-TX-Austin: Win Device Driver Developer, 8+yrs exp. , 5+yrs. Win Device Driver (45342658838)

14. US-TX-Austin: Win Device Driver Developer, 8+yrs exp. , 5+yrs. Win Device Driver (45347214409)

15. US-TX-Austin: Win Device Driver Developer, 8+yrs exp. , 5+yrs. Win Device Driver (45349014402)