From: Greg KH <greg@kroah.com>
To: David Brownell <david-b@pacbell.net>
Cc: Patrick Mochel <mochel@osdl.org>, Dave Jones <davej@suse.de>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driverfs support for USB - take 2
Date: Mon, 4 Feb 2002 22:49:12 -0800 [thread overview]
Message-ID: <20020205064912.GA31487@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201291711560.800-100000@segfault.osdlab.org> <08cf01c1a933$f45ac460$6800000a@brownell.org> <20020130040908.GA23261@kroah.com> <0a1501c1a9c9$bdf427e0$6800000a@brownell.org> <20020202001804.GC10313@kroah.com> <0e9101c1ac1d$b18b25c0$6800000a@brownell.org>
In-Reply-To: <0e9101c1ac1d$b18b25c0$6800000a@brownell.org>
On Sat, Feb 02, 2002 at 11:13:26AM -0800, David Brownell wrote:
> > No, I'll say that we need to stay one physical device per device in the
> > tree.
>
> But we aren't that way today. Examples:
<snip>
Ok, you're right. We want to tell the drivers to shut down (remember,
the original goal of driverfs was for power management), so all drivers
that attach to a device need to be shown.
I'll play with the code some more and make this kind of change.
> > If you want to do an interface tree, let's put that in usbfs,
> > where it belongs :)
>
> Ah, but changing usbfs is impractical at this point since lots of
> userspace programs rely on it not changing. Which is why I
> was pointing this out in the context of driverfs, which can still
> be improved in such ways ... "usbdevfs" was always advertised
> as "preliminary", anyway! :)
Heh, I took the "preliminary" tag off of it a short while ago, as so
many different userspace programs were using it. Maybe usbfs2? :)
Seriously, I've had some ideas of a different way to implement the
functionality of usbfs, possibly without all of the ioctl calls, but I
have not had the time to experiment with it...
thanks,
greg k-h
next prev parent reply other threads:[~2002-02-05 6:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 0:24 [PATCH] driverfs support for USB - take 2 Greg KH
2002-01-30 1:03 ` Dave Jones
2002-01-30 1:09 ` Greg KH
2002-01-30 1:19 ` Patrick Mochel
2002-01-30 2:15 ` [linux-usb-devel] " David Brownell
2002-01-30 4:09 ` Greg KH
2002-01-30 20:07 ` [linux-usb-devel] " David Brownell
2002-02-02 0:18 ` Greg KH
2002-02-02 19:13 ` David Brownell
2002-02-05 6:49 ` Greg KH [this message]
2002-01-30 1:49 ` [linux-usb-devel] " Stephen J. Gowdy
2002-01-30 4:10 ` Greg KH
2002-01-30 18:26 ` Patrick Mochel
2002-01-30 20:24 ` [linux-usb-devel] " David Brownell
2002-02-02 0:23 ` Greg KH
2002-02-02 19:27 ` David Brownell
2002-01-31 12:49 ` Pavel Machek
2002-02-01 9:27 ` Horst von Brand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020205064912.GA31487@kroah.com \
--to=greg@kroah.com \
--cc=davej@suse.de \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mochel@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox