From owner-freebsd-stable@FreeBSD.ORG Fri Aug 8 20:27:35 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7F4C37B401; Fri, 8 Aug 2003 20:27:35 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23A3943FBF; Fri, 8 Aug 2003 20:27:35 -0700 (PDT) (envelope-from b.j.casavant@ieee.org) Received: from abigail.msp.angeltread.org (c-24-245-17-149.mn.client2.attbi.com[24.245.17.149](untrusted sender)) by comcast.net (rwcrmhc12) with ESMTP id <2003080903273401400kdomre>; Sat, 9 Aug 2003 03:27:34 +0000 Received: from abigail.msp.angeltread.org (abigail.msp.angeltread.org [192.168.64.4]) by abigail.msp.angeltread.org (Postfix) with ESMTP id 8A134E; Fri, 8 Aug 2003 22:27:33 -0500 (CDT) Date: Fri, 8 Aug 2003 22:27:33 -0500 (CDT) From: Brent Casavant X-X-Sender: bcasavan@abigail.msp.angeltread.org To: Craig Boston In-Reply-To: <200307312340.45844.craig@meoqu.gank.org> Message-ID: <20030808220952.W898@abigail.msp.angeltread.org> References: <200307312340.45844.craig@meoqu.gank.org> Organization: "Angeltread Software Organization" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-gnats-submit@FreeBSD.org cc: freebsd-stable@FreeBSD.org Subject: Re: kern/55094: Intel USB 2.0 unrecognized (partial patch provided) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Brent Casavant List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Aug 2003 03:27:36 -0000 Craig, Sorry for the incredibly late response. General busyness you know. On Thu, 31 Jul 2003, Craig Boston wrote: > If it's the USB 2.0 controller that's isn't being detected, shouldn't ehci by > patched instead of uhci...? You may want to give the attached, completely > untested, patch a try. I.e. it compiles on my box, but I don't have any > hardware to actually test it on yet. Might theoretically work depending on > how closely Intel followed the EHCI spec. Note that the patch includes > entries for both the DB and EB variants of the chip. You are of course correct sir. See below. > I'm not sure why the code to pick up generic EHCI devices didn't find it > though. Ignorance mostly. This being the first machine I've ever had with USB on it, I wasn't aware that USB 2.0 was handled by EHCI instead of the OHCI or UHCI drivers (EHCI doesn't appear in the NOTES file and I didn't think to make LINT until just a few minutes ago). Once I configured EHCI into the kernel all was well, and with your patch it works swimmingly since it's even identified precisely. So I for one can confirm that the patch you gave does indeed work. Now if only I had the cash to buy a USB device to plug into the PC... Thanks, Brent Casavant -- Brent Casavant http://www.angeltread.org/ KD5EMB -.- -.. ..... . -- -... 44 54'24"N 93 03'21"W 907FASL EN34lv