public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: webmaster@dragonslave.de
Cc: Stuart_Hayes@dell.com, greg@kroah.com,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net, jikos@jikos.cz
Subject: Re: EHCI Regression in 2.6.23-rc2
Date: Tue, 14 Aug 2007 01:01:19 -0700	[thread overview]
Message-ID: <200708140101.19651.david-b@pacbell.net> (raw)
In-Reply-To: <200708140843.42196.webmaster@dragonslave.de>

On Monday 13 August 2007, Daniel Exner wrote:
> David Brownell wrote:
> > On Monday 13 August 2007, Stuart_Hayes@dell.com wrote:
> > > With the VIA controller I have,
> >
> > Which kind is that?  The VT6202 is buggy as all get-out, and
> > they sold a *LOT* of those discrete chips for use in add-on PCI
> > cards.  We generally warn people away from those.  A more current
> > version is the VT6212, which was much more usable.  (If it says
> > EHCI 0.95, it's a VT6202... their EHCI 1.0 chips were much better.)
>
> Where exactly should I search for this? Neither lspci nor lsusb showed any 
> hint on the EHCI rev. the chip conforms to..

The driver logs that information as it starts; on this sytem:

 ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004

vs "EHCI 0.95".

 
> [..]
> > > Perhaps for now the best thing would just be to bypass the EHCI CPU
> > > frequency notifier code (i.e., my patch) for VIA EHCI controllers, since
> > > they are broken.  Would a hard-coded blacklist (just an "if
> > > (manufacturer==VIA)..." type thing) be OK?
> >
> > Yes ... although if you don't need to blacklist their EHCI 1.0 chips
> > don't do it.  (Any VIA EHCI integrated into a southbridge is going
> > to follow spec rev 1.0 pretty well, modulo idiosyncratic timings.)
>  
> I guess its needed to blacklist even the ECHI 1.0 chips, since my problem is
> with exactly one of those ;)

Something doesn't add up then ... above you ask where to find that info,
but here you say you already got it from somwhere ... ?


> I'm not really into USB protocol specs, but perhaps its possible to test 
> wether the problem Stuarts patch addressed can actually happen on VIA EHCI 
> chips? Perhaps those guys solved the problem in Hard/Firmware..

Theoretically possible, and I've certainly seen hardware made to do
stranger things than that.


> > > I've also acquired a card with an NEC EHCI controller on it, which I'm
> > > going to look at while I'm into it...
> >
> > Another case where there are a lot of add-on "EHCI 0.95" cards; but
> > in this case the quirks were less significant.
>
> Some guy donated me a PCMCIA card with one of those, cause it'll wont work in 
> his Windows only Notebook :)

A NEC 0.95 ??  Should be fine with Linux.  Assuming no bugs have
crept in.

- Dave




  reply	other threads:[~2007-08-14  8:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  8:45 EHCI Regression in 2.6.23-rc2 Daniel Exner
2007-08-10  9:27 ` Jiri Kosina
2007-08-10 13:08   ` Daniel Exner
2007-08-13 20:48     ` Stuart_Hayes
2007-08-13 22:16       ` David Brownell
2007-08-14  6:43         ` Daniel Exner
2007-08-14  8:01           ` David Brownell [this message]
2007-08-14  9:46             ` Daniel Exner
2007-08-14 15:13               ` Stuart_Hayes
2007-08-14 15:49                 ` David Brownell
2007-08-14 21:33                   ` Stuart_Hayes
2007-08-15 18:38                     ` Stuart_Hayes
2007-08-15 19:12                       ` [linux-usb-devel] " David Brownell
2007-08-14 15:42               ` David Brownell
2007-08-14 15:57                 ` Daniel Exner
2007-08-14 16:12                   ` David Brownell
2007-08-10 15:14   ` Stuart_Hayes

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=200708140101.19651.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=Stuart_Hayes@dell.com \
    --cc=greg@kroah.com \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=webmaster@dragonslave.de \
    /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