On 09/06/2012 08:26 AM, Ben Chan wrote:
ModemManager configure script currenty requires glib 2.30.2 or later,
bud g_variant_new_fixed_array requires at least glib 2.32. To maintain
the compatibility with glib 2.30, this patch modifies the code to use
g_variant_new_from_data instead of
Oops :-)
Pushed, thanks.
On 09/06/2012 02:21 AM, Ben Chan wrote:
---
plugins/icera/mm-broadband-bearer-icera.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/plugins/icera/mm-broadband-bearer-icera.c
b/plugins/icera/mm-broadband-bearer-icera.c
index
On 09/06/2012 03:31 AM, Ben Chan wrote:
Modem plugins set the 'modem' property before the 'config' property when
creating a bearer. set_signal_handlers() should thus be called after both
properties are set such that modem_{3gpp,cdma}_registration_state_changed
checks roaming allowance
ModemManager[13706]: warn [1346679919.021922] [mm-plugin-manager.c:283]
plugin_supports_port_ready(): (Huawei): (tty/ttyUSB4) error when checking
support: 'Defer needed'
ModemManager[13706]: debug [1346679919.022013] [mm-plugin-manager.c:320]
plugin_supports_port_ready(): (tty/ttyUSB4):
bjorn@nemi:/usr/local/src/git/linux$ mmcli -b 0
Bearer '/org/freedesktop/ModemManager1/Bearer/0'
-
Status | connected: 'yes'
| suspended: 'no'
| interface: 'wwan0'
| IP
ModemManager[11662]: KEY: 06:00:03:02:00:00:00:00
ModemManager[11662]: Service: 02
ModemManager[11662]: Client ID: 03
ModemManager[11662]: Transaction ID: 06:00
ModemManager[11662]: [/dev/cdc-wdm0] Received message...
QMUX:
length = 47
flags = 0x80
service = dms
On 09/03/2012 03:52 PM, Bjørn Mork wrote:
ModemManager[13706]: warn [1346679919.021922] [mm-plugin-manager.c:283]
plugin_supports_port_ready(): (Huawei): (tty/ttyUSB4) error when checking
support: 'Defer needed'
ModemManager[13706]: debug [1346679919.022013] [mm-plugin-manager.c:320]
Hey Bjørn
On 09/03/2012 05:13 PM, Aleksander Morgado wrote:
On 09/03/2012 03:52 PM, Bjørn Mork wrote:
ModemManager[13706]: warn [1346679919.021922] [mm-plugin-manager.c:283]
plugin_supports_port_ready(): (Huawei): (tty/ttyUSB4) error when checking
support: 'Defer needed'
ModemManager
On 09/03/2012 06:24 PM, Marius Kotsbak wrote:
Patch attached again in right format.
From d54ebafd698210e44ca92f4ba6f0fed597ed9518 Mon Sep 17 00:00:00 2001
From: Marius B. Kotsbak mar...@kotsbak.com
Date: Sun, 2 Sep 2012 22:29:18 +0200
Subject: [PATCH] sierra: add support for new !SELRAT
On 10/04/2011 01:34 AM, Dan Williams wrote:
I do see problems in both implementations, and I understand that the new
one may be more complex, but trying to cope with the addition of 4G to
the list is not an easy task, I would say.
Yeah, I know.
It would be good to check what modes the
Are you able to compile both MM and libqmi with CFLAGS=-ggdb -O0 and
get me a bit more info about where in data_available() the thing
crashed? I don't even know if that's the data_available() from MM or
libqmi-glib... :-/
Sure. Just had to figure out how not to strip these things be
On 09/02/2012 03:55 PM, Bjørn Mork wrote:
ModemManager[4941]: warn [1346593549.302696] [mm-broadband-modem.c:7095]
initialization_started_ready(): Couldn't start initialization: Transaction
timed out
ModemManager[4941]: info [1346593549.302828] [mm-iface-modem.c:993]
Pushed a fix to use the global packet data handle if this ever happens;
should at least fix the segfault.
Yup, confirmed. But I got another one for you... Disconnecting the USB
device results in:
ModemManager[25297]: debug [1346422178.492667] [mm-modem-helpers-qmi.c:190]
---
src/mm-bearer-qmi.c | 19 ---
1 file changed, 4 insertions(+), 15 deletions(-)
diff --git a/src/mm-bearer-qmi.c b/src/mm-bearer-qmi.c
index ef28e95..95d856c 100644
--- a/src/mm-bearer-qmi.c
+++ b/src/mm-bearer-qmi.c
@@ -596,14 +596,6 @@ connect_context_step (ConnectContext
Hey Bjørn;
Can you take a look at the following patches to see if they are enough to handle
the devices with multiple QMI ports? Not sure if the udev logic to find the
matching QMI port of a given WWAN port is correct or not.
The general idea with multiple bearers is that you can create as many
QMI and wwan ports come in pairs. Each wwan port has an associated control QMI
port, which is the only port allowed to send the Start|Stop Network QMI requests
to start|stop the connection in the given wwan interface.
Paired QMI and wwan interfaces (should) share the same parent udev device,
On 08/30/2012 01:30 PM, Marius Kotsbak wrote:
For the Sierra MC7710, it also does not work:
$ mmcli -m 0 --set-preferred-mode 4g --set-allowed-modes 4g
That is also strange, as it is possible to set preference using custom
AT command AT!SELRAT (or maybe it is only allowed modes?). Are
I did, but maybe hit a bad timing. Anyway, master version now builds and
connection still works with my ZTE modem, but I got a crash with the
Sierra modem (which is not Icera):
ERROR:mm-port-probe.c:531:serial_probe_at_icera_result_processor:
assertion failed: (g_variant_is_of_type
And note: you are the first one testing the port of the Sierra plugin
(so thanks thanks); but be aware that more nasty issues may happen, just
report them if possible.
Forgot to say; there are some additional fixes to get ported from
MM06/MM05 to git master regarding the Sierra plugin
On 08/30/2012 02:10 PM, Marius Kotsbak wrote:
Den 30. aug. 2012 14:05, skrev Aleksander Morgado:
On 08/30/2012 01:30 PM, Marius Kotsbak wrote:
For the Sierra MC7710, it also does not work:
$ mmcli -m 0 --set-preferred-mode 4g --set-allowed-modes 4g
That is also strange, as it is possible
Can you take a look at the following patches to see if they are enough to
handle
the devices with multiple QMI ports? Not sure if the udev logic to find the
matching QMI port of a given WWAN port is correct or not.
The general idea with multiple bearers is that you can create as many
Maybe nobody have tried it yet. It would be useful to get the test
results to see it there are missing parts.
I'll get working on it, then.
Also, even though I had success using mmcli to connect semimaually, it
might be easier/better to connect using libqmi support scripts.
I just read
More or less, yes. You have the 'mmcli' utility in that branch,
though,
so you can skip writing raw dbus-send commands and play with the cli
instead, like this (assuming only one modem connected, so index 0):
Show modem info and status:
$ mmcli -m 0
Send PIN:
$ sudo mmcli
Attached is a patch which makes the after-sim-unlock step get run also
when PIN request is disabled. Could you give it a try with your use case
and a proper implementation of the modem_after_sim_unlock() callback? I
would actually try the ZTE way (running +CPMS? retries), as IIRC you
were
On 08/28/2012 07:36 PM, Tristan Stevens wrote:
I'm now running 0.5.999 as downloaded
from https://launchpad.net/ubuntu/quantal/amd64/modemmanager however am
still seeing the same problem. Logs below:
Aug 28 18:27:33 hostname-1 modem-manager[1065]: debug
[mm-modem-huawei-gsm.c:712]
Hey everyone,
So, the 'qmi-support' was just merged to git master, which means that
you'll now need libqmi git master [1] to compile ModemManager. All new
QMI-related development will now go into git master directly.
Cheers!
[1] http://cgit.freedesktop.org/libqmi
--
Aleksander
I actually got the connection up now using the method above (mmcli +
ifup wwan0) so it seems to be close to functional now.
Regarding connectivity; QMI-powered MM is fully functional. Missing
things include messaging and location, which are scheduled for next
weeks.
Okay. What about
On a related note, since ModemManager already uses AT+CRSM to read
ICCID and operator name/ID, I wonder if it makes sense to
AT+CRSM=176,28423,0,0,9 instead of AT+CIMI for reading IMSI, or use
it as a fallback solution if AT+CIMI fails or is not supported by a
modem.
At least on one modem
So, the 'qmi-support' was just merged to git master, which means that
you'll now need libqmi git master [1] to compile ModemManager. All new
QMI-related development will now go into git master directly.
Wow, great work!
I noticed that you even support multiple bearers now, allowing me to
On 08/28/2012 07:09 AM, Ben Chan wrote:
For (1), the 'Modem' interface has a generic 'modem_after_sim_unlock'
step which allows plugin implementations to provide a method to (try to)
ensure that the SIM access is valid. Some plugins may just provide a N
second timeout to be run in that step. I
Do you mean that you still need the timeout even if the PIN request is
not enabled?
If the code tries to load Sim properties before unlocking the PIN and
those fail, they will anyway get retried after the successful PIN unlock.
Yes, the issue happens on a SIM without PIN locked. One
that we don't rewrite exactly the same implementation in
different plugins).
--
Aleksander
From 4065606a694d55d03bee5b4c7e6fd431d8f8e9ec Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Tue, 28 Aug 2012 18:34:07 +0200
Subject: [PATCH] iface-modem: run after-sim-unlock
On 08/24/2012 05:04 PM, Ben Chan wrote:
---
This patch is a stripped-down version of the previous patch sim: retry SIM
operations during initialization. It does not retry SIM operations but
simply validates the IMSI value.
A follow-up patch is needed to handle retries appropriately under
Pushed, thanks.
On 08/26/2012 06:34 AM, Ben Chan wrote:
---
src/mm-sms-part.c | 11 ++-
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/src/mm-sms-part.c b/src/mm-sms-part.c
index 6637325..53b6678 100644
--- a/src/mm-sms-part.c
+++ b/src/mm-sms-part.c
@@
After the +CPIN: READY response, there is a period of time where SIM
operations are not reliable on some modems. I've observed issues with
reading ICCID and IMSI. The following example shows that the modem
reports bogus values of ICCID. The first reply of
AT+CRSM=176,12258,0,0,10 is IMSI
The timeout + retries really tries to address flaky SIM operations on
some modems. We could limit the retries to certain error codes, but
that won't address flakiness, unfortunately :(
We could let individual plugins to configure whether it should retry
on failed SIM operations. For a
I'm running 0.9.4.0 on Ubuntu 12.04.
Logs below with NM and MM in debug mode.
Ubuntu 12.04 still has ModemManager 0.5 (with NetworkManager is 0.9.4).
IIRC there's a ModemManager 0.6 package for the next Ubuntu 12.10; you
may want to try that instead. Or otherwise compile the 0.6-rc1
Hey,
Updated the 'Modem' DBus interface in git master so that instead of
returning just one driver (it was the driver of the first port grabbed)
it now returns a list (signature 'as') of all drivers for all the
grabbed ports.
Cheers,
--
Aleksander
On 08/22/2012 07:28 AM, Ben Chan wrote:
This patch modifies the MMSim interface to validate the IMSI value
reported by AT+CIMI and retry the command upon an error. It also
modifies other SIM operations during the interface initialization to
retry upon an error.
I'm a bit worried about the
Hey,
Updated the Modem.CreateBearer() and Simple.Connect() interfaces in git
master so that the 'ip-type' entry in the dictionaries now expect a
uint32 (matched to the new MMBearerIpFamily enum) instead of a set of
predefined strings. See commit 1ac18a06bb37d8745480a9af4fd6bc2f762bf265.
With
I pushed some fixes to the 'qmi-support' branch of ModemManager trying
to cope with the 'usb'-'usbmisc' transition. Basically, I'm assuming
that either one or the other may appear, trying to avoid the need for a
runtime kernel version check. Could you test that in the newest kernels
with
On 08/20/2012 08:27 AM, Ben Chan wrote:
This patch modifies MMBroadbandModemIcera as follows:
- Change modem_load_current_bands to report only bands that are
currently enabled
- Change modem_set_bands to handle setting ANY band in a way that no
forbidden bands are activated.
Pushed,
This happens when developed but not tested :-) Good catch!
Pushed.
On 08/20/2012 08:26 AM, Ben Chan wrote:
---
plugins/icera/mm-broadband-modem-icera.c |2 +-
src/mm-broadband-bearer.c|7 +--
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git
On 08/17/2012 06:26 AM, Ben Chan wrote:
---
plugins/icera/mm-broadband-bearer-icera.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/plugins/icera/mm-broadband-bearer-icera.c
b/plugins/icera/mm-broadband-bearer-icera.c
index b4e8082..789c727 100644
---
On 08/10/2012 08:05 AM, Ben Chan wrote:
In practice, it may take longer time for a SIM to become ready when the
modem interface tries to use AT+CPIN? to determine if the SIM is
PIN-locked. This patch increases the number of trials for PIN check to
address the issue.
Pushed now, thanks.
---
Hi Franko,
Do you have began to develop the MBIM driver for Linux kernel?
Do you have got the MBIM device for test?
We are developing some devices to support MBIM protocol. We hope that
it can be used on Linux.
So I think that we maybe do some cooperation
Is this branch working now with master version of Network manager
including the gnome applet?
Not yet, no. The 'qui-support' branch is to be considered unstable, as
I'm still hacking into it extensively. That branch is then based on git
master, which is more stable, but not integrated yet
Is this branch working now with master version of Network manager
including the gnome applet?
Not yet, no. The 'qui-support' branch is to be considered unstable, as
I'm still hacking into it extensively. That branch is then based on git
master, which is more stable, but not integrated
Is this branch working now with master version of Network manager
including the gnome applet?
Not yet, no. The 'qui-support' branch is to be considered unstable, as
I'm still hacking into it extensively. That branch is then based on git
master, which is more stable, but not integrated yet
More or less, yes. You have the 'mmcli' utility in that branch, though,
so you can skip writing raw dbus-send commands and play with the cli
instead, like this (assuming only one modem connected, so index 0):
Show modem info and status:
$ mmcli -m 0
Send PIN:
$ sudo mmcli -i 0
On 08/01/2012 08:53 PM, Ben Chan wrote:
---
The issue doesn't seem to affect update_signa_quality.
Pushed this patch now, thanks!
Updating signal quality or access tech values would really be affected.
If the interface is shutdown while we're waiting the reply to the AT
command, we would end
Good catch :-)
Are you able to update the patch including the same fix for the access
technologies loading? Suffers from the same issue.
Also, if the context is not anymore available because we
disabled/shutdown the interface, I wouldn't also set the values
retrieved (e.g. skip calling
On 07/31/2012 01:46 AM, Ben Chan wrote:
This patch fixes mmcli to set the default timeout on the manager proxy
interface (MmGdbusOrgFreedesktopModemManager1) instead of MMManager
itself. The later is not a GDBusProxy object.
---
This is what 'mmcli -L' currently prints out:
(mmcli:4689):
Hey!
You're truly trying *a lot* of untested code :-)
I am playing a bit with the qmi-support branch, which seems to be
getting close to operational. Nice work!
But I have a few issues I don't like, as usual :-)
Don't worry, I think I already owe you a couple of beers for all this
Hey Ben Thieu,
---
src/mm-bearer.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/src/mm-bearer.c b/src/mm-bearer.c
index 3cce948..3b1be8c 100644
--- a/src/mm-bearer.c
+++ b/src/mm-bearer.c
@@ -450,7 +450,8 @@ mm_bearer_disconnect (MMBearer *self,
}
On 22/04/12 19:53, Alexander Orlov wrote:
Aleksander Morgado:
In the ZTE plugin case, using POWER_UP as well may be not needed, as the
plugin overrides the whole enabling sequence, and therefore the generic
code launching the power up command from that property is never called
(just check
Hey Alexander,
When I send an USSD query, it should be encoded to proper charset (UCS2
in my case). But it is not. Because of this USSD queries do not work at
all on my ZTE MF192 modem:
(ttyACM0): -- 'AT+CUSD=1,*100#,15CR'
(ttyACM0):-- 'CRLFERRORCRLF'
In git logs I have found this
On Mon, Jul 9, 2012 at 9:25 PM, Brian Gitonga Marete
mar...@toshnix.com wrote:
Hello all,
I have the same (or very similar) ZTE MF192 modem referred to by
Dmitry Morozhnikov here:
https://mail.gnome.org/archives/networkmanager-list/2012-February/msg00014.html
My modem is supplied by
On 07/17/2012 07:23 AM, Ben Chan wrote:
load_supported_storages may fail, which results in unallocated storage
memory. This patch modifies load_initial_sms_parts_from_storages and
is_storage_supported to handle that gracefully.
---
src/mm-iface-modem-messaging.c | 10 ++
1 files
Probably your modem doesn't support mode switching with AT^SYSCFG then...
I just found some manual [1], the command need an '?' after it, thus should be
'AT^SYSCFG?'.
[1] http://www.letswireless.com.cn/cn/down/download.asp?id=81t=en ,
section 10.6 on page 43
Yeah, we know that. We
d36dcdd2c13f01dafc994d9b60f68e568a8f8ea0 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Sun, 15 Jul 2012 18:26:11 +0200
Subject: [PATCH] huawei: limit the number of deferred tasks
The Huawei plugin requires to probe first the USB interface 0; all the other
probing
The Huawei plugin always starts probing USB interface 0; and it seems
that none of the 3 ttyACM ports given has usbif 0, so never starts
probing the other ports. The plugin should possibly wait up to N
seconds
for usbif 0 to appear, and keep on probing normally if it doesn't
appear
in that
Hello, it works now! nearly perfect, but still another problem, how
could I lock the
network to 3g(td-scdma), and not automaticly switch back and forth between
3g and 2g(edge, sometimes even gprs)? My signal here is sometimes a little low,
and I'd like to not switch back to 2g.
I tried the
Hello, it works now! nearly perfect, but still another problem, how
could I lock the
network to 3g(td-scdma), and not automaticly switch back and forth between
3g and 2g(edge, sometimes even gprs)? My signal here is sometimes a little
low,
and I'd like to not switch back to 2g.
I tried the
It's a Huawei ET8282, TD-SCDMA HSDPA 3g mobile broadbrand card.
It's on ExpessCard, but appears to be a stand USB device in my Debian
Squeeze Box.
I have made it to work with wvdial by usb-modeswitch. yes, it's a device
with id 12d1:1da1, after eject the cd, it became 12d1:1d09, and
Hey,
It's a Huawei ET8282, TD-SCDMA HSDPA 3g mobile broadbrand card.
It's on ExpessCard, but appears to be a stand USB device in my Debian
Squeeze Box.
I have made it to work with wvdial by usb-modeswitch. yes, it's a device
with id 12d1:1da1, after eject the cd, it became 12d1:1d09, and
or not, as I don't have any Huawei modem around
to play with. Please attach debug logs in any case.
Cheers!
--
Aleksander
From d36dcdd2c13f01dafc994d9b60f68e568a8f8ea0 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Sun, 15 Jul 2012 18:26:11 +0200
Subject: [PATCH
The Huawei plugin always starts probing USB interface 0; and it seems
that none of the 3 ttyACM ports given has usbif 0, so never starts
probing the other ports. The plugin should possibly wait up to N seconds
for usbif 0 to appear, and keep on probing normally if it doesn't appear
in that
Hey Greg,
I was wondering if there's any effort going on to support MBIM devices
on Linux?
No plans yet for ModemManager (see thread [1]). Is there any device out
there which already supports that protocol?
Cheers,
[1]
On 07/12/2012 11:12 PM, Ben Chan wrote:
expire_signal_quality() / mm_iface_modem_update_access_technologies()
may be called after the DBus object skeleton is removed in
mm_iface_modem_shutdown() and before their associated timeout source is
removed (in *_context_free) due to destruction of the
Hey Ben,
Yep, that works too. How about this?
diff --git a/src/mm-iface-modem.c b/src/mm-iface-modem.c
index 49a18a5..7b44d6a 100644
--- a/src/mm-iface-modem.c
+++ b/src/mm-iface-modem.c
@@ -3676,6 +3676,14 @@ mm_iface_modem_shutdown (MMIfaceModem *self)
{
g_return_if_fail
When the serial port is not open, internal_queue_command
(mm-serial-port.c) invokes serial_probe_at_parse_response
(mm-port-probe.c) with a NULL response. This patch modifies
serial_probe_at_parse_response to handle that properly.
---
src/mm-port-probe.c |2 +-
1 files changed, 1
Is it safe to assume that response processor(s) can handle NULL gchar*?
I guess we need to check that in response processors as well.
Yes, there aren't so many response processors out there, as they're only
used during probing time (once the modem is created we use
How do I get NM to start modem-manager with --log-level=WARN?
You'll need to avoid having NM do the dbus-activated start. You can
avoid this by moving the modem-manager binary from
/usr/sbin/modem-manager to another location, like /modem-manager. Once
you do that, you'll need to launch the
On 07/12/2012 05:28 PM, Ben Chan wrote:
When the serial port is not open, internal_queue_command
(mm-serial-port.c) invokes serial_probe_at_parse_response
(mm-port-probe.c) with a NULL response. This patch modifies
serial_probe_at_parse_response to handle NULL response properly.
---
Hey Ben,
expire_signal_quality() may be called after the DBus object skeleton is
removed in mm_iface_modem_shutdown() and before
signal_quality_update_context_free() is called due to the destruction of
the modem object. This patch prevents expire_signal_quality() from
accessing an already
Hey,
How do I get NM to start modem-manager with --log-level=WARN?
TIA
You'll need to avoid having NM do the dbus-activated start. You can
avoid this by moving the modem-manager binary from
/usr/sbin/modem-manager to another location, like /modem-manager. Once
you do that, you'll need to
Hey Bjørn,
I noticed that there had been significant progress in the qmi-support
branch, so I thought I might give it a try.
Ah, so much to do in that branch... :-)
It currently just grabs a QMI port when available, nothing else yet, and
that itself may be buggy. I'll be improving that over
Hey,
Yes, I am sure about connectivity. I can use it on my mate's Win OS.
PFA MM and NM logs http://old.nabble.com/file/p33878121/nm.log.txt
nm.log.txt , http://old.nabble.com/file/p33878121/modem.log.txt
modem.log.txt
The device is a Via Telecom model CBP7.0, which reports both CDMA
Hey,
http://old.nabble.com/file/p33876035/kern.log kern.log
http://old.nabble.com/file/p33876035/lshal.log lshal.log
http://old.nabble.com/file/p33876035/m-tool.log m-tool.log
http://old.nabble.com/file/p33876035/searchusb.log searchusb.log
On 05/20/2012 03:47 PM, ezee wrote:
Hi Aleksander,
Thanks for your reply :)
Yes, I am sure about connectivity. I can use it on my mate's Win OS.
Could you please refer me to any guide to create ModemManager log?
http://live.gnome.org/NetworkManager/Debugging
or
On 18/05/12 22:46, PongráczI wrote:
# Bus 001 Device 002: ID 12d1:1c05 Huawei Technologies Co., Ltd. E173s 3G
broadband stick (modem on)
# Modemmanager output (debug log, this part repeating again and again,
continuously):
* info [main.c:167] main(): ModemManager (version 0.5.2.0) starting...
On 05/19/2012 07:42 PM, PongráczI wrote:
Thank you!
You were right, meanwhile we realized, it is an ancient package from the
past, when we used the MM from git, because the package system did not
include these packages.
So, I guess, it is solved by cleaning up the system.
Yes, that
I found this in my logs, a huge amount:
May 18 07:52:40 localhost modem-manager[1998]:
mm_serial_port_queue_process: (ttyUSB2) response array is not empty when
using cached reply, cleaning up 26 bytes
May 18 07:52:56 localhost modem-manager[1998]:
mm_serial_port_queue_process: (ttyUSB2)
Given that the $NWQMISTATUS reply is not bearer-specific (reports
overall status of the modem), I was thinking in moving the periodic
connectivity check to MMIfaceModem instead, and plug it in using the
same logic as e.g. the signal quality check. In that way, other
On 05/04/2012 07:14 PM, Jason Glasgow wrote:
In the XML comments we have descriptions of the keys returned in
GetStatus, Scan, and the arguments to Simple.Connect and others. These
key names are not part of the generated ModemManager-names.h header file.
Attached is a patch that allows us
Hey Nathan,
On 05/02/2012 09:42 PM, Nathan Williams wrote:
Kind of a monster of a patch, but walking you all through my development
steps didn't seem like it would really help anybody.
Thanks; I pushed it, along with some additional fixes, to a new
'samsung-plugin-chromium' branch in my MM
Subject: [PATCH 1/5] novatel: Add support for connecting to
specific APNs and
specifying username/password.
While here, pass through the other relevant bearer properties.
Did you have time to check the 'bearer-properties' branch I
Hey Nathan,
static void
+poll_connection_ready (MMBaseModem *modem,
+ GAsyncResult *res,
+ MMBroadbandBearerNovatel *bearer)
+{
+const gchar *result;
+GError *error = NULL;
+
+result = mm_base_modem_at_command_finish (modem, res,
Hey Nathan,
On 04/26/2012 01:58 AM, Nathan Williams wrote:
1. When a new single-part message arrives, an Added signal is sent but
the Completed signal is not sent.
We emit Added if we got a singlepart message or whenever we get the
first part of a multipart message. In the latter case, the
Also, do we plan to support the older non-LTE/non-QMI devices with the
'novatel' plugin? Or should we rename this plugin to 'novatel-qmi' and
have a 'novatel-gsm' and 'novatel-cdma' for the legacy (MDM 9xxx)
devices?
The current novatel plugin in git master should really be novatel-4g
Hey Nathan,
On 05/01/2012 06:07 PM, Nathan Williams wrote:
Subject: [PATCH 1/5] novatel: Add support for connecting to specific APNs and
specifying username/password.
While here, pass through the other relevant bearer properties.
Did you have time to check the 'bearer-properties' branch I
On 05/01/2012 06:07 PM, Nathan Williams wrote:
Date: Thu, 22 Mar 2012 16:18:24 -0400
Subject: [PATCH 2/5] novatel: Use the ALLOWED_SINGLE_AT property. Saves 5
seconds on probing.
Is it that the modem exposes only one AT port? Or that it exposes
multiple ports but only one is needed? The
On 05/01/2012 06:09 PM, Nathan Williams wrote:
+static gboolean
+poll_connection (MMBroadbandBearerNovatel *bearer)
+{
+mm_base_modem_at_command (
+bearer-priv-connection_modem,
+$NWQMISTATUS,
+3,
+FALSE,
+
On 05/01/2012 06:09 PM, Nathan Williams wrote:
Subject: [PATCH 5/5] novatel: Remove band-setting implementation to improve
connections
The $NWBAND command seems to disturb the internal state of the modem
such that it is unlikely to connect to the network, and produces
widely varying error
On 05/01/2012 06:08 PM, Nathan Williams wrote:
Subject: [PATCH 3/5] novatel: Implement load_access_technologies.
Change-Id: Ib503d900850d3754d79525dbc9a40b7b9c221dd7
Pushed this one, thanks.
--
Aleksander
___
networkmanager-list mailing list
Hey,
On 05/02/2012 04:43 PM, Nathan Williams wrote:
+networkmanager-list
On Wed, May 2, 2012 at 10:43 AM, Nathan Williams n...@google.com
mailto:n...@google.com wrote:
On 05/01/2012 06:07 PM, Nathan Williams wrote:
Subject: [PATCH 1/5] novatel: Add support for connecting
On 05/02/2012 04:53 PM, Nathan Williams wrote:
On Wed, May 2, 2012 at 6:11 AM, Aleksander Morgado
aleksan...@lanedo.com mailto:aleksan...@lanedo.com wrote:
On 05/01/2012 06:07 PM, Nathan Williams wrote:
Date: Thu, 22 Mar 2012 16:18:24 -0400
Subject: [PATCH 2/5] novatel: Use
I'm leery of including code that can run the $NWBAND command to set the
modem's state, since as far as I can tell it simply breaks the modem, at
least until it is power-cycled. Not setting the bands in the simple
connect process unless explicitly requested seems like a fine change on
its
On 05/02/2012 07:11 PM, Nathan Williams wrote:
Needed by the Novatel plugin.
- Nathan
0001-Add-a-utility-routine-to-do-ITU-V.250-quoting-of-str.patch
From 26d1efa84314a77432aa0121aaa978f8abb4f598 Mon Sep 17 00:00:00 2001
From: Nathan Williams n...@chromium.org
Date: Fri, 23 Mar
401 - 500 of 664 matches
Mail list logo
