On Sun, 29 Aug 2004, Mauro Ziliani wrote: > Goodmorning. > My name is Mauro Ziliani, is write from Parma, and I'm and computer science > adviser. > I'm apologize in advance for my english: sometimes is terrible. > I hope to be clear in my questions. > > I'm in trouble because I don't understand what happen with my driver and > ohci core. > > I need to drive an USB device (Philips PUSBD12+Hitachi H8/3664) that has two > alternate setting of interface 0, configuration 0.
<...> > Now, if I setup the device to setting0 then to setting1 (i.e. without tx/rx > data in setting0) and I trasmit data on EP2OUT Interrput all works well , > i.e. the EP2OUT interrupt completion handler is thrown regulary, and the > "close" syscall (release function in the driver) doesn't lock the calling > process. > > I'm working with 2.4.23 kernel and gcc 3.2.2. > > Why this strange OHCI behavior? > > Thanks a lot, even if you cannot help me. I would guess that the 2.4.23 kernel doesn't tell the OHCI controller that the endpoint has changed from bulk to interrupt and that the maxpacket size has changed. Why are you using 2.4.23 instead of 2.6.8? The newer kernel will probably work much better. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
