> I have another problem and perhaps you can help me. > When I first try to load my driver, everything goes right. But if I > unload it and try to reload it, I get errors. A few days ago, it wasn't > able to read the correct chip id, but now, after I used some mdelays in > IO as you told me to, it manages to read ChipID and fails at writing > Scratch and reading it back. If you recall, there is a pattern written > and then read back, followed by the same procedure with the pattern > being reversed. Well, when it writes and then reads Scratch for the > first time, I get the second value (left from the previous load of the > driver) and it obviously fails to go on!
Sounds like there are still delays missing. Olav ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
