From owner-freebsd-current@FreeBSD.ORG Sat Oct 30 19:33:15 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 6873816A4CE for ; Sat, 30 Oct 2004 19:33:15 +0000 (GMT) Received: from s1tank.virtdom.com (s1tank.virtdom.com [12.26.83.50]) by mx1.FreeBSD.org (Postfix) with SMTP id B845843D2D for ; Sat, 30 Oct 2004 19:33:14 +0000 (GMT) (envelope-from brian@aljex.com) Received: (qmail 3060 invoked by uid 89); 30 Oct 2004 19:33:23 -0000 Received: from ool-43552092.dyn.optonline.net (HELO venti) (brian@aljex.com@67.85.32.146) by s1tank.virtdom.com with SMTP; 30 Oct 2004 19:33:23 -0000 Message-ID: <02ed01c4beb7$4b45ba50$6400000a@venti> From: "Brian K. White" To: References: <20041029075930.GG701@marvin.riggiland.au><20041029080817.GB728@empiric.icir.org> <200410291511.24063.michaelnottebrock@gmx.net> Date: Sat, 30 Oct 2004 15:32:17 -0400 Organization: Aljex Software MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-15"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 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 19:33:15 -0000 > On Friday, 29. October 2004 10:08, Bruce M Simpson wrote: > > On Fri, Oct 29, 2004 at 09:59:30AM +0200, Thomas E. Zander wrote: > > > I'm just wondering why ehci doesn't make it into GENERIC for RELENG_5. > > > Are there unresolved show stoppers related to it? > > > > ehci(4) is not stable code and fails reproducibly with my ALi-based > > USB2 disk enclosure. > > Well, if we would take stability and general usefulness (even more so in > comparison to other USB implementations in mind) as the reference point, > we > would need to disable most of USB. I think enabling ehci in GENERIC would > be > a good idea, especially since there's no loadable module... I think that since it can't be unloaded and can crash or lock up a box before the kernel even finishes booting, that this idea is absolutely backwards. You like it and it happens to work ok for you with the devices you just happen to currently use, and you want it to be more convenient for you to use it? Fine, make it into a module. Still keep it off by default but you could then put a nice easy little line in your loader.conf and no one else will have to answer questions like why did they put something into the generic kernel that stops some people from being able to even boot the install cd anymore? Ask me how I know. Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/ +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani