Re: sierra gpl driver backport

Alan Stern <[email protected]>
Newsgroups gmane.linux.usb.devel
Message-ID <[email protected]>
On Tue, 11 Sep 2007, Anthony Tzouris wrote:

> Working on a project in which I need to backport the GPL Sierra Wireless
> Cell Modem driver.  The platform an ARM9 linux 2.6.5 kernel with a linux
> kernel 2.6.9 usb subsystem backport.  There is no option to upgrade the
> kernel on this project.
> 
> The sierra driver needs to be backported from linux kernel version
> 2.6.21 to 2.6.5.  I have tested the backport on the ARM9 and x86 linux
> 2.6.5 kernels and get similar results of the 3 usb-to-serial devices
> /dev/ttyUSB0, USB1, and USB2 being enumerated but the driver does not
> communicate serially to the cell modem through the /dev/ttyUSBx serial
> device.  On the ARM9 platform I end up getting three warnings in the USB
> Host Controller:
> 
> got unlink
> aborting urb
> aborted running urb
> 
> that ends up with the following warning message in the sierra driver:
> 
> sierra_indat_callback: nonzero status: -2 on endpoint
> 
> I did attempt to track down the -2 status (urb->status) but did not find
> anything in the kernel tree.
> 
> Does anyone with usb development experience from early to current 2.6.x
> linux usb development know generally what the cause of this problem
> might be?

-2 is -ENOENT (as defined in include/asm-generic/errno-base.h).  

According to Documentation/usb/error-codes.txt, -ENOENT in urb->status 
means that the URB was synchronously unlinked.

Alan Stern


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.