Messages in this thread | ![/](/images/icornerl.gif) | | Date | Mon, 20 Jan 2003 15:54:35 +0000 | From | Dave Jones <> | Subject | propagating failures down to pci_module_init() |
| |
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 ?
Dave
-- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - 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/
| ![\](/images/icornerr.gif) |