From owner-freebsd-arch@FreeBSD.ORG Thu Jan 4 18:22:30 2007 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 82B9416A415 for ; Thu, 4 Jan 2007 18:22:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 0B20013C448 for ; Thu, 4 Jan 2007 18:22:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l04HjGsK031320; Thu, 4 Jan 2007 12:45:16 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-arch@freebsd.org Date: Thu, 4 Jan 2007 11:21:01 -0500 User-Agent: KMail/1.9.1 References: <20070101.113801.818271922.imp@bsdimp.com> <20070103205841.GB85200@roadrunner.q.local> In-Reply-To: <20070103205841.GB85200@roadrunner.q.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701041121.02455.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 04 Jan 2007 12:45:16 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2413/Thu Jan 4 04:46:27 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Ulrich Spoerlein Subject: Re: usb modems and com devices into GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2007 18:22:30 -0000 On Wednesday 03 January 2007 15:58, Ulrich Spoerlein wrote: > M. Warner Losh wrote: > > I'd like to place the following in GENERIC. We're getting more and > > more questions about these devices that we wouldn't be getting if we > > had them compiled in by default. The really imporant ones are marked > > with a '*' below > > > > device ucom # * > > device umodem # * > > device umct > > device uark > > device ubsa > > device ubser > > device uftdi # * > > device uplcom # * > > device uvisor > > device uvscom > > > > the cost isn's so much, and we can filter them out from the > > installation kernel if size is an issue. > > > > Comments? > > Hi Warner, > > why not do it the other way round? Keep them out of GENERIC, but have > loader(8) load some of the most used modules (snd_driver!) per default. > > That way, people can easily disable these (without needing to > recompile). > > I mean, what point is there in the whole KLD infrastructure, if we are > going to add every device into GENERIC anyway? It works great when you are developing a driver that lives in a module. :) The point is to give people tools to use, it's up to different people to use them as they see fit. I pretty much never use kernel modules (except for either working on a driver or test modules I write) but use static kernels since kernel debugging tends to be simpler when you avoid modules. It can also be a larger pain to manage if you are administering a lot of machines. You also then have the extra task of making sure kernel and modules are always in sync ABI-wise (a static kernel is always self-consistent). -- John Baldwin