public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Collins, Bernard F. (Skip)" <Bernard.Collins@jhuapl.edu>
Cc: "''linux-kernel@vger.kernel.org' '" <linux-kernel@vger.kernel.org>
Subject: Re: Visor USB hang
Date: Sat, 6 Dec 2003 19:22:52 -0800	[thread overview]
Message-ID: <20031207032251.GA28879@kroah.com> (raw)
In-Reply-To: <E37E01957949D611A4C30008C7E691E2F38C26@aples3.dom1.jhuapl.edu>

On Sat, Dec 06, 2003 at 12:52:52PM -0500, Collins, Bernard F. (Skip) wrote:
>  
> Greg KH wrote:
> >On Thu, Dec 04, 2003 at 09:49:31AM -0500, Bernard Collins wrote:
> > On Wed, 2003-12-03 at 19:24, Greg KH wrote:
> 
> > Sounds like a uhci timing issue :(
> 
> Does :( mean that it is not likely to be fixed? If so, is that because
> usb-uhci is going to be deprecated in favor of uhci?

Well, in 2.6, uhci turned into uhci-hcd and the usb-uhci driver
disappeared.

> >> So is there a downside to uhci compared to usb-uhci?
> 
> > Not that I know of, it's what I use...
> 
> I did find one problem on my machine: VMware USB support depends on
> usb-uhci. Oh, and my USB storage keychain device works with usb-uhci but not
> uhci.

I've run vmware just fine with uhci, it just seems that some distros
prefer usb-uhci.  But use what works for you.

greg k-h

  reply	other threads:[~2003-12-07  3:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06 17:52 Visor USB hang Collins, Bernard F. (Skip)
2003-12-07  3:22 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-04  3:31 Collins, Bernard F. (Skip)
2003-12-03 22:36 Collins, Bernard F. (Skip)
2003-12-04  0:24 ` Greg KH
2003-12-04 14:49   ` Bernard Collins
2003-12-06  1:03     ` Greg KH
2003-12-03 20:44 Collins, Bernard F. (Skip)
2003-12-03 21:21 ` 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=20031207032251.GA28879@kroah.com \
    --to=greg@kroah.com \
    --cc=Bernard.Collins@jhuapl.edu \
    --cc=linux-kernel@vger.kernel.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