Re: [PATCH] Airprime driver improvements to allow full speed EvDOtransfers

[Jeremy Fitzhardinge]

Andy Gay wrote:
> BTW - Jeremy suggested that the number of EPs to configure should be
> determined from the device ID. Makes sense to me, but then many users
> may have no use for the additional EPs. Alternatively, Greg suggested
> that maybe this should split into 2 drivers. Any preferences, anyone?
>   
I think if the hardware has the EPs, they should be exposed by the 
driver.  You can tweak usermode as to whether they get device nodes, 
what they're called, etc.
> I don't know which of these devices present multiple EPs though. Can you
> send me the appropriate section from 'cat /proc/bus/usb/devices'?
>   
Phil Karn mentions on http://www.ka9q.net/5220.html:

   It may help to know what's actually inside the 5220 card. It
   contains a Qualcomm MSM 5500 mobile station modem chip that
   implements the actual 1xEV-DO functionality. This chip has a native
   USB 1.1 interface that emulates two USB serial ports. The first
   provides a classic serial modem interface that accepts AT commands
   and PPP data. The second is reserved for diagnostics and is unused.

For completeness:

T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1199 ProdID=0218 Rev= 0.01
S:  Manufacturer=Sierra Wireless
S:  Product=Sierra Wireless MC5720 Modem
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 7 Cls=ff(vend.) Sub=ff Prot=ff Driver=airprime
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=128ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=84(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=85(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=05(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms


   J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/