Hello, I have borrowed Greg's changes in the Visor USB serial driver (2.5.x kernel) that replaces a fixed pool of write urbs with dynamically allocated write urbs, I want to use the same technique in the ftdi_sio driver.
A simple 'dd' command to write several seconds worth of data to the serial port now returns pretty much instantly (because the 'chars_in_buffer' function pretends the data is already flushed). This leaves plenty of time to 'rmmod' the driver module while the data is still being transmitted, but this causes an Oops, presumably when the callback function gets called on completion of an urb. I'm a newbie as far as the 2.5.x kernel is concerned, but MOD_INC... and MOD_DEC... seem to be frowned upon now, so what's the best way around this problem? I'm guessing it happens in the Visor driver too? -- -=( Ian Abbott @ MEV Ltd. E-mail: <[EMAIL PROTECTED]> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=- ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
