On Fri, 3 Dec 2004, Per-Arne Söderkvist wrote:

> Hello Alan!
> 
> Thank's for your quick answer. Seems that we have to update our kernel as
> you said, to get a "good" solution. When we test your proposed solution with
> the kernel mentioned above we got the following message
> "Dec  3 16:11:11 localhost kernel: oh: dis_usb.c, ioctl USBDEVFS_RESET
> Dec  3 16:11:11 localhost kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000178". Do you think is because of "old"
> kernel or is it any other reason?

I don't know, but I wouldn't try using that ioctl with anything below 
2.6.9.

> We are also testing a "raw" solution that seems to do the work, approx to do
> the things what happens when "hotplugged", see below:
> 
> 1. rmmod "our usb-module"
> 2. insmod "our usb-module"
> 3. chmod 777 /udev/"our dev"
> 4. fxload -I "our hex-file" -D `ls -1 /proc/bus/usb/*/* | grep -v 001`

If that works, then good.  But you shouldn't have to unload and reload 
your module.  (In fact, you didn't even mention before that you were using 
a kernel module.)

Alan Stern



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to