On Wed, Feb 05, 2003 at 11:39:27AM +0100, Jules Bjørn Colding wrote: > Hi, > > On Wed, 2003-02-05 at 10:04, Erik Mouw wrote: > > Don't fiddle with the PCI config space like that. We have the function > > pci_write_config_byte() and friends for that. If you use those > > functions, your driver will be portable, so it will work without > > changing a single line of code the minute you put it in a PowerPC > > machine. Another advantage is that using the pci_*() functions make > > your code much more readable. > > I would love to do that, but I need a struct pci_dev before I can use > pci_write_config_byte() and friends. To find a pci_dev (with > pci_find_device() I think) I need a vendor and device id. My problem is > that I don't have these. My device is a CR16MCS9 (see google) which has > been bolted onto the PCI/ISA bridge. This device reports no vendor or > device id to the system, well.. maybe it does, but then I can't find it. > > I can therefore not see how I can get a pci_dev pointer and thought that > my only solution was to write directly to the pci registers. Is there > another way around this problem ? Use the pci_write_config_*_nodev() functions in the 2.4 kernel, or the pci_bus_write_config_*() fuctions in 2.5. That should do what you need. Good luck. greg k-h -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
