mirror of https://lore.kernel.org/lkml/
 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
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: VIA VT6307 OHCI version?
Date: Tue, 16 Oct 2007 22:20:27 +0200	[thread overview]
Message-ID: <m3d4vebylw.fsf@maximus.localdomain> (raw)
In-Reply-To: <4714EF01.2060609@s5r6.in-berlin.de> (Stefan Richter's message of "Tue, 16 Oct 2007 19:04:01 +0200")

Stefan Richter <stefanr@s5r6.in-berlin.de> writes:

> AFAIK all 6306 are OHCI 1.0.  I presume that currently produced 6307 are
> OHCI 1.1 and maybe only first revisions of it were 1.0 --- but that's
> just my speculation.  I would be surprised though if it was merely a
> matter of EEPROM contents.

Both VT6306 and VT6307 datasheets claim selectable OHCI 1.0/1.1.
I guess they did that for compatibility or something like that.

The 6307 chip allows for either I^2C (24c01 etc) or 93c64 EEPROM (there
is a pin to select), while 6306 works with 93c64 only (4-wire: chip
select, clock, data-in, data-out).

I examined 3 machines with VT6307 using a simple home-made signal
analyzer:
a) using 93C46 EEPROM and OHCI 1.0
b) using 24C01A EEPROM and OHCI 1.0
c) using 24C01A EEPROM and OHCI 1.1

All 3 chips have PCI vendorID 1106 and deviceID 3044, revision is 0x80.

The VT6307 chip reads the EEPROM (after reset) in the following order:

ADDR	ADDR	a)	b)	c)
4-wire	I^2C
 A	14	subsystem vendor ID
 B	16	subsystem device ID

10	20	103C	103C	103C	values same on all machines
 C	18	DF03	DF03	DF03
 D	1A	8040	8040	8040
 E	1C	2000	2000	2000
 F	1E	7300	7300	7300

11	22	0000	0000	0008
12	24	0000	0000	0000
 0	 0	4000	0000	1000	config_rom: offset 0E
 1	 2	0063	DC10	00DC	(GUID)		   0C
 2	 4	0100	FD00	0101			   12
 3	 6	D0D4	8F75	F2D4			   10

 4	 8	0404	0404	0404	values same on all machines
 5	 A	5532	5532	5532	
 6	 C	00F8	00F8	00F8	
 7	 E	02A2	02A2	02A2	
 8	10	00A1	00A1	00A1	
 9	12	6340	6340	6340	

The only difference (not counting GUID) is at address 0x11 (0x22
for I2C).
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.
-- 
Krzysztof Halasa

       reply	other threads:[~2007-10-16 20:21 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 [this message]
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
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=m3d4vebylw.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --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®