On Fri, Jun 16, 2006 at 08:05:20PM +0400, Sergei Organov wrote: > Greg KH <[EMAIL PROTECTED]> writes: > > > On Tue, Jun 13, 2006 at 02:42:38PM +0400, Sergei Organov wrote: > >> Greg KH <[EMAIL PROTECTED]> writes: > [...] > >> > I've posted some patches here for the airprime driver that should be > >> > able to saturate the USB bus as fast as the device can handle. If you > >> > could test that patch, with your device id, I would appreciate it. > >> > >> What patch? I've looked through the mailing list for "airprime", but > >> don't know which of the posts I found you mean. Do I just take some > >> recent kernel (which one?) and modprobe airprime (with my IDs) instead > >> of usbserial? > > > > This patch: > > > > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-04-usb/airprime_major_update.patch > > I've applied the patch to the 2.6.16.8 kernel tree, then added my > vendor/product IDs to the id_table. Now the driver is loaded OK, > /dev/ttyUSB0 is created, but I can't open the port with a weird errno: > > osvr:/usr/src/linux# cat /dev/ttyUSB0 > cat: /dev/ttyUSB0: Message too long > > and enabled debug output from the driver (modprobe airprime debug=1) > gives: > > osvr:/usr/src/linux# dmesg | grep airprime > drivers/usb/serial/airprime.c: airprime_open - port 0 > airprime ttyUSB0: airprime_open - failed submitting read urb, error -90 > osvr:/usr/src/linux# > > When modprobing usbserial with my ids, the /dev/ttyUSB0 works OK. > > Any idea what's wrong?
No, others have also reported this problem, while it doesn't seem to bother some at all. I'll look into it. thanks, greg k-h _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
