Date: Thu, 21 May 2009 14:40:43 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: phk@phk.freebsd.dk Cc: scottl@samsco.org, src-committers@FreeBSD.org, jhb@FreeBSD.org, svn-src-all@FreeBSD.org, attilio@FreeBSD.org, svn-src-head@FreeBSD.org, rwatson@FreeBSD.org, kostikbel@gmail.com Subject: Re: svn commit: r192535 - head/sys/kern Message-ID: <20090521.144043.-501541558.imp@bsdimp.com> In-Reply-To: <2070.1242926222@critter.freebsd.dk> References: <20090521.101537.864824728.imp@bsdimp.com> <2070.1242926222@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <2070.1242926222@critter.freebsd.dk>
"Poul-Henning Kamp" <phk@phk.freebsd.dk> writes:
: In message <20090521.101537.864824728.imp@bsdimp.com>, "M. Warner Losh" writes:
:
: >Right now, the devctl_notify() is what gets it into devd. However,
: >I'd always viewed devd as having multiple event sources and not just
: >from the /dev/devctl device.
:
: Correct, but kqueuing /dev is not nearly as expressiv as devctl,
: where the protocol has space where the device driver could pass
: useful information to devd(8).
It could, but right now it doesn't.
: For instance, I find the regexp matching of ethernet drivers very,
: very silly: the device driver should just tell devd(8) that it is
: an ethernet, so that we don't have this non-documented registry of
: device driver names.
We don't use the ethernet driver regex any more, since we base it all
on interface arrival in ifnet layer...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090521.144043.-501541558.imp>