From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-user@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: VIA VT6307 OHCI version?
Date: Tue, 16 Oct 2007 22:33:41 +0200 [thread overview]
Message-ID: <m38x62bxzu.fsf@maximus.localdomain> (raw)
In-Reply-To: <m3d4vebylw.fsf@maximus.localdomain> (Krzysztof Halasa's message of "Tue, 16 Oct 2007 22:20:27 +0200")
Krzysztof Halasa <khc@pm.waw.pl> writes:
[VIA VT6306/6307]
> I haven't yet checked if it changes OHCI version - I of course
> could program the EEPROM externally but I think I'd better find
> how to do that from PCI side.
Added Cc:lkml, perhaps someone at VIA could find that strictly
confidential and destroy-before-reading document and spare me
the effort? :-)
All I need to know is:
a) meaning of the config EEPROM data for VIA firewire chips
b) how to read/write the EEPROM from PCI side (i.e., probably
EECS, EEDO, EEDI/SDA and EECK/SCL bit locations or however
it's done).
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-10-16 20:34 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 [this message]
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
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=m38x62bxzu.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-user@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.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
all inboxes | Powered by JetHome®