In message <Pine.NEB.3.96L.1050125143745.3036A-100000_at_fledge.watson.org>, Robert Watson writes: >We're really not interested >in the newbus announcement, since there are lots of network interfaces >that have no physical representation and so aren't visible to newbus. I think this is the crux of the matter. newbus events will mostly be able tell us that we need to load a driver kld. devfs events on the other hand tells us that something can be accessed from userland. Since we added /dev/net/* we have sort of collapsed the split we previously had where some devices did not appear in /dev. There are still virtualized cases though, adding more hardware under opencrypto comes to mind. I can't really turn that into an example where we need to do more than respond to newbus by loading the driver. But as I said in the other email, we should probably have devfs communicate the type of device to devd to save some rather complex code in userland. (The regexp matching all our ethernet drivers in devd.conf have always irritated me). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk_at_FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.Received on Tue Jan 25 2005 - 14:14:15 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:26 UTC