From owner-freebsd-usb@FreeBSD.ORG  Sat Feb  5 17:23:19 2005
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
Delivered-To: freebsd-usb@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 69ECC16A4CE
	for <freebsd-usb@freebsd.org>; Sat,  5 Feb 2005 17:23:19 +0000 (GMT)
Received: from mailfe10.swip.net (mailfe10.swipnet.se [212.247.155.33])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3768F43D1D
	for <freebsd-usb@freebsd.org>; Sat,  5 Feb 2005 17:23:18 +0000 (GMT)
	(envelope-from hselasky@c2i.net)
X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw==
Received: from mp-216-41-27.daxnet.no ([193.216.41.27] verified)
  by mailfe10.swip.net (CommuniGate Pro SMTP 4.2.7)
  with ESMTP id 81917949; Sat, 05 Feb 2005 18:23:16 +0100
From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org, Eugene Rogoza <euro@i.com.ua>
Date: Sat, 5 Feb 2005 18:23:46 +0100
User-Agent: KMail/1.7
References: <002701c50b96$d43525e0$8b33bb81@beast1000>
In-Reply-To: <002701c50b96$d43525e0$8b33bb81@beast1000>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200502051823.47280.hselasky@c2i.net>
Subject: Re: USB does not recognize any dynamically plugged devices -
	problem fixed
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: hselasky@c2i.net
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Feb 2005 17:23:19 -0000

On Saturday 05 February 2005 16:24, Eugene Rogoza wrote:
> > uhci0: <Intel 82801DB (ICH4) USB controller USB-A> port 0x1820-0x183f irq
> > 11 at device 29.0 on pci0
> > uhci0: [GIANT-LOCKED]
> > usb0: <Intel 82801DB (ICH4) USB controller USB-A> on uhci0
> > usb0: USB revision 1.0
> > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub0: 2 ports with 2 removable, self powered
> > uhci1: <Intel 82801DB (ICH4) USB controller USB-B> port 0x1840-0x185f irq
> > 10 at device 29.1 on pci0
> > uhci1: [GIANT-LOCKED]
> > usb1: <Intel 82801DB (ICH4) USB controller USB-B> on uhci1
> > usb1: USB revision 1.0
> > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub1: 2 ports with 2 removable, self powered
> > uhci2: <Intel 82801DB (ICH4) USB controller USB-C> port 0x1860-0x187f irq
> > 10 at device 29.2 on pci0
> > uhci2: [GIANT-LOCKED]
> > usb2: <Intel 82801DB (ICH4) USB controller USB-C> on uhci2
> > usb2: USB revision 1.0
> > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub2: 2 ports with 2 removable, self powered
>
> Dear all,
>
> To be able to detect USB devices after system startup one has to compile
> "device ehci" into kernel along with "device ohci" or "device uhci".
> Actually it may work without EHCI for a while (as it was with me), but
> further there is no guarantee.
>
> There is no string "device ehci" even in GENERIC kernel, so I guess one
> should be kept aware of turning this feature on either by some notice or by
> including that string into GENERIC configuration file in future releases.

The reason for not having "device ehci" in GENERIC was something about missing 
support for USB2.0 HUBs. When one has got a USB2.0 HUB and "device ehci" in 
the kernel config file, then the HUB will probe as USB2.0, which is not 
supported for HUBs, else USB1.x. So maybe your problem is a reason to push 
support for USB2.0 HUBs?

Yours
--HPS