Re: Buses, devices and modules
- From: "M. Warner Losh" <imp@xxxxxxxxxx>
- Date: Sat, 24 Jun 2006 19:16:59 -0600 (MDT)
In message: <922B6543-53D0-4877-9E97-B9ED1CDACFA8@xxxxxxx>
Artem Ignatiev <zazubrik@xxxxxxx> writes:
: When I do 'echo mydev_load="YES" >>/boot/loader.conf', loader loads
: both mydev.ko and mybus.ko, and mybus.ko attaches properly, but
: mydev.ko don't attach to anything.
:
: I suppose this happens because mydev happens to probe for devices
: before mybus creates them, and fails to find anything to attach to.
:
: I'm looking for way to trigger the mydev driver to re-probe after the
: mybus driver actually creates the devices, or may be I'm missing
: something simple (like priority of module probing)?
re-probing is automatic for all instances of bus FOO when a driver
that has a FOO attachment is loaded. If the FOO bus driver creates a
child device, then they are responsible for calling
device_probe_and_attach on it.
Warner
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"
- References:
- Buses, devices and modules
- From: Artem Ignatiev
- Buses, devices and modules
- Prev by Date: Re: mmap() vs. character special file
- Next by Date: Re: A New FreeBSD Server
- Previous by thread: Buses, devices and modules
- Next by thread: mmap() vs. character special file
- Index(es):
Relevant Pages
|
