From: Daniel Exner <webmaster@dragonslave.de>
To: David Brownell <david-b@pacbell.net>
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 11:46:42 +0200 [thread overview]
Message-ID: <200708141146.43215.webmaster@dragonslave.de> (raw)
In-Reply-To: <200708140101.19651.david-b@pacbell.net>
David Brownell wrote:
> On Monday 13 August 2007, Daniel Exner wrote:
[..]
> > 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".
ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Build into:
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890
South]
> > > > 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.
Didn't test it yet with 2.6.23-rc2 or rc3, but up to 2.6.22 it was fine :)
Regarding the option to blacklist VIA in the module:
I would prefer blacklisting VIA by default but giving the module some
parameter like "honours inactive bit" to override this.
Perhaps there are newer VIA Chips out there, that indeed do this and some
users trigger happy enough to test this. :)
Greetings
Daniel Exner
next prev parent reply other threads:[~2007-08-14 9:47 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
2007-08-14 9:46 ` Daniel Exner [this message]
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=200708141146.43215.webmaster@dragonslave.de \
--to=webmaster@dragonslave.de \
--cc=Stuart_Hayes@dell.com \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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