From owner-freebsd-arch@FreeBSD.ORG Thu Oct 9 12:09:12 2008 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53C8F10656A6; Thu, 9 Oct 2008 12:09:12 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id 0292E8FC23; Thu, 9 Oct 2008 12:09:11 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id 62B1743C504; Thu, 9 Oct 2008 14:51:36 +0300 (EEST) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HFUGC1IIxb6V; Thu, 9 Oct 2008 14:51:36 +0300 (EEST) Received: from [10.2.1.87] (gateway.cybervisiontech.com.ua [91.198.50.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 7872E43C555; Thu, 9 Oct 2008 14:51:34 +0300 (EEST) Message-ID: <48EDF045.8030604@icyb.net.ua> Date: Thu, 09 Oct 2008 14:51:33 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20080929) MIME-Version: 1.0 To: John Baldwin References: <48E6D21E.8040808@bluezbox.com> <48E7AE7D.6020709@bluezbox.com> <8C0B1202-5DF8-45CF-82EA-03367BFABAE7@FreeBSD.ORG> <200810081743.45011.jhb@freebsd.org> In-Reply-To: <200810081743.45011.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Modular ata chipsets data 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, 09 Oct 2008 12:09:12 -0000 on 09/10/2008 00:43 John Baldwin said the following: > What happens with mii is that you have a choice, you can either use 'device > miibus' in which case you get all of the various drivers and the > infrastructure, or you can use 'device mii', 'device rlphy', etc. if you wish > to take a more fine-grained approach. Similarly, there is a miibus.ko that > just depends on all the sub-drivers so you can still do 'kldload miibus.ko' > to load all of them. I think this is probably a fine model as it will still > load everything by default, but people who care about the space savings can > trim things down as desired. Sorry for hijacking the thread but is this documented anywhere? On RELENG_7 system I couldn't find the above info in NOTES and miibus(4), only device miibus is referred to. -- Andriy Gapon