On Fri, 14 May 2004 15:08:30 -0500 Al Borchers <[EMAIL PROTECTED]> wrote:
> > This late in the 2.4 development cycle, I don't really know. If it > > fixes real bugs, probably. Otherwise I doubt it. > > As we have talked about before, the semaphore in usbserial write leads > to an oops if the semaphore is held and write is called on interrupt > time. Remember, write can be called from an interrupt under certain > circumstances and you can't use semaphores then. Please rerun your tests on 2.4.26 and report me the results. I worked around this problem for 2.4 already, so it's not an issue anymore. The 2.4 could stand porting some elements of usb-serial from 2.6, we discussed it just this week (e.g. the removal of __serial_close from the disconnect path). But that's entirely separate. -- Pete ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
