<div dir="ltr"><div>Thanks for the response, great blog post ! Even for the Gobinet driver, for some devices like Pantech UML295, I dont even see them putting a linux gobi driver for that in their webpage .. Looks like other than netgear (ie old sierra wireless), no one seems to be really putting the vendor specific version of GobiNet driver on their website !! </div>Now in this whole scheme of things, where does the sierra_net.c stand ? I see that netgear packages sierra.c (serial) and sierra_net.c (direct ip) as their drivers for some of their models, and GobiNet as their driver for some other models. So is sierra.c and sierra_net.c the driver which was created before GobiNet and then later GobiNet became the standard vendor provided driver which provides the same functionality as sierra.c and sierra_net.c ? Also I see that the sierra_net.c is still used along with qmmi/cdc modules - I guess the sierra_net.c is used for the ethernet/data portion and qmmi/cdc is purely for management/control ? Rgds, Gopa. </div><div class="gmail_extra"> <div class="gmail_quote">On Fri, Aug 15, 2014 at 9:31 AM, Aleksander Morgado <<a href="mailto:aleksander@aleksander.es" target="_blank">aleksander@aleksander.es</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Fri, Aug 15, 2014 at 3:52 PM, Gopakumar Choorakkot Edakkunni <<a href="mailto:gopakumar.c.e@gmail.com">gopakumar.c.e@gmail.com</a>> wrote: > >>>> No, I Sierra Wireless do definitely test their Linux drivers. And they >>>> do provide support for them (in the embedded market). So the >>>> GobiSerial/GobiNet drivers *might* be the correct choice for some users, > > So does the Gobinet driver that I get for example from the Netgear AC340U > product page - does that work for ALL classes of Sierra devices or does > Netgear or other vendors (huawei etc..) put in their own fixes on top and > repackage it and put it on their website ? Or is there some other place > where qualcomm maintains a gobinet driver which is the latest and greatest > and supports netgear and huawei and pantech and etc.. etc.. ? </div>More or less on-topic, I wrote a blogpost about this not long ago: <a href="https://sigquit.wordpress.com/2014/06/11/qmiwwan-or-gobinet/" target="_blank">https://sigquit.wordpress.com/2014/06/11/qmiwwan-or-gobinet/</a> There is a 'qualcomm' GobiNet, in the CodeAurora project page, but every vendor keeps its own. E.g. Sierra will modify the stock GobiNet at least to add their specific VID/PID matches as well as their unique USB interface layouts. I guess others do this as well. Sierra actually also decided to port a fix that Bjørn did in the upstream qmi_wwan driver, but don't know if others did that as well. >From my POV, there are reasons to use GobiNet instead of qmi_wwan (e.g. if you're looking for the vendor-provided product support), or other things which we currently don't support yet (like firmware loading)... apart from those, I'd really suggest to use qmi_wwan and libqmi (with qmicli and/or ModemManager :) ). -- Aleksander <a href="https://aleksander.es" target="_blank">https://aleksander.es</a> </blockquote></div> </div>