Date: Tue, 19 Jul 2005 09:28:50 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: phk@haven.freebsd.dk Cc: arch@freebsd.org, rwatson@freebsd.org Subject: Re: Network-related device drivers and MPSAFEty: status, and plans for 7.0 Message-ID: <20050719.092850.11989358.imp@bsdimp.com> In-Reply-To: <20050719.092044.41685623.imp@bsdimp.com> References: <20050718183717.N9430@fledge.watson.org> <1447.1121761910@phk.freebsd.dk> <20050719.092044.41685623.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20050719.092044.41685623.imp@bsdimp.com>
Warner Losh <imp@bsdimp.com> writes:
: > Some of the mii/phy drivers we have are specific to just one particular
: > network driver.
:
: I've been looking into listing the mii drivers to include in a given
: kernel. For the general case, we want to include them all. For
: specific cases, only a small subset are necessary. I don't think
: tying them to a specific driver is necessarily the right way to go, as
: old designs have a bad habit of reappearing in new when you least
: expect it.
BTW, explicit lists are much easier now that we can have something
like
include mii.all
in our config files. As for the modules, some thought and care is
necessary there, but I'm working on a long term build evolution for
modules that might make solving the mii problem easier. As I move
through the prototyping stage, I'll be posting some test patches. You
can watch the progress in p4.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050719.092850.11989358.imp>