Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935899AbXJPVHd (ORCPT ); Tue, 16 Oct 2007 17:07:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S935005AbXJPVG7 (ORCPT ); Tue, 16 Oct 2007 17:06:59 -0400 Received: from einhorn.in-berlin.de ([192.109.42.8]:41720 "EHLO einhorn.in-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934153AbXJPVG5 (ORCPT ); Tue, 16 Oct 2007 17:06:57 -0400 X-Envelope-From: stefanr@s5r6.in-berlin.de Message-ID: <471527E5.1050407@s5r6.in-berlin.de> Date: Tue, 16 Oct 2007 23:06:45 +0200 From: Stefan Richter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20070807 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Krzysztof Halasa CC: linux1394-user@lists.sourceforge.net, lkml Subject: Re: VIA VT6307 OHCI version? References: <4714EF01.2060609@s5r6.in-berlin.de> In-Reply-To: X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 874 Lines: 21 Krzysztof Halasa wrote: > Both VT6306 and VT6307 datasheets claim selectable OHCI 1.0/1.1. > I guess they did that for compatibility or something like that. I wouldn't read too much into these data sheets. Note that actual OHCI 1.1 features are nowhere documented in these data sheets; i.e. this documentation can't be trusted to begin with. As far as VT6306 is concerned, the wording could be copy'n'waste from the VT6307 datasheet. And in case of VT6307, I suspect it's VIA who selects the implementation level (based on chip revision), not the card vendor. -- 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/