From: Greg KH <gregkh@suse.de>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Scott James Remnant <scott@canonical.com>,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: can we move USB_DEVICEFS to non-embedded?
Date: Tue, 23 Jun 2009 08:39:28 -0700 [thread overview]
Message-ID: <20090623153928.GA32604@suse.de> (raw)
In-Reply-To: <b6a2187b0906230829k308cb875r7362f184bccb1d6d@mail.gmail.com>
On Tue, Jun 23, 2009 at 11:29:50PM +0800, Jeff Chua wrote:
> On Tue, Jun 23, 2009 at 10:42 PM, Greg KH<gregkh@suse.de> wrote:
> > On Tue, Jun 23, 2009 at 01:11:51PM +0800, Jeff Chua wrote:
> >> commit cc71329b3b89b4a5be849b617f2c4f151f0b9213 moved USB_DEVICEFS to
> >> be embedded and marked it as depreciated. Can this be reverted? This
> >> breaks vmware and those systems not using udev.
>
> > vmware now works properly with this fix, and has for over a year or so.
>
> vmware is working, but can't detect USB devices.
Odd, what version of vmware are you using?
> > What distro does not use udev or mdev or something like it already and
> > also does not use an updated libusb?
> > We need some specifics here please.
>
> I'm not using it and have been fine without it all these while, so
> don't see any gain moving to udev or perhaps it's time to consider ...
If you are running your own custom distro/install, then you should be
able to select CONFIG_EMBEDDED and then USB_DEVICEFS just fine on your
own. But note, that you don't sound like the "normal" user at all :)
thanks,
greg k-h
next prev parent reply other threads:[~2009-06-23 15:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 5:11 can we move USB_DEVICEFS to non-embedded? Jeff Chua
2009-06-23 8:17 ` Scott James Remnant
2009-06-23 14:42 ` Greg KH
2009-06-23 15:29 ` Jeff Chua
2009-06-23 15:39 ` Greg KH [this message]
2009-07-08 10:54 ` Dave Airlie
2009-07-08 11:03 ` Kay Sievers
2009-07-08 11:20 ` Dave Airlie
2009-07-08 11:42 ` Scott James Remnant
2009-07-08 13:00 ` Greg KH
2009-07-08 13:52 ` Peter Jones
2009-07-08 13:55 ` Peter Jones
2009-07-08 14:04 ` Greg KH
2009-07-08 14:12 ` Peter Jones
2009-07-08 14:56 ` Greg KH
2009-07-08 15:05 ` Peter Jones
2009-07-08 15:47 ` Greg KH
2009-07-08 21:23 ` Dave Airlie
2009-07-09 0:43 ` Jeff Chua
2009-07-09 1:59 ` Randy Dunlap
2009-07-09 2:31 ` Jeff Chua
2009-07-09 3:01 ` Randy Dunlap
2009-07-09 12:12 ` Jeff Chua
2009-07-09 1:33 ` Greg KH
2009-07-08 15:12 ` Bill Nottingham
2009-07-08 15:44 ` 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=20090623153928.GA32604@suse.de \
--to=gregkh@suse.de \
--cc=jeff.chua.linux@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@canonical.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.