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: Sun, 28 Oct 2007 18:41:46 +0100 [thread overview]
Message-ID: <4724C9DA.7030900@s5r6.in-berlin.de> (raw)
In-Reply-To: <m3ejfp4bg9.fsf@maximus.localdomain>
Krzysztof Halasa wrote:
> Ok. I just put a program on something like
> http://www.kernel.org/~chris/vt6307ohciver.c
>
> Anybody with OHCI-1.0 VT6307* Firewire chip may want to try. Obviously
> it's based on undocumented features, it may blow your machine etc.
>
> Please remove your ohci1394 or firewire-ohci driver before using this
> program.
>
> Compile with the usual spell: gcc -Wall -O2 vt6307ohciver.c -o vt6307ohciver
I also had to specify "-lpci" on Mandrake 10.1, "-lpci -lz" on Gentoo.
...
> If you have a VT6306-based card and you run this program, I'd
> appreciate it if you let me know the EEPROM contents (make sure
> you mention chip type)
# lspci|grep 1394
00:0a.3 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394
Host Controller (rev 46)
00:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394
Host Controller (rev 46)
These are both VT6306, one on the motherboard and one on a PCI card.
# ./a.out 00:0a.3
I/O region #1 is at C800
It seems your VT6307 chip is connected to 93c46 EEPROM
Page size is 4096 (0x1000) bytes
GUID PROM register address is 0xec101004
Mapping 8 (0x8) bytes of memory at 0xec101000
Mapped mem region #0 at virtual address 0xb7f3a000
GUID PROM register is at virtual address 0xb7f3a004
EEPROM dump:
00: 00 11 06 00 00 00 E3 32 00 88 00 08 44 00 00 00
10: A1 E4 2F 00 06 11 44 30 03 DF 40 00 00 20 00 73
20: 3C 10 00 00 00 00 FF FF FF FF FF FF D7 57 55 75
Your VT6307 chip is in OHCI 1.0 mode
# ./a.out 00:0c.0
I/O region #1 is at D000
It seems your VT6307 chip is connected to 93c46 EEPROM
Page size is 4096 (0x1000) bytes
GUID PROM register address is 0xec103004
Mapping 8 (0x8) bytes of memory at 0xec103000
Mapped mem region #0 at virtual address 0xb7f1a000
GUID PROM register is at virtual address 0xb7f1a004
EEPROM dump:
00: 00 30 1B AC 00 00 2B A4 04 04 32 55 F8 00 A2 02
10: A1 00 40 63 06 11 44 30 03 DF 40 00 00 20 00 73
20: 3C 10 00 00 00 00 FF FF FF FF FF FF FF FF FF FF
Your VT6307 chip is in OHCI 1.0 mode
On another PC:
# lspci | grep 1394
02:02.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2
IEEE-1394b Link Layer Controller (rev 01)
05:04.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394
Host Controller (rev 80)
06:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394
Host Controller (rev 46)
The "rev 80" chip is a VT6307 on the motherboard.
# ./a.out 05:04.0
I/O region #1 is at ED00
It seems your VT6307 chip is connected to I^2C (24c01 or
similar) EEPROM
Page size is 4096 (0x1000) bytes
GUID PROM register address is 0xfbffd004
Mapping 8 (0x8) bytes of memory at 0xfbffd000
Mapped mem region #0 at virtual address 0xb7f76000
GUID PROM register is at virtual address 0xb7f76004
EEPROM dump:
00: 00 10 DC 56 00 FE D2 D4 04 04 32 55 F8 00 A2 02
10: A1 00 40 63 20 63 62 14 03 DF 40 80 00 20 00 73
20: 3C 10 08 00 00 00 FF FF FF FF FF FF FF FF FF FF
Your VT6307 chip is in OHCI 1.1 mode
The "rev 46" chip is on a CardBus card. So far I believed it to be a
VT6306 but I can't easily open the card's casing...
# ./a.out 06:00.0
I/O region #1 is at E000
It seems your VT6307 chip is connected to I^2C (24c01 or
similar) EEPROM
Page size is 4096 (0x1000) bytes
GUID PROM register address is 0x80000004
Mapping 8 (0x8) bytes of memory at 0x80000000
Mapped mem region #0 at virtual address 0xb7f2f000
GUID PROM register is at virtual address 0xb7f2f004
EEPROM dump:
00: 00 11 06 00 00 00 41 CC 04 04 32 55 F8 00 92 02
10: A1 00 40 63 06 11 44 30 03 DF 40 80 00 20 00 73
20: 3C 10 00 00 00 00 A0 00 FF FF FF FF FF FF FF FF
Your VT6307 chip is in OHCI 1.0 mode
> and, if you tried "upgrading" or "downgrading", if it worked.
I haven't tried it yet.
--
Stefan Richter
-=====-=-=== =-=- ===--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-10-28 17:42 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
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 [this message]
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=4724C9DA.7030900@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