linux-kernel - Re: VIA VT6307 OHCI version?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 17 Oct 2007 22:11:47 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Krzysztof Halasa <khc@...waw.pl>
CC:	linux1394-user@...ts.sourceforge.net,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: VIA VT6307 OHCI version?

Krzysztof Halasa wrote:
> Stefan Richter <stefanr@...6.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

What I meant was:  First revisions may have had incomplete OHCI 1.1
support and were sold as OHCI 1.0 chips, and as soon as they stabilized
it they sold them as OHCI 1.1 chips.  But that's mere speculation on my
part.  I can't think of any other reason though why anybody would hide
OHCI 1.1 compatibility.

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

And are you going to test if and how stable OHCI 1.1 features work?
(Which features are these?  Right now only dual buffer reception comes
to my mind.)
-- 
Stefan Richter
-=====-=-=== =-=- =---=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/