Date: Mon, 21 Nov 2011 10:09:37 -0700 From: Warner Losh <imp@bsdimp.com> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-hackers@FreeBSD.org, FreeBSD-Current <freebsd-current@FreeBSD.org> Subject: Re: Reprobing of devices after module load? Message-ID: <8D7CE344-05B3-4A48-8E5B-91100A48F0B1@bsdimp.com> In-Reply-To: <201111211126.15627.jhb@freebsd.org> References: <CAPYw7P6nqLmdRqa2Szntnac5pc3otf75cfGkCvVz1FoazssU%2Bg@mail.gmail.com> <201111211126.15627.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 21, 2011, at 9:26 AM, John Baldwin wrote: > On Friday, November 18, 2011 11:48:20 am Paul B. Mahol wrote: >> Hi, >>=20 >> Is there nice way in FreeBSD to force reprobe of devices for specific >> driver like it is done when kernel module is loaded (via >> DRIVER_MODULE(...) stuff)? >=20 > Note that those probes happen for specific buses rather than for = specific=20 > drivers. The routine that does this currently is static=20 > (devclass_driver_added() in sys/kern/subr_bus.c). What specific = problem are=20 > you trying to solve? You might be able to use BUS_DRIVER_ADDED() or=20= > device_probe_and_attach() to achieve what you are trying to do. You can load a dummy module that has an attach point to the bus that = you're wanting to force a rescan on. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8D7CE344-05B3-4A48-8E5B-91100A48F0B1>