<div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div>Thanks Benoit for the reply.<br><br></div>I wrote this email, when I was absolutely clueless as to how things fit in.<br></div>Fortunately, through the help of MM and NM mailing lists, I have been successful in achieving what I wanted.<br><br></div>For other people who might be going through the pain (I know it really hurts), here are the broad-level steps I followed ::<br><br></div>a)<br></div>Changed the modem to QMI-mode.<br><br><a href="https://forum.sierrawireless.com/viewtopic.php?f=117&t=6759#p28436" target="_blank">https://forum.sierrawireless.<wbr>com/viewtopic.php?f=117&t=<wbr>6759#p28436</a><br><a href="https://lists.freedesktop.org/archives/modemmanager-devel/2016-August/003303.html" target="_blank">https://lists.freedesktop.org/<wbr>archives/modemmanager-devel/<wbr>2016-August/003303.html</a><br><br><br></div>b)<br></div>Ensured that ModemManager was a fairly recent-one.<br><br><a href="https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-trusty" target="_blank">https://launchpad.net/~<wbr>aleksander-m/+archive/ubuntu/<wbr>modemmanager-trusty</a><br></div>sudo apt-get install modemmanager<br><br><br></div>c)<br></div>Let the kernel use qcserial/qmi_wwan/qmi-proxy to load /dev/cdc-wdm... interface, to set up communication in manner ::<br> <br></div> Any-User-App <=> ModemManager <=> qmi-proxy <=> /dev/cdc-wdm .. <=> modem<br> ^<br> ||<br></div><div> V<br></div><div> mmcli<br></div><div><br></div>Then use mmcli for setting up connections manually.<br><br></div>Detailed Q&A in <a href="https://lists.freedesktop.org/archives/modemmanager-devel/2016-August/003292.html">https://lists.freedesktop.org/archives/modemmanager-devel/2016-August/003292.html</a> thread.<br><br><br></div>Thanks and Regards,<br></div>Ajay<br><div><div><div><div><div><div><div><div><div><div><div><br></div></div></div></div></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 16, 2016 at 12:43 PM, Benoit Donnette <span dir="ltr"><<a href="mailto:benoit.donnette@21net.com" target="_blank">benoit.donnette@21net.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Answering through ModemManager, for this is where the code uses the /dev/ttyUSBx device.<br><br></div>Well, if you want to have a modem connection up and ready through NetworkManager/ModemManager, they're doing the job, and you won't need to access the device anyway. This is obviously not what you're doing, so I'd say let the ModemManager off this modem.<br><br></div>If you're trying to establish a socket connection to a server, then it looks like you're trying to use the modem as a data connection still. Then ModemManager makes what you want...<br><br></div>So, if you're trying to use the modem as a data carrier, ModemManager/NetworkManager do all the unpleasant part for you, what is your reason for accessing the device ? You possibly need no more that a few lines of C to have an elementary multiplexer on your device (and set up MM to use the multiplex instead of ttyUSBx).<br><br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Thu, Aug 11, 2016 at 4:03 PM, Ajay Garg <span dir="ltr"><<a href="mailto:ajaygargnsit@gmail.com" target="_blank">ajaygargnsit@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">CCing NM and MM guys.<br> <br> On Thu, Aug 11, 2016 at 2:23 PM, Ajay Garg <<a href="mailto:ajaygargnsit@gmail.com" target="_blank">ajaygargnsit@gmail.com</a>> wrote:<br> > Hi All.<br> ><br> > Have posted the question on Sierra-forums<br> > <a href="https://forum.sierrawireless.com/viewtopic.php?f=117&t=9898" rel="noreferrer" target="_blank">https://forum.sierrawireless.c<wbr>om/viewtopic.php?f=117&t=9898</a><br> > Posting it here as well, as the activity there is relatively low, and<br> > this is where all the kernel-guys hand :)<br> ><br> ><br> > I am using a Ubuntu interfaced with a Sierra-MC8090 module.<br> ><br> > Right now MC8090 is identifed as a network-interface on Linux, made<br> > possible by the usage of "sierra" (serial-driver) and "sierra_net"<br> > (direct-ip usb-to-wwan driver) kernel-drivers. This "mostly" works,<br> > except that we, in the user-application, are not able to access the<br> > serial-file /dev/ttyUSB3 (this file is in constant usage by<br> > /usr/sbin/ModemManager).<br> ><br> > Now, my question is, if we disable loading the "sierra_net" driver,<br> > and use just "sierra" driver to communicate on the serial-port, will<br> > using the Sierra-Linux-QMI-SDK do the job? In particular,<br> ><br> > *<br> > I understand that we will now have exclusive access (please correct me<br> > if I am wrong) to the serial-port /dev/ttyUSB3.<br> ><br> > *<br> > How to do we create a socket to a particular server-port using the<br> > QMI-SDK? I can see in the examples that we can start a data-call for a<br> > profile (ConnectGSM.c), but I am unable to find how to instantiate a<br> > socket through which we can do regular reads/writes.<br> ><br> ><br> > Will be grateful to hear back from someone.<br> ><br> ><br> > Thanks and Regards,<br> > Ajay<br> </div></div><span><font color="#888888"><br> <br><span class="HOEnZb"><font color="#888888"> <br> --<br> Regards,<br> Ajay<br> ______________________________<wbr>_________________<br> networkmanager-list mailing list<br> <a href="mailto:networkmanager-list@gnome.org" target="_blank">networkmanager-list@gnome.org</a><br> <a href="https://mail.gnome.org/mailman/listinfo/networkmanager-list" rel="noreferrer" target="_blank">https://mail.gnome.org/mailman<wbr>/listinfo/networkmanager-list</a><br> </font></span></font></span></blockquote></div><br></div> </blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Regards,<br>Ajay<br></div> </div>