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: Sat, 20 Oct 2007 00:42:34 +0200	[thread overview]
Message-ID: <m3abqeybdx.fsf@maximus.localdomain> (raw)
In-Reply-To: <m3fy09ffp9.fsf@maximus.localdomain> (Krzysztof Halasa's message of "Thu, 18 Oct 2007 02:07:30 +0200")

> 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.

BTW: I've looked at it a bit closer and it seems the EEPROM lines
are controlled by VT6307 I/O ports (region #1) 0x0 and 0x20:

01:04.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
		Controller (rev 80) (prog-if 10 [OHCI])
        Memory at feafe800 (32-bit, non-prefetchable) [size=2K]
        I/O ports at d480 [size=128]
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

port 0x20 R/O bit 8 is set in 93c46 mode and reset in I^2C mode
port 0x20 bit 4 must be set to drive CS, CLK and DATA-OUT outputs
port 0x20 bits 3, 2 and 1 are, respectively, CS, CLK and DATA-OUT
     pins in 93c46 mode and unused, SCL and SDA pins in I^2C mode
port 0x20 R/O bit 0 is DATA-IN input in 93c46 mode

port 0x0 bit 8 must be set to enable access
port 0x20 must be written 0x20 (bit 5 only) to disable access
     (clears port 0x0 bit 8).

They are all 32-bit I/O ports.

The above allows for complete control in 93c46 mode (I'll make the
program available later) and unfortunately I don't yet know how to
read SDA (and SCL) state in I^2C mode (I can blindly write to the
EEPROM and I can read the EEPROM data using GUID PROM register so
there is a workaround).
-- 
Krzysztof Halasa

  reply	other threads:[~2007-10-19 22: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 [this message]
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=m3abqeybdx.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