Messages in this thread | | | Date | Mon, 20 Jan 2003 16:33:21 +0000 | From | Christoph Hellwig <> | Subject | Re: propagating failures down to pci_module_init() |
| |
On Mon, Jan 20, 2003 at 03:54:35PM +0000, Dave Jones wrote: > I've got a wierd situation with a certain chipset for agpgart. > There are a few cases where I want to be able to use the existing > pci_driver api to detect the right PCI device, and call > the relevant .probe routine. No problem there. > > The problem is that in these cases, I want to be able to read > a certain register in that device, and if a bit is 0, bail out > of the .probe function with -ENODEV, and make the loading of > the module fail. > > The problem is that the ENODEV in my .probe routine doesn't > propagate back down as far as pci_module_init(). > > Ideas ?
Just use pci_register_driver.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |