From owner-freebsd-current@FreeBSD.ORG Sat Oct 30 18:14:50 2004 Return-Path: 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 1475E16A4CE for ; Sat, 30 Oct 2004 18:14:50 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id B928B43D2F for ; Sat, 30 Oct 2004 18:14:49 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 4E20EF186D; Sat, 30 Oct 2004 11:14:49 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20234-08; Sat, 30 Oct 2004 11:14:44 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 1C805F1837; Sat, 30 Oct 2004 11:14:44 -0700 (PDT) From: Sean McNeil To: Gary Jennejohn In-Reply-To: <200410300907.i9U97plE004694@peedub.jennejohn.org> References: <200410300907.i9U97plE004694@peedub.jennejohn.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ESpI1HXd2EO+Oq3yyKi3" Message-Id: <1099160083.21798.5.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 30 Oct 2004 11:14:44 -0700 X-Virus-Scanned: by amavisd-new at mcneil.com 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Oct 2004 18:14:50 -0000 --=-ESpI1HXd2EO+Oq3yyKi3 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2004-10-30 at 02:07, Gary Jennejohn wrote: > Sean McNeil writes: > > What I am wondering about is why I get ehci in my kernel when I do not > > ask for it: > 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. OK, thanks. Looks like it isn't really in the kernel. I made a build with adding "device ehci" and I think "pci/ehci" is the actual device, not "ehci/usb". Sorry for the noise. FWIW, using ehci doesn't cause me any additional issues with USB. My umass pen drive behaves the same with/without ehci except it is faster.=20 This makes me think that my previous issues are with the msdos filesystem, not the usb driver. Cheers, Sean --=-ESpI1HXd2EO+Oq3yyKi3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBg9oTyQsGN30uGE4RAoasAJ9oFNVc3RTXL6HmyKy1/49IWSaOcgCg8NB+ 5CJbqtLlJ01B1+53cJ0gzd4= =hag3 -----END PGP SIGNATURE----- --=-ESpI1HXd2EO+Oq3yyKi3--