Date: Mon, 19 Jul 2004 16:35:36 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: pjd@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: Unloading USB driver while device is attached. Message-ID: <20040719.163536.81896269.imp@bsdimp.com> In-Reply-To: <20040719173819.GI57678@darkness.comp.waw.pl> References: <20040719145745.GH57678@darkness.comp.waw.pl> <20040719102139.N59702@carver.gumbysoft.com> <20040719173819.GI57678@darkness.comp.waw.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20040719173819.GI57678@darkness.comp.waw.pl>
Pawel Jakub Dawidek <pjd@freebsd.org> writes:
: On Mon, Jul 19, 2004 at 10:23:16AM -0700, Doug White wrote:
: +> Theres a discussion going on in -arch about making kldunload a bit more
: +> careful about cleaning up before detaching. In the interim adding a
: +> method that just vetos any unload request would prevent this from
: +> occuring, but also preclude unloading the driver. :)
:
: Yeah, but even on 'kldunload -f' it should be possible to clean up
: and avoid panic on next load.
kldunload -f isn't supported at this point :-) Or more accurately,
there's no hook into the driver system (newbus). And even if there
was, usb has been poorly integrated into newbus in the past, so it
likely still would do bad things. Eg, -f isn't going to save you.
umass should be fixed.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040719.163536.81896269.imp>