From owner-freebsd-arch@FreeBSD.ORG Thu Oct 9 12:39:55 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 2CA01106569F for ; Thu, 9 Oct 2008 12:39:55 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx1.rink.nu (gloom.rink.nu [213.34.49.2]) by mx1.freebsd.org (Postfix) with ESMTP id DFA788FC16 for ; Thu, 9 Oct 2008 12:39:54 +0000 (UTC) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx1.rink.nu (Postfix) with ESMTP id 5BE516D423; Thu, 9 Oct 2008 14:23:00 +0200 (CEST) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx1.rink.nu ([213.34.49.2]) by localhost (gloom.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id skojld8sIshr; Thu, 9 Oct 2008 14:22:51 +0200 (CEST) Received: by mx1.rink.nu (Postfix, from userid 1000) id DDCD06D41E; Thu, 9 Oct 2008 14:22:51 +0200 (CEST) Date: Thu, 9 Oct 2008 14:22:51 +0200 From: Rink Springer To: Andriy Gapon Message-ID: <20081009122251.GB89052@rink.nu> References: <48E6D21E.8040808@bluezbox.com> <48E7AE7D.6020709@bluezbox.com> <8C0B1202-5DF8-45CF-82EA-03367BFABAE7@FreeBSD.ORG> <200810081743.45011.jhb@freebsd.org> <48EDF045.8030604@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48EDF045.8030604@icyb.net.ua> User-Agent: Mutt/1.5.18 (2008-05-17) 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:39:55 -0000 On Thu, Oct 09, 2008 at 02:51:33PM +0300, Andriy Gapon wrote: > 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. I've once tried this. Adding modules for xxxphy is easy, but I found it rather difficult to isolate which NIC needs to depend on which phy (for example, you'll want if_rl to depend on rlphy - but this isn't obvious for all NIC/PHY combinations) Regards, -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder