On Tue, Apr 21, 2015 at 11:42 AM, Riccardo Vangelisti
riccardo.vangeli...@sadel.it wrote:
Fiuu... ;)
I've attach'd the previuosly patch with CallLog renamed to Voice as you want
:)
I think this is already a good start for an API.
Dan, what do you think?
Let me know what's the next step.
On Tue, Apr 21, 2015 at 6:36 PM, Ali Nematollahi alirez...@gmail.com wrote:
Script /usr/sbin/chat -v -f /etc/ppp/peers/hspa_chat finished (pid 4962),
status = 0x0
Serial connection established.
using channel 1
Using interface ppp0
Connect: ppp0 -- /dev/ttyUSB3
ModemManager[3261]: debug
On Thu, Apr 30, 2015 at 6:30 PM, Bernd Eggink mono...@sudrala.de wrote:
I tried that, didn't help. Actually I think the whole suspend-resume thing
is a red herring. All tests I made showed that suspending and resuming does
_not_ harm the connection, but _disconnecting_ does. In most cases after
On Mon, Apr 27, 2015 at 12:36 PM, Riccardo Vangelisti
riccardo.vangeli...@sadel.it wrote:
Dear everyone,
we've pushed on our branch (
https://bitbucket.org/riccardovangelisti/modemmanager/branch/voicecall )
these features:
* Proposal of call api in introspection (xml and enums)
* Added
On Tue, Apr 28, 2015 at 7:54 AM, Andreas XXX andreas...@web.de wrote:
ModemManager and the libraries libqmi, libmbim and so on can throw a lot
different error messages. I wanna know, is there any list of suggested
actions or detailed descriptions for each possible message?
Just one example:
We have tested new mm with these modems:
* Simcom SIM7250E
* Telit GT863-PY
* Falcom Twist
* Huawei MU709S-2
all modems works ! :)
Quick question; how do all these modems implement the actual voice
channel? Is it a physical audio channel? Is it an audio channel going
through a tty?
On Sat, May 9, 2015 at 4:47 PM, Aleksander Morgado
aleksan...@aleksander.es wrote:
On Fri, May 8, 2015 at 11:00 AM, Torsten Hilbrich
torsten.hilbr...@secunet.com wrote:
Version of modemmanager: 1.4.6
Version of libmbim: 1.12.2
Version of libqmi: 1.12.4
I noticed some unexpected behaviour
On Sun, Jun 14, 2015 at 9:48 AM, Tomas Jura tomas.ju...@gmail.com wrote:
I have Ericsson modem F3507 with the GPS. For a long time I was using it
with the modemmanager and a control tool called mbm-gpsd which was handling
the GPS (ttyACM02) port. It was working together somewhat. Most problems
On Wed, Aug 19, 2015 at 5:39 PM, Dan Williams d...@redhat.com wrote:
I have a Problem in RAW GPS, i enabled the gps-raw
root@wica:/# mmcli -m 0 --location-status
/org/freedesktop/ModemManager1/Modem/0
Location | capabilities: '3gpp-lac-ci, gps-raw, gps-nmea,
On Wed, Aug 19, 2015 at 9:16 AM, Ahmed Tafesh tafish_ah...@hotmail.com wrote:
root@wica:/# mmcli -m 0 --location-status
/org/freedesktop/ModemManager1/Modem/0
Location | capabilities: '3gpp-lac-ci, gps-raw, gps-nmea, cdma-bs'
| enabled:
On Wed, Aug 19, 2015 at 10:52 PM, Dan Williams d...@redhat.com wrote:
Unfortunately mmcli
doesn't seem to have a way to print the bearer properties.
You should be able to print them like this:
$ mmcli --bearer=[PATH/INDEX]
(i.e. without action)
--
Aleksander
https://aleksander.es
On Thu, Aug 20, 2015 at 8:29 AM, Ahmed Tafesh tafish_ah...@hotmail.com wrote:
thanks allot for hellping me i fix the promlem. the proplem is there is no
GPS Signal in the room.
when i put the sensor in window i got some result.
:)
i have another question.
is ther a way to start my script
On Wed, Jun 3, 2015 at 4:04 PM, Riccardo Vangelisti
riccardo.vangeli...@sadel.it wrote:
Anyway, the branch looks good enough to me; there are some things that
it doesn't yet cover, but I believe it's a good start. Dan, what do
you think?
libmm-glib: added support for Modem.Voice and Call
On Tue, Jul 28, 2015 at 7:33 PM, Bernd Eggink mono...@sudrala.de wrote:
Thank you Aleksander.
I'm on Ubuntu so I tried this without success:
jmss@aida:~$ sudo update-rc.d modemmanager defaults
update-rc.d: /etc/init.d/modemmanager: file does not exist
Then I looked inside
On Thu, Aug 13, 2015 at 3:14 PM, Andreas Fett andreas.f...@secunet.com wrote:
during connect the ModemManager debug logs show a List of provisioned
contexts. I assume that those are stored on the sim or in the modem
itself. Is there a way to query this list via the dbus api?
Not currently, no.
Hey hey,
New bugfix release in the ModemManager 1.4.x series.
Overview of changes in ModemManager 1.4.10
--
* QMI: retry unlock check on 'UimUninitialized' errors.
* QMI: fix '0' prefixed IMEI/ESN/MEID.
* Huawei: fix secondary port unsolicited message
On Thu, Oct 22, 2015 at 10:45 PM, Dan Williams wrote:
>> Being NAS commands, are these available also when not registered
>> anywhere? E.g. when in low-power mode?
>> I've seen people using these commands to retrieve SIM MCCMNC, but was
>> never sure about them as they were NAS
On Thu, Oct 22, 2015 at 11:03 PM, Dan Williams wrote:
> I forgot to CC the list, so here goes.
>
> On Thu, 2015-10-22 at 16:02 -0500, Dan Williams wrote:
>> In MM 0.6 days it used to be obfuscated, but that was pointless. Now
>> it's just the ICCID.
>>
Looks good, please push.
On Wed, Oct 21, 2015 at 2:00 PM, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
>
>>
>> Hi, I am working with Telit LE910. It works properly with ModemManager using
>> QMI, but if I disable and enable the modem again, I get the following:
>>
&
On Tue, Oct 27, 2015 at 4:06 PM, Dan Williams wrote:
>> >>> >> Being NAS commands, are these available also when not registered
>> >>> >> anywhere? E.g. when in low-power mode?
>> >>> >> I've seen people using these commands to retrieve SIM MCCMNC, but was
>> >>> >> never sure
On Wed, Oct 28, 2015 at 6:59 PM, Dan Williams wrote:
>> > As you can see, there is only one supported mode (allowed: 2g, 3g, 4g;
>> > preferred: none) which (as far as I know) offers me no contl about
>> > which network technology is being used. When using this modem with
>> >
On Fri, Oct 23, 2015 at 1:14 PM, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
> On Fri, Oct 23, 2015 at 12:13 AM, Dan Williams <d...@redhat.com> wrote:
>> On Thu, 2015-10-22 at 23:30 +0200, Aleksander Morgado wrote:
>>> On Thu, Oct 22, 2015 at 10:45 PM, Dan Wi
On Wed, Nov 11, 2015 at 7:40 PM, Dan Williams wrote:
> ---
> src/mm-broadband-modem-qmi.c | 49
>
> 1 file changed, 49 insertions(+)
>
> diff --git a/src/mm-broadband-modem-qmi.c b/src/mm-broadband-modem-qmi.c
> index
Hey John,
On Sat, Oct 17, 2015 at 3:16 PM, John Whitmore wrote:
> This is a development list so possibly the wrong place for this question but
> please redirect me as necessary.
>
No, this is the correct place to ask :)
> I've got a problem using two USB LTE Dongle modems of
When changing from idle to registered we'll load registration info before really
reporting that we're registered (so that clients can get the new registration
info directly). During this time, we should also allow LAC/CID updates triggered
in the location interface.
E.g. when receiving this QMI
On Wed, Oct 14, 2015 at 9:43 PM, Dan Williams wrote:
>>
>> The following two patches will fix the MCC/MNC/LAC/CID reporting in the
>> Location interface, which was broken especially with newer QMI modems like
>> the MC7304. Once the two patches are in place, the location info
LAC/CID may only be given in the serving system indications when the values
change, and therefore we shouldn't reset the values to 0 whenever they're not
reported.
This seems to happen in newer devices; older devices like the MC7710 did always
report the values in the indications.
---
On Thu, Oct 15, 2015 at 4:13 PM, Dan Williams wrote:
>> When changing from idle to registered we'll load registration info before
>> really
>> reporting that we're registered (so that clients can get the new registration
>> info directly). During this time, we should also allow
On Thu, Oct 8, 2015 at 12:00 AM, João M. S. Silva
<joao.m.santos.si...@gmail.com> wrote:
> On 10/07/2015 07:51 PM, Aleksander Morgado wrote:
>>
>> Hum... can you compile ModemManager yourself and try to get a
>> backtrace from that mmcli run?
>
>
> I can
On Thu, Oct 8, 2015 at 1:11 AM, João M. S. Silva
wrote:
> If I run this in the command line:
>
> mmcli -m ${modem} --messaging-create-sms="text='ççç',number=${number}"
>
> the SMS is created correctly:
>
> Successfully created new SMS:
>
On Fri, Oct 16, 2015 at 9:35 AM, Manuel Lauss wrote:
> On Tue, Nov 25, 2014 at 11:51 AM, Manuel Lauss wrote:
>> i have a machine with a Dell 5570 HSPA+ card, which according to lsusb
>> and windows is a sierra wireless device. The kernel recognizes
Auth settings will be added in a QMI message only if at least one of these is
requested:
* An explicit auth preference is requested.
* User string is given and isn't empty.
* Password string is given and isn't empty.
---
Any comment on this patch?
---
src/mm-bearer-qmi.c | 22
Hey José,
>
> Hi, I am working with Telit LE910. It works properly with ModemManager using
> QMI, but if I disable and enable the modem again, I get the following:
>
> root@ccimx6sbc:~# mmcli -m 0 -e
>
> ModemManager[698]: Modem /org/freedesktop/ModemManager1/Modem/0:
> state changed
On Thu, Aug 27, 2015 at 3:57 PM, Highland, Glenn
glenn.highl...@digi.com wrote:
I found the two links below very helpful. I’ve implemented C code that
communicates with
ModemManager via DBus using the DBus API, not the libmm-glib.
On Thu, Aug 27, 2015 at 2:27 PM, Raul Suarez Moreno
raul.sua...@blue-tc.com wrote:
We are trying to get an embedded device (equipped with Cinterion PLS8 rel.1
radio module) working using ModemManager. The device runs a Linux 3.14
configured using ptxdist-2013.12.0. We've been successful at
On Thu, Aug 27, 2015 at 4:26 PM, Raul Suarez Moreno
raul.sua...@blue-tc.com wrote:
Ok, thinks are clearer now.
Indeed, I did it. I attached the ModemManager log to this message.
Ah, I see it now in the other email.
Do you have udev setup in your system? Looks like ModemManager wasn't
notified
On Mon, Aug 31, 2015 at 2:17 PM, Raul Suarez Moreno
wrote:
> [947188221.161321] [mm-iface-modem-3gpp.c:751]
> mm_iface_modem_3gpp_run_registration_checks(): Running registration checks
> (CS: 'yes', PS: 'yes', EPS: 'no')
Looks like the modem was detected, but wasn't
On Mon, Aug 31, 2015 at 8:38 PM, Highland, Glenn
wrote:
> Our device is running ModemManager v1.4.6 against a Telit HE910-D modem
> (rev. 12.00.024). We’ve been quite successful
>
> in expediting data transfer via IP through the cell network (no problems
> there), but
>
> Sorry, that was my fault. I attach here the full ModemManager debug log just
> from the system booting until the modem enabling process finished. I got it
> after applying Daniels patch, so don't know if anything may be different.
So the modem is indeed being detected as LTE, so that's not
On Tue, Sep 1, 2015 at 12:19 PM, Raul Suarez Moreno
wrote:
> Aleksander, I've enabled debug mode to udev and here is the log content:
I think there was a misunderstanding; what we need is full
ModemManager debug logs, not udev debug logs :)
--
Aleksander
On Tue, Sep 1, 2015 at 6:41 PM, Raul Suarez Moreno
wrote:
> Aleksander, you mean using the "--with-newest-qmi-commands" configure is not
> advisable?? In fact, I built using that configuration just because it was
> used in the newer ptxdist version building config, should
On Tue, Sep 1, 2015 at 2:12 PM, Highland, Glenn wrote:
> I've performed the re-test you suggested below and attached the log showing
> the results.
> I did start MM in debug mode just so I could use it to enable the modem and
> then I
> ordered it to terminate
On Fri, Sep 4, 2015 at 8:30 PM, Ward, David - 0665 - MITLL
wrote:
> This was confirmed with the HP lt4111, which is a branded Sierra
> Wireless EM7355:
> https://bugzilla.redhat.com/show_bug.cgi?id=1223646#c46
>
>
> Aleksander,
>
> Your blog entry seems to have become a
On Wed, Sep 2, 2015 at 4:53 PM, Highland, Glenn wrote:
>
> Aleksander suggested that I propose the change below to the mailing list.
>
> Essentially we're encountering a problem with SMS notifications not being
> received
> by the application from ModemManager v1.4.6
Hey,
On Tue, Sep 8, 2015 at 10:41 PM, Stevens, Nick wrote:
> Variability in the response style from certain modems would cause the parsing
> of the +CGMR response to fail. For example, the Telit HE910 inserts an empty
> string ("") in the second field of the response,
On Tue, Sep 8, 2015 at 10:37 PM, Stevens, Nick wrote:
> Previously the enable unsolicited messages command (+CNMI) was only
> being sent on the primary. This patch adds support for sending the
> enable on the secondary as well. If the secondary doesn't exist, or if
>
On Wed, Sep 16, 2015 at 12:26 AM, Dan Williams wrote:
>> +/* +CMGR: ,,(whitespace) */
>> +/* The and fields are matched, but not currently used
>> */
>> +r = g_regex_new
>> ("\\+CMGR:\\s*(\\d+)\\s*,([^,]*),\\s*(\\d+)\\s*([^\\r\\n]*)", 0, 0, error);
>> +
On Wed, Sep 16, 2015 at 3:21 PM, Nick Stevens wrote:
>> > +
>> > +if (g_regex_match_full (r, reply, strlen (reply), 0, 0, _info,
>> > _error)) {
>>
>> I think you should also just restructure the function with a 'goto' for
>> error handling to break out early. Yeah
On Wed, Sep 16, 2015 at 3:46 PM, Krzysztof Kotlenga wrote:
> ---
> libmm-glib/mm-modem-simple.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Pushed to git master and mm-1-4, thanks!
> diff --git a/libmm-glib/mm-modem-simple.c b/libmm-glib/mm-modem-simple.c
Hey,
Is anyone out there using the MC7330 in Japan?
--
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
d on the secondary is a non-fatal error,
> it is unlikely that this will cause issues with other modems.
>
> Signed-off-by: Nick Stevens <nick.stev...@digi.com>
> ---
> V1->V2:
> Reworked event flow per suggestions from Aleksander Morgado - rather than
> passing callback an
On Wed, Sep 23, 2015 at 6:56 PM, Priyank Kumar wrote:
> Thanks for prompt response,
> I used att information to make a bearer, I get ppp but I dont see any IP in
> ifconfig, neither the PPP network interface comes as ppp0, which normally
> comes in wvdial.
> So I am stuck
On Thu, Sep 24, 2015 at 9:49 AM, Jean-Christian de Rivaz wrote:
> While trying to reproduce a bug by power cycling a USB modem 4 time per
> hour, I faced this message from the kernel:
>
> cdc_acm 1-2:1.0: no more free acm devices
>
> I found the the problem is caused by
On Thu, Sep 24, 2015 at 6:24 PM, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
> On Thu, Sep 24, 2015 at 6:09 PM, Jean-Christian de Rivaz <j...@eclis.ch>
> wrote:
>>
>> Actually the /dev/ttyACM* device node has been deleted by the kernel. Only
>> the M
On Thu, Sep 24, 2015 at 6:09 PM, Jean-Christian de Rivaz wrote:
>
> Actually the /dev/ttyACM* device node has been deleted by the kernel. Only
> the MM file descriptor on it still exists, but correspond to nothing
> anymore. And it's certain that the kernel notified the application
Just realized there were multiple questions in the email :)
On Wed, Sep 23, 2015 at 9:17 AM, Priyank Kumar wrote:
> It would be really useful if one example is given on mmcli or dbus API how
> to do the connect and disconnect to packet service.
Connection request can be
On Wed, Sep 23, 2015 at 9:17 AM, Priyank Kumar wrote:
> I am trying to connect a modem on Ubuntu 14.04.
> Everything works fine, i.e modem is enabled, I can send and receive SMS
> through mmcli.
> The problem I am facing is that once a bearer is created with right APN and
On Thu, Sep 17, 2015 at 11:31 PM, Nick Stevens wrote:
> Variability in the response style from certain modems causes the parsing
> of the +CGMR response to fail. For example, the Telit HE910 inserts an
> empty string ("") in the second field of the response, causing the
>
---
cli/mmcli-bearer.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/cli/mmcli-bearer.c b/cli/mmcli-bearer.c
index 5829e60..fe54810 100644
--- a/cli/mmcli-bearer.c
+++ b/cli/mmcli-bearer.c
@@ -135,10 +135,12 @@ print_bearer_info (MMBearer *bearer)
On Wed, Dec 2, 2015 at 5:50 PM, Carlo Lobrano wrote:
> I am trying to solve a problem on HE910 Telit modem (I also opened bug 93135
> about this), which does not support NULL items for AT+CPMS command, so
> commands like
>
> AT+CPMS="","ME"
>
> return with error. My idea
Hey!
This looks much better now :)
See comments below.
On Tue, Dec 15, 2015 at 3:44 PM, Carlo Lobrano wrote:
> From: Carlo Lobrano
>
> ---
> plugins/Makefile.am | 18 +-
> plugins/telit/mm-broadband-modem-telit.c
On Tue, Dec 15, 2015 at 5:38 PM, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
>
> Looks like the 'retries' object is not being freed properly in the
> case of errors. What you need to do is to make sure that the ownership
> of the retries object is always transferre
On Wed, Dec 16, 2015 at 5:55 PM, Dan Williams <d...@redhat.com> wrote:
> On Wed, 2015-12-16 at 10:27 +0100, Aleksander Morgado wrote:
>> We were trying to load the generic modes supported reported by either
>> *CNTI=2 or
>> AT+WS46=?, so that then we could filter
Hey!
See comments below.
On Mon, Dec 14, 2015 at 12:51 PM, Carlo Lobrano wrote:
> ---
> plugins/telit/mm-broadband-modem-telit.c | 169
> +++
> plugins/telit/mm-broadband-modem-telit.h | 2 +
> 2 files changed, 171 insertions(+)
>
> diff
We were trying to load the generic modes supported reported by either *CNTI=2 or
AT+WS46=?, so that then we could filter out the MBM-specific modes unsupported.
But, this may not be ideal, as both these two commands may fail:
[mm-broadband-modem.c:1612] modem_load_supported_modes(): loading
On Tue, Jan 5, 2016 at 11:19 PM, Reinhard Speyerer wrote:
> AFAIK it should not be required to implement a IMS client in
> ModemManager for sending/receiving SMS in the Verizon LTE network at
> least when either the MC7750 or the MC7354 with the VZW Gobi image is
> used as both
Hey Jerry :)
On Tue, Dec 29, 2015 at 7:26 PM, Jerry Hicks wrote:
> Wondering what you might think about text messaging on Verizon's LTE with the
> MC74XX modules?
>
> As I loosely understand things, Verizon requires a connection to their IPv6
> VZWIMS network for text
On Mon, Dec 14, 2015 at 8:57 PM, Dan Williams wrote:
>> Looks mostly good. Though I did get an error attempting to disable a
>> my QMI-based E397 while location gathering was active, which probably
>> wasn't caused by this specific patch:
>>
>> ModemManager[28430]:
On Mon, Dec 14, 2015 at 8:50 PM, Dan Williams wrote:
>> The default setup uses a refresh time of 30s, which means that even
>> if the GPS
>> location updates are received at a higher frequency, the DBus
>> interface will
>> still expose at most one update every 30s.
>>
>> This
f the License, or
+ * (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more
The following patch series implements a new 'Stats' property in the Bearer
object which reports connection statistics. The values are directly retrieved
from the device (e.g. queried), as opposed to measuring the stats in the
network interface.
This implementation is currently limited to:
*
The new property is a dictionary which may include different parameters,
depending on what is actually supported by the underlying modem. For now,
just bytes RX/TX.
Note that this object will expose the stats *as reported by the modem*. These
values may differ from e.g. what is seen in the
On Thu, Sep 17, 2015 at 6:51 PM, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
> Is anyone out there using the MC7330 in Japan?
For anyone interested, these devices come usually locked to NTT
Docomo. Once operator-unlocked I could play with the device in
European 3G network fr
On Mon, Nov 30, 2015 at 5:21 PM, Dan Williams <d...@redhat.com> wrote:
> On Fri, 2015-11-27 at 14:51 +0100, Aleksander Morgado wrote:
>> The new property is a dictionary which may include different
>> parameters,
>> depending on what is actually supported by the u
On Mon, Nov 30, 2015 at 5:33 PM, Dan Williams wrote:
>> +static gboolean
>> +stats_update_cb (MMBaseBearer *self)
>> +{
>> +/* If the implementation knows how to update stat values, run it
>> */
>> +if (MM_BASE_BEARER_GET_CLASS (self)->reload_stats &&
>> +
On Wed, Nov 18, 2015 at 9:14 AM, José wrote:
> Seems like the log I gave was not complete. Here is a better one:
>
> http://pastebin.com/Y24a9Y8W
>
> At line 1849 seems like ModemManager decides to abort the connection, I am
> not sure why.
During the connection attempt the
On Fri, Jun 3, 2016 at 4:53 AM, Ralph Plawetzki wrote:
> just for the record please find attached in short what goes wrong:
> [EM7455 gets local IP] http://pastebin.com/K7j10Y64
Ralph, could you get the latest ModemManager "qmi-over-mbim" branch,
rebuild and retry? The
On Fri, Jun 10, 2016 at 11:57 AM, Bjørn Mork wrote:
>> On a unrelated note: my 4G signal is rather poor. Mobile phone
>> typically flips back and forth between 2g and 3g. I have the feeling
>> that the Sierra modem does not really fall back to 2g. The connection
>> is established
On Fri, Jun 10, 2016 at 11:46 AM, Stefan Armbruster
wrote:
> I have not done enough testing but it seems to work so far. I've cold
> booted the machine and got "power state: on" on `mmcli -l 0` - so fcc
> auth seems to be done. After a suspend/resume cycle I also got a
>
On Thu, Jun 9, 2016 at 11:53 AM, Bjørn Mork wrote:
>> What do you guys think, should we unconditionally try to send the FCC
>> auth via QMI over MBIM in the generic MBIM implementation? E.g. during
>> the power-up sequence.
>
> My memory lasts exactly this far: .
>
> Did we test
On Thu, Jun 9, 2016 at 12:24 PM, Bjørn Mork wrote:
>>> How difficult will it be to restrict this to Sierra modems with QMI
>>> service support? Or was that the set you meant we should
>>> unconditionally try the command on? If so, then I say "go!".
>>
>> I tried the QMI MBIM
On Sat, Jun 11, 2016 at 11:14 AM, Stefan Armbruster
wrote:
> @Aleksander: see the modem-manager debug logfile at
> http://pastebin.com/4eyg9ZKk - please let me know if that is
> sufficient or if you need something else.
Wow, I'm impressed even myself; that looks like it
On Mon, Jun 13, 2016 at 1:01 AM, Andreas Fett wrote:
> On 10/06/16 20:46, Stefan Armbruster wrote:
>> On a unrelated note: my 4G signal is rather poor. Mobile phone
>> typically flips back and forth between 2g and 3g. I have the feeling
>> that the Sierra modem does not
On Mon, Jun 13, 2016 at 9:53 AM, Rasmus Lerdorf wrote:
> Aleksander asked me to post the debug output from this almost-working mbim
> session.
> The backstory is that it is connecting, getting ip/dns info and bringing the
> wwan0 interface up, but no packets are flowing:
>
On Sat, May 14, 2016 at 9:25 AM, Ting-Yuan Huang wrote:
> From: Ting-Yuan Huang
>
> This patch makes declarations bind to definitions within the same module
> to prevent the potential ambiguity if referenced directly.
>
> AddressSanitizer think they
On Tue, May 31, 2016 at 11:02 PM, Dan Williams wrote:
>>
>> Hey Yegor,
>>
>> Sorry, completely forgot about it.
>>
>> Could you try this patch and see if it works?
>
> Looks good to me.
Thanks, merged to git master.
--
Aleksander
https://aleksander.es
On Wed, Jun 1, 2016 at 7:22 PM, Dan Williams <d...@redhat.com> wrote:
> On Wed, 2016-06-01 at 19:20 +0200, Aleksander Morgado wrote:
>> On Wed, Jun 1, 2016 at 7:13 PM, Dan Williams <d...@redhat.com> wrote:
>> >
>> > On Wed, 2016-06-01 at 15:46 +0200, Aleksan
On Wed, Jun 1, 2016 at 7:13 PM, Dan Williams <d...@redhat.com> wrote:
> On Wed, 2016-06-01 at 15:46 +0200, Aleksander Morgado wrote:
>> On Wed, Jun 1, 2016 at 11:15 AM, Ralph Plawetzki <ra...@purejava.org>
>> wrote:
>> >
>> > iface_modem_fir
wrote:
> On Wed, Jun 22, 2016 at 1:40 AM, Aleksander Morgado
> <aleksan...@aleksander.es> wrote:
>
> Hey Ralph & Rasmus, I've just pushed a new patch (broadband-modem: run power
> up/down actions unconditionally) to the "qmi-over-mbim" branch in the
> ModemMa
Hey Ralph & Rasmus,
I've just pushed a new patch (broadband-modem: run power up/down
actions unconditionally) to the "qmi-over-mbim" branch in the
ModemManager repo, the libqmi and libmbim ones were not updated.
Could you guys update and retry?
I think I'm actually going to try to buy one of
On Fri, Jun 17, 2016 at 5:46 PM, Dan Williams wrote:
> MM never passes MBIM_CONTEXT_IP_TYPE_DEFAULT which would require paying
> attention to the ip_type in the reply to figure out what type the modem
> activated. Instead, MM always specifies the ip_type it wants to activate,
>
On Wed, Jun 22, 2016 at 11:01 PM, Jason L Tibbitts III
wrote:
>
> JD> I've been in and out of the FCC over MBIM stuff over
> JD> here. Alexander, you ever find someone to test with EM7455? I got
> JD> one. Probably can't test until the weekend. But I might have some
> JD> time
On Thu, Jun 23, 2016 at 7:00 PM, George Tepnadze
wrote:
> old modem manager but patched libqmi-qmi-over-mbim from AUR
Note that an old modemmanager won't try the FCC auth command via
QMI-over-MBIM; you'd need to manually do it yourself using qmicli
before MM tries to
On Fri, Jun 24, 2016 at 12:28 PM, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
>>> I also have one (Sierra with USB ID 1199:9079). Just found out that I
>>> need to rebuild a few things from git branches and was planning on
>>> trying to get to that today
On Mon, Jan 4, 2016 at 9:02 PM, Dan Williams wrote:
>> We were trying to load the generic modes supported reported by either
>> *CNTI=2 or
>> AT+WS46=?, so that then we could filter out the MBM-specific modes
>> unsupported.
>
> LGTM; returns the right supported modes for my
On Sun, Jan 10, 2016 at 9:25 PM, Brendan Simon (eTRIX)
wrote:
> I'm looking for a Python example/sample/snippet to send an SMS message to a
> mobile phone.
>
> All I can find is older code that uses EnumerateDevices() method.
>
> e.g.
>
On Mon, Jan 18, 2016 at 4:39 PM, José wrote:
> Is there a way to know when is late enough to issue the connect
> request? Im trying to get an embedded system connected to cellular
> network on boot, so the commands are getting issued as soon as
> ModemManager detects the
On Mon, Jan 18, 2016 at 10:15 PM, Glenn Washburn
wrote:
> "curl -v --interface wwan0 http://www.google.com;
You're binding the request to the wwan interface, which I assume it's
because it isn't the default route.
Try to disable the reverse path filtering,
Response parsing was being done in different places for AT and QCDM subclasses;
in the case of AT it was being done early, before returning the byte array in
the mm_serial_port_command_finish() response. In the case of QCDM, it was being
done after mm_serial_port_command_finish(), and that was
On Mon, Jan 18, 2016 at 9:53 PM, Dan Williams wrote:
>> > So wouldn't that also blow away the next messages in the buffer for
>> > something like cancellation or random internal MM errors?
>> >
>>
>> If we've got unsolicited messages interleaved with the response,
>> those
>>
1 - 100 of 2422 matches
Mail list logo