Hello Reinhard, thanks for the hint, that did the trick. Dynamically adding the USB IDs didn't work, however, I've rebuilt qcserial with the added ID and now it works as expected. Should I send a patch adding the ID? Florian On So, 2011-08-07 at 16:43 +0200, Reinhard Speyerer wrote: > Florian Echtler <floe-H5Ww8s0cz1NjHglVgfe8mg@xxxxxxxxxxxxxxxx> wrote: > > However, it seems I can't yet talk to them via minicom. Can anybody give > > me some hints/background info on this device? > [replying directly since I am not subscribed to the linux-usb mailing list] > > Hi Florian, > > since this device is described by Sierra Wireless as having a Gobi API > you might have better luck using > modprobe qcserial > followed by > echo "1199 9011" > /sys/bus/usb/drivers/qcserial/new_id > if the corresponding USB VID/PID is not part of the standard entries for > qcserial.ko in 2.6.38. > > Please note that using pppd for higher HSPDA speeds might be a bottleneck. > Gobi devices also seem to provide a USB network interface to get around > this problem. AFAIK due to various reasons the corresponding driver > is not (yet?) part of the standard Linux kernel. > > Regards, > Reinhard >
Attachment:
signature.asc
Description: This is a digitally signed message part
