Um, the current hotplug scripts, and my diethotplug program already do
this. Why write another user program to do this? What problem are you
trying to solve?
> Maybe we should make a file in the source tree where driver developers
> can list their supported hardware IDs but more importantly
> documentation on the attributes registered into driverfs.
The support hardware ids are already in the source code, and can be
easily extracted, that is what depmod(8) does to build the modules.*map
files. See the linux-hotplug documentation at
http://linux-hotplug.sf.net/ and this article:
http://www.linuxjournal.com/article.php?sid=5604
on how all of this works. I need to move that article into the
Documentation/DocBook directory someday soon...
driverfs documentation could be retrieved with the DEVICE_ATTR macro, if
we _really_ throught this would be useful.
thanks,
greg k-h
-
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/