From owner-freebsd-current@FreeBSD.ORG  Sat Oct 30 09:08:00 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7E35416A4CE
	for <freebsd-current@freebsd.org>;
	Sat, 30 Oct 2004 09:08:00 +0000 (GMT)
Received: from peedub.jennejohn.org (Jb8df.j.pppool.de [85.74.184.223])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B735243D1F
	for <freebsd-current@freebsd.org>;
	Sat, 30 Oct 2004 09:07:59 +0000 (GMT)
	(envelope-from garyj@jennejohn.org)
Received: from jennejohn.org (localhost [127.0.0.1])
	by peedub.jennejohn.org (8.13.1/8.11.6) with ESMTP id i9U97plE004694;
	Sat, 30 Oct 2004 11:07:55 +0200 (CEST)
	(envelope-from garyj@jennejohn.org)
Message-Id: <200410300907.i9U97plE004694@peedub.jennejohn.org>
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4
To: Sean McNeil <sean@mcneil.com>
In-Reply-To: Message from Sean McNeil <sean@mcneil.com> 
	<1099085184.28681.3.camel@server.mcneil.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 30 Oct 2004 11:07:51 +0200
From: Gary Jennejohn <garyj@jennejohn.org>
X-Mailman-Approved-At: Sat, 30 Oct 2004 12:12:50 +0000
cc: freebsd-current@freebsd.org
Subject: Re: EHCI considered harmful? 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Oct 2004 09:08:00 -0000


Sean McNeil writes:
> What I am wondering about is why I get ehci in my kernel when I do not
> ask for it:
> 
> server# grep ehci LINT
> LINT:device             ehci
> 
> So there is a config directive available...
> 
> server# grep hci AMD64
> AMD64:device            uhci            # UHCI PCI->USB interface
> AMD64:device            ohci            # OHCI PCI->USB interface
> 
> So I have not specified it...
> 
> server# kldstat -v | grep ehci
>                 135 ehci/usb
> 
> Yet it is in my kernel?
> 

No, this output most probably comes from this:

root:peedub:sys:bash:4> grep ehci ./dev/usb/usb.c
DRIVER_MODULE(usb, ehci, usb_driver, usb_devclass, 0, 0);

which AFAIK means that ehci could be loaded as a module.

The real way to check is by grep'ing /var/run/dmesg.boot which will
contain scads of messages about EHCI if it's in the kernel.

---
Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de