public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sun, 21 Oct 2007 01:23:50 +0200	[thread overview]
Message-ID: <m3ejfp4bg9.fsf@maximus.localdomain> (raw)
In-Reply-To: <4719FF0F.3080504@s5r6.in-berlin.de> (Stefan Richter's message of "Sat, 20 Oct 2007 15:13:51 +0200")

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

Examine (and backup) the EEPROM data first:

# /sbin/lspci | grep 1394
01:04.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
	Controller (rev 80)

# ./vt6307ohciver 01:04.0
[some debug info]
It seems your VT6307 chip is connected to I^2C (24c01 or similar) EEPROM

EEPROM dump:
00: 00 10 DC 00 01 01 D4 F2 04 04 32 55 F8 00 A2 02
10: A1 00 40 63 62 14 0D 25 03 DF 40 80 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

(If you have only one VIA firewire chip you can use "" as the argument.)

I'd check if there is a small SMD 8-pin 24c01 or similar EEPROM
near VT6307 if I were you. Alternatively the program may say you
have 93c46, also a small 8-pin chip.

Now you can try upgrading to OHCI-1.1:

# ./vt6307ohciver "" 1.1
It seems your VT6307 chip is connected to I^2C (24c01 or similar) EEPROM
writing 0x08 at address 0x22
Please reboot

People with 93c46 will see 0x11 address.

Do as commanded, reboot (PCI reset) is required for the VT6307 to reload
the configuration from its EEPROM.


Please let me know if it doesn't work.


This program may possibly run on VT6306-based board/card as well,
though I don't know what would happen (I suspect it could work,
but may need some modifications).

The "dump" function should work with any OHCI firewire device,
though for non-VIA chips you would have to change PCI device/vendor
ID in the source.

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) and, if you tried "upgrading" or
"downgrading", if it worked. In theory VT6306 should be able to
run in OHCI-1.1 mode, but I don't really know.
VT6306 only supports 93c46 EEPROM so if the program says 24c01
you may want to force it (edit the source) and let me know.

VT6305 users may not bother, this chip doesn't support OHCI-1.1.
Not sure if anything like it ever existed, though.
-- 
Krzysztof Halasa

  reply	other threads:[~2007-10-21  2:30 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 [this message]
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=m3ejfp4bg9.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