[lkml]   [2002]   [Aug]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] 2.5.31 driverfs: patch for your consideration
    On Mon, Aug 19, 2002 at 03:50:57PM +0000, Adam Belay wrote:
    > What does need to be done is a user level program that finds and loads
    > the proper modules automatically. Maybe we could use the existing
    > hotplug scripts or we could even start from scratch.

    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 and this article:
    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.


    greg k-h
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:28    [W:2.532 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site