Date: Thu, 9 Oct 2008 14:22:51 +0200 From: Rink Springer <rink@FreeBSD.org> To: Andriy Gapon <avg@icyb.net.ua> Cc: freebsd-arch@freebsd.org Subject: Re: Modular ata chipsets data Message-ID: <20081009122251.GB89052@rink.nu> In-Reply-To: <48EDF045.8030604@icyb.net.ua> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081009122251.GB89052>