Date: Sun, 26 Jun 2011 11:51:51 -0600 From: Warner Losh <imp@bsdimp.com> To: Robert Millan <rmh@debian.org> Cc: Jeremy Messenger <mezz.freebsd@gmail.com>, freebsd-current@FreeBSD.org, Hans Petter Selasky <hselasky@c2i.net> Subject: Re: Automatic load of PCI kernel modules [WAS: [RFT] Automatic load of USB kernel modules] Message-ID: <B9BDB3DC-7F3C-4D4E-AEA6-3AD36409D2CD@bsdimp.com> In-Reply-To: <BANLkTikdww3jDM_ennzjFHKmKU0WrDBDHA@mail.gmail.com> References: <201106242342.47194.hselasky@c2i.net> <ACCD2B48-1E78-42B6-883E-542FDFD567F6@bsdimp.com> <201106251907.02052.hselasky@c2i.net> <201106260738.21847.hselasky@c2i.net> <BANLkTikdww3jDM_ennzjFHKmKU0WrDBDHA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 26, 2011, at 4:33 AM, Robert Millan wrote: > 2011/6/26 Hans Petter Selasky <hselasky@c2i.net>: >> Hi, >>=20 >> I see that a lot of PCI device drivers use code to check their ID's. >>=20 >> [...] >=20 > I seem to recall devd doesn't process PCI because it is event-driven = and > there are no "events" associated with PCI cards. That's totally false. > Perhaps it could be modified to scan for PCI cards via libpci on = initialization > and generate "fake" events for them? Since your premise is false, this solution also is false. Devices are handled in a completely uniform manner in the system. When = they attach, an attach even is generated. When they detach, a detach = event is generated. When there is no driver attached after the = probe/attach sequence, a NOMATCH event is generated. Events are queued = up during the early boot process until devd can run. They are then = processed in order. Devices that haven't had a driver attach to them = would be processed when devd had a chance to start. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B9BDB3DC-7F3C-4D4E-AEA6-3AD36409D2CD>