Thanks Benoit for the reply. I wrote this email, when I was absolutely clueless as to how things fit in. Fortunately, through the help of MM and NM mailing lists, I have been successful in achieving what I wanted.
For other people who might be going through the pain (I know it really hurts), here are the broad-level steps I followed :: a) Changed the modem to QMI-mode. https://forum.sierrawireless.com/viewtopic.php?f=117&t=6759#p28436 https://lists.freedesktop.org/archives/modemmanager-devel/ 2016-August/003303.html b) Ensured that ModemManager was a fairly recent-one. https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-trusty sudo apt-get install modemmanager c) Let the kernel use qcserial/qmi_wwan/qmi-proxy to load /dev/cdc-wdm... interface, to set up communication in manner :: Any-User-App <=> ModemManager <=> qmi-proxy <=> /dev/cdc-wdm .. <=> modem ^ || V mmcli Then use mmcli for setting up connections manually. Detailed Q&A in https://lists.freedesktop.org/archives/modemmanager-devel/2016-August/003292.html thread. Thanks and Regards, Ajay On Tue, Aug 16, 2016 at 12:43 PM, Benoit Donnette <[email protected] > wrote: > Answering through ModemManager, for this is where the code uses the > /dev/ttyUSBx device. > > 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. > > 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... > > 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). > > > On Thu, Aug 11, 2016 at 4:03 PM, Ajay Garg <[email protected]> wrote: > >> CCing NM and MM guys. >> >> On Thu, Aug 11, 2016 at 2:23 PM, Ajay Garg <[email protected]> >> wrote: >> > Hi All. >> > >> > Have posted the question on Sierra-forums >> > https://forum.sierrawireless.com/viewtopic.php?f=117&t=9898 >> > Posting it here as well, as the activity there is relatively low, and >> > this is where all the kernel-guys hand :) >> > >> > >> > I am using a Ubuntu interfaced with a Sierra-MC8090 module. >> > >> > Right now MC8090 is identifed as a network-interface on Linux, made >> > possible by the usage of "sierra" (serial-driver) and "sierra_net" >> > (direct-ip usb-to-wwan driver) kernel-drivers. This "mostly" works, >> > except that we, in the user-application, are not able to access the >> > serial-file /dev/ttyUSB3 (this file is in constant usage by >> > /usr/sbin/ModemManager). >> > >> > Now, my question is, if we disable loading the "sierra_net" driver, >> > and use just "sierra" driver to communicate on the serial-port, will >> > using the Sierra-Linux-QMI-SDK do the job? In particular, >> > >> > * >> > I understand that we will now have exclusive access (please correct me >> > if I am wrong) to the serial-port /dev/ttyUSB3. >> > >> > * >> > How to do we create a socket to a particular server-port using the >> > QMI-SDK? I can see in the examples that we can start a data-call for a >> > profile (ConnectGSM.c), but I am unable to find how to instantiate a >> > socket through which we can do regular reads/writes. >> > >> > >> > Will be grateful to hear back from someone. >> > >> > >> > Thanks and Regards, >> > Ajay >> >> >> >> -- >> Regards, >> Ajay >> _______________________________________________ >> networkmanager-list mailing list >> [email protected] >> https://mail.gnome.org/mailman/listinfo/networkmanager-list >> > > -- Regards, Ajay
_______________________________________________ ModemManager-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
