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 for Android: free password hash cracker in your pocket

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

Message-ID: <m3bqausztv.fsf@maximus.localdomain>
Date:	Sat, 20 Oct 2007 15:03:24 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	linux1394-user@...ts.sourceforge.net,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: VIA VT6307 OHCI version?

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

> What if we add a whitelisting in the driver which ignores the register
> contents which state OHCI 1.0 implementation level, and just treats
> these VIA chips as OHCI 1.1 implementations?

It would be interesting but I'm not sure it would work. I guess
if these chips are in OHCI 1.0 mode the 1.1 functionality may be
unavailable (the datasheet seems to suggest that).

OTOH I think it's better to change the EEPROM contents anyway,
it's a simple program (which I'm going to write when I'm a bit
less loaded).

I wonder if OHCI 1.0 hardware based on VT6307 (and 6306) is
a common thing, or is it just an exception.
-- 
Krzysztof Halasa
-
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/