From: Greg KH <gregkh@linuxfoundation.org>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: no USB keyboard in 3.5-rc1 and later
Date: Fri, 29 Jun 2012 23:36:26 -0400 [thread overview]
Message-ID: <20120630033626.GB4792@kroah.com> (raw)
In-Reply-To: <20120628060456.GA2132@gherkin.frus.com>
On Thu, Jun 28, 2012 at 01:04:56AM -0500, Bob Tracy wrote:
> On Tue, Jun 26, 2012 at 08:30:31PM -0500, Bob Tracy wrote:
> > Here's hoping it's something simple. Attached USB devices fail to
> > initialize/work for kernel version 3.5-rc1 and later (up through
> > 3.5-rc4). From what I can tell from the dmesg output (attached),
> > there used to be an "input" or "generic-usb" message that appeared
> > for each device following detection -- showing the sysfs path to the
> > device.
>
> The answer *was* simple: the deprecated usbfs under /proc went bye-bye
> starting with 3.5-rc1. I'm still using a static "/dev" (no "udev").
> Hence, no device nodes under "/dev/bus/usb".
If you are using a static /dev/ then you should just create these nodes
statically and you should be fine, right?
thanks,
greg k-h
prev parent reply other threads:[~2012-06-30 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 1:30 Bob Tracy
2012-06-28 6:04 ` Bob Tracy
2012-06-30 3:36 ` Greg KH [this message]
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=20120630033626.GB4792@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rct@gherkin.frus.com \
/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
Powered by JetHome