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: Wed, 17 Oct 2007 21:38:29 +0200 [thread overview]
Message-ID: <m34pgpmszu.fsf@maximus.localdomain> (raw)
In-Reply-To: <471527E5.1050407@s5r6.in-berlin.de> (Stefan Richter's message of "Tue, 16 Oct 2007 23:06:45 +0200")
Stefan Richter <stefanr@s5r6.in-berlin.de> writes:
> And in case of VT6307, I suspect it's VIA who
> selects the implementation level (based on chip revision), not the card
> vendor.
Can't be, the customers (real ones - board makers) would kill them
at once and then buy a different brand. That's not selling a different
wifi card under the old name.
Anyway, I just connected a programmer to the EEPROM (machine "a" in my
previous mail = EPIA-M 600 MHz), wrote "8" to the 16-bit word at address
0x11 (93c46 EEPROM), and now this VT6307S dated 0239CD (2002, 39th week)
says:
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[12] MMIO=[de000000-de0007ff]
Max Packet=[2048] IR/IT contexts=[4/8]
Unfortunately it's not much good for general consumption, and I haven't
yet found a way to write to the EEPROM using VT6307 registers (one can
easily read it using documented GUID register).
Nobody with a good VIA contact?
I'm not asking for something extraordinary, am I?
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-10-17 19:38 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 ` VIA VT6307 OHCI version? Krzysztof Halasa
2007-10-16 20:33 ` Krzysztof Halasa
2007-10-16 21:06 ` Stefan Richter
2007-10-17 19:38 ` Krzysztof Halasa [this message]
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=m34pgpmszu.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