From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux1394-user@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: VIA VT6307 OHCI version?
Date: Sat, 20 Oct 2007 08:31:32 +0200 [thread overview]
Message-ID: <4719A0C4.3050301@s5r6.in-berlin.de> (raw)
In-Reply-To: <m3fy09ffp9.fsf@maximus.localdomain>
Krzysztof Halasa wrote:
> OTOH, it's no magic - they claim OHCI 1.1 and they do it. We don't
> only know how to enable it with (only) software. I suspect all those
> VT6306 could be "upgraded" as well.
What if we add a whitelisting in the driver which ignores the register
contents which state OHCI 1.0 implementation level, and just treats
these VIA chips as OHCI 1.1 implementations?
--
Stefan Richter
-=====-=-=== =-=- =-=--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-10-20 6:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3sl4ciz1h.fsf@maximus.localdomain>
[not found] ` <4714EF01.2060609@s5r6.in-berlin.de>
2007-10-16 20:20 ` Krzysztof Halasa
2007-10-16 20:33 ` Krzysztof Halasa
2007-10-16 21:06 ` Stefan Richter
2007-10-17 19:38 ` Krzysztof Halasa
2007-10-17 20:11 ` Stefan Richter
2007-10-17 20:54 ` Krzysztof Halasa
2007-10-17 21:06 ` Stefan Richter
2007-10-18 0:07 ` Krzysztof Halasa
2007-10-19 22:42 ` Krzysztof Halasa
2007-10-20 6:31 ` Stefan Richter [this message]
2007-10-20 13:03 ` Krzysztof Halasa
2007-10-20 13:13 ` Stefan Richter
2007-10-20 23:23 ` Krzysztof Halasa
2007-10-28 17:41 ` Stefan Richter
2007-10-28 20:40 ` Krzysztof Halasa
2007-10-28 23:12 ` Stefan Richter
2007-10-29 12:53 ` Krzysztof Halasa
2007-11-03 19:15 ` Stefan Richter
2007-11-04 16:54 ` Krzysztof Halasa
2007-11-04 19:31 ` Andreas Mohr
2007-11-04 23:00 ` Krzysztof Halasa
2007-11-05 18:25 ` Andreas Mohr
2007-11-05 19:14 ` Stefan Richter
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=4719A0C4.3050301@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-user@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
all inboxes | Powered by JetHome®