Date: Sun, 2 Apr 2000 21:19:41 +0100 (BST) From: Nick Hibma <n_hibma@calcaphon.com> To: Warner Losh <imp@village.org> Cc: Nikolai Saoukh <nms@otdel-1.org>, freebsd-hackers@freebsd.org Subject: Re: Reserving Resources Message-ID: <Pine.BSF.4.20.0004022113120.604-100000@localhost> In-Reply-To: <200003270518.WAA89979@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> In theory, if one matches with a -1 or smaller rather than 0, then it > will be detached on reprobe. Isn't that the case? On -newbus this issue has come up and the conclusion was that there is always some problem rearing its ugly head. On loading a new driver you would have to run a non-intrusive probe on the device (if at all possible, some USB devices won't let you do that), the driver needs to detach (if possible, what if they attached to a CAM SIM which you should not delete) and the new driver needs to attach and initialise the device (if possible, what about ISA cards that freeze if you treat them the wrong way?). The issue is pretty hairy and for now I think the solution is to make any stub use DEVICE_NOMATCH (see pci.c), which does not attach a driver to a device, just mentions it during boot. I have no idea however whether this can be done with the unknown driver Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.0004022113120.604-100000>