Re: [linux-usb-devel] disconnect called after driver deregister!!

2002-05-24 Thread David Brownell
> - in the module's cleanup routine, i unregister the usb device > which causes the diconnect routine to be > invoked(with the device still attached) If you unregister the _driver_ that'd be correct. And I'm hoping that your disconnect() routine actually gets rid of all hooks that your

Re: [linux-usb-devel] disconnect called after driver deregister!!

2002-05-24 Thread Avinash natarajan
ot;Because i live in a large tin can and i work in an egg carton Flirting is the only joy i have:)" - Original Message - From: David Brownell To: Avinash natarajan Cc: [EMAIL PROTECTED] Sent: Friday, May 24, 2002 8:25 PM Subject: Re: [linux-usb-devel] d

Re: [linux-usb-devel] disconnect called after driver deregister!!

2002-05-24 Thread David Brownell
> I have my usb driver as a linux module. the problem i have is this - > i forcefully remove the module when the usb > device is attached... Presumably you mean "detached"? > a proper cleanup happens and the device is > unregistered succesfully... That should happen regardless of wheth

[linux-usb-devel] disconnect called after driver deregister!!

2002-05-22 Thread Avinash natarajan
Hi...     I have my usb driver as a linux module. the problem i have is this - i forcefully remove the module when the usb device is attached...a proper cleanup happens and the device is unregistered succesfully...but the problem is even after doing this, removal of device causes a core du