It looks like a good start - a lot of things will be cleaner afterward.
A question...
In struct device_driver:
> probe:
> Check for device existence and associate driver with it.
What, exactly, does "associate driver" mean? Filling in the struct device
field, perhaps? Calling register_chrdev (or register_whatever)? Creation
of a ddfs entry? As a driver writer I can understand that the probe
routine should check for the existence of some device, and perhaps set up
an internal data structure. What else happens?
jon
Jonathan Corbet
Executive editor, LWN.net
corbet@lwn.net
-
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/