From owner-freebsd-doc@FreeBSD.ORG Mon Jun 2 10:09:46 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 805F337B401; Mon, 2 Jun 2003 10:09:46 -0700 (PDT) Received: from tweedledee.esatclear.ie (tweedledee.esatclear.ie [194.145.128.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA60343F3F; Mon, 2 Jun 2003 10:09:45 -0700 (PDT) (envelope-from aecolley@spamcop.net) Received: from [194.165.171.202] (helo=cornerstone.colley.ie) by tweedledee.esatclear.ie with esmtp (Exim 4.14) id 19MsoZ-0006zH-Jz; Mon, 02 Jun 2003 18:09:44 +0100 Received: by cornerstone.colley.ie (Postfix, from userid 1001) id 475051A3; Mon, 2 Jun 2003 18:04:35 +0100 (IST) Date: Mon, 2 Jun 2003 18:04:35 +0100 From: Adrian Colley To: "Bruce A. Mah" Message-ID: <20030602170434.GA321@cornerstone.colley.ie> References: <20030528205016.GA1214@cornerstone.colley.ie> <200305291450.h4TEoB9c084898@bmah.dyndns.org> <20030529194910.GA321@cornerstone.colley.ie> <200305301500.h4UF0o9c093116@bmah.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200305301500.h4UF0o9c093116@bmah.dyndns.org> User-Agent: Mutt/1.4.1i cc: doc@freebsd.org Subject: Re: Suggestions for HARDWARE.TXT X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2003 17:09:46 -0000 On Fri, May 30, 2003 at 08:00:50AM -0700, Bruce A. Mah wrote: >>> Any idea if this device works with CURRENT also? >> I don't have a sufficiently current -CURRENT to immediately try it out. >> 5.0-RELEASE is the closest I have until I go for another cvsup run, and >> it behaves as 4.8 does above. I'll send an update when I get -current. > Actually, if it worked on 5.0-RELEASE, that's probably close enough. > It'd be interesting to see at some point if 5.1-RELEASE probes the card > as a USB 2.0 device (it should). I just tried it with -current (cvsupped 2003-05-31, 5.1-BETA). Once the kernel is compiled with `device ehci', the verbose boot messages include these: ehci0: mem 0xfedfdc00-0xfedfdcff irq 11 at device 14.2 on pci0 ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0,usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: NEC EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 3 ports with 3 removable, self powered So it looks like it does indeed treat it as a USB 2.0 device. However, the stock GENERIC kernel doesn't have ehci included, and so it attaches only the USB-1.0 ohci0 driver. > OK. I'm probably going to defer this until after 5.1-RELEASE. (I'm > trying to reduce the churn in the release documentation because this > creates last-minute work for the translation teams.) I can do this > anytime after the release though. If you don't see this go in within a > week or two after the release, can you send me a ping? (Alternatively, > file a doc PR and send me the number.) OK. --Adrian.