[lkml]   [2002]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [linux-usb-devel] Re: 2.5.26 hotplug failure

    On Sat, 21 Sep 2002, Brad Hards wrote:

    > On Sat, 21 Sep 2002 06:42, David Brownell wrote:
    > > >>I wasn't joking about putting back the /proc/bus/usb/drivers file. This
    > > >> is really going to hurt us in 2.6.
    > >
    > > Considering that the main use of that file that I know about was
    > > implicit (usbfs is available if its files are present, another
    > > assumption broken in 2.5), I'm not sure I feel any pain... :-)
    > OK. Everytime someone goes "I've got usbfs loaded, and here is
    > /proc/bus/usb/devices, but can't send you /proc/bus/usb/drivers", I'll assume
    > that you two will answer the question.
    > Helping people is hard. Please don't make it harder. :-(

    We definitely don't want to make it harder, for users or developers. We're
    actually trying to make it easier for both, even though it may not be
    apparent right now.

    Converting code to the driver model means we get to consolidate a lot of
    similar yet disparate interfaces and code, which most people seem to

    As far as userspace goes, there are tools being developed to extract
    data from driverfs, to give users easy access to device and driver
    attributes; the stuff that was encoded in various proc files. With these
    tools, $user should be able to extract $data for $developer WRT $object.

    And, they should work identically for any instance of an object type
    that's encoded in driverfs: all devices or all bus types or all class
    types, etc, will behave identicaly and give similar data.

    For example, to extract the data you mention above, it would be something

    $ lsbus usb devices >
    $ lsbus usb drivers >>

    No, they're not done, and so I'm all talk about at this point. But, this
    has been the plan all along..


    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:29    [W:0.022 / U:26.712 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site