On Sat, Mar 13, 2004 at 06:53:02PM +0100, Jean Delvare wrote: > > Note: What kind of error should the detection function return when the > user forces the driver, but the driver doesn't agree to load? Some of > our drivers return -EINVAL (e.g. w83781d), some -ENODEV (e.g. asb100, > lm78), some return without an error (e.g. it87). I think we should decide > of a policy and stick to it. Why would the driver not agree to load? It should always load, but just not bind to a device, right? Anyway, -ENODEV is a good error, as the device isn't there, or can't be found. thanks, greg k-h
