public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Frans Pop <elendil@planet.nl>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.31-rc0-git: lsusb stopped working?
Date: Tue, 23 Jun 2009 09:13:34 -0700	[thread overview]
Message-ID: <20090623161334.GA503@kroah.com> (raw)
In-Reply-To: <200906231709.45851.elendil@planet.nl>

On Tue, Jun 23, 2009 at 05:09:44PM +0200, Frans Pop wrote:
> Pavel Machek wrote:
> > On thinkpad x60. Otherwise usb seems to work, including btusb dongle.
> > 
> > /proc/bus/usb does not seem to exists.
> 
> Correct. usbfs has been removed in 2.6.31.

To be pedantic, no, the filesystem has not been "removed".  Only the
user-mountable filesystem option has been moved under CONFIG_EMBEDDED,
as there should not be any userspace code that still uses that interface
into usbfs.

The recommended solution is to use the device nodes for usbfs, which
have been around for a few years now, and usually show up under
/dev/bus/usb/ and have the proper ACL and permissions that the
filesystem nodes can't have for a variety of reasons.

If for some reason you can not use the /dev/bus/usb/ device nodes, you
can enable the config option by turning on CONFIG_EMBEDDED.

Hope this helps,

greg k-h

  reply	other threads:[~2009-06-23 16:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 13:55 2.6.31-rc0-git: lsusb stopped working? Pavel Machek
2009-06-23 15:01 ` Greg KH
2009-06-23 15:01   ` Greg KH
2009-07-11  9:10   ` Pavel Machek
2009-07-11 17:43     ` Greg KH
2009-07-10 16:13       ` Pavel Machek
2009-07-12  0:25         ` Greg KH
2009-06-23 15:09 ` Frans Pop
2009-06-23 16:13   ` Greg KH [this message]
2009-06-23 20:35     ` Olivier Galibert
2009-06-23 20:37       ` Pavel Machek
2009-06-23 20:57       ` Greg KH

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=20090623161334.GA503@kroah.com \
    --to=greg@kroah.com \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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