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)
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