On 05/02/2012 05:19 PM, Aleksander Morgado wrote:
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
On 05/02/2012 07:13 PM, Nathan Williams wrote:
0001-novatel-Use-the-ALLOWED_SINGLE_AT-property.-Saves-5-.patch
From ad53cf829f42a5570e8eab46bb1ab0065110f3d8 Mon Sep 17 00:00:00 2001
From: Nathan Williams n...@chromium.org
Date: Thu, 22 Mar 2012 16:18:24 -0400
Subject: [PATCH] novatel:
On 05/02/2012 07:14 PM, Nathan Williams wrote:
0001-novatel-Poll-for-whether-the-connection-still-exists.patch
From 976d9e914a07d8757054088025b26587e7c1853e Mon Sep 17 00:00:00 2001
From: Nathan Williams n...@chromium.org
Date: Fri, 6 Apr 2012 13:12:15 -0400
Subject: [PATCH] novatel: Poll
Testing for a QMI port is currenly non-trivial. You will have to modify
the cdc-wdm or qmi_wwan drivers to bind to the device and see if it
replies to QMI. A nice test util for someone to write (I've been
planning to, but haven't had the time and probably won't either...)
would be something
Hey,
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 if there is a +CFUN=1 command sent alone in the logs).
On 18/04/12 18:43, spicykappella Gmail wrote:
On 18/04/2012 08:39, spicy kappella wrote:
Please provide debug output of modemmanager.
--
Marius
Attachment provided
And will send a new log from a newer build(newer versions of mm nm)
once i return back(on a trip)
Yes, please try with a
Too many different issues in the same email :-) It is much better to
provide separate patches/emails for different issues, so that they can
be discussed in different threads and followed separately.
Aleksander, thank you for your reply. I reworked my patches, and do as
you said: provide
On 16/04/12 17:40, Alexander Orlov wrote:
ZTE modem stays connected and consumes power when disabled. This patch
uses +CFUN=4 command to turn off radio module. Command +CFUN=0 gains
more power savings, but is more dangerous.
--- a/plugins/mm-modem-zte.c2012-03-13 23:06:11.0 +0400
On 16/04/12 18:00, Alexander Orlov wrote:
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
Hi Tore,
This patch makes it possible to use MM to set up PDP contexts with
PDP types other than 'IP', which is particularly useful when trying
to use the 'IPV6' or 'IPV4V6' PDP types defined in recent 3GPP specs.
If ip-type isn't specified, 'IP' will be used by default, due to the
fact that
On 04/13/2012 04:57 PM, Nathan Williams wrote:
As described. This replaces a regexp of ?\S*? , which doesn't match
the string Line 1 because of the embedded whitespace, with a somewhat
more elaborate regular expression that does. It
also accommodates escaped quotes inside the quoted string.
On 04/13/2012 05:22 PM, Nathan Williams wrote:
Pretty much what it says.
With this and the prior patch mmcli -m 0 now shows me the modem's number.
- Nathan
Pushed, thanks.
--
Aleksander
___
networkmanager-list mailing list
On 04/13/2012 07:58 PM, Tore Anderson wrote:
This patch makes it possible to use MM to set up PDP contexts with
PDP types other than 'IP', which is particularly useful when trying
to use the 'IPV6' or 'IPV4V6' PDP types defined in recent 3GPP specs.
If ip-type isn't specified, 'IP' will be
Hey hey Tore,
I tried to simplify a bit the handling of the Bearer properties in MM;
the rework is available in the 'bearer-properties' branch in the
following git repo: git://gitorious.org/aleksander/modemmanager.git
Hi Aleksander,
I just tried the branch in order to hopefully be able
Hey,
For anyone interested, there's some work ('qmi-wdm' branch in the
upstream MM tree) to be able to grab qmi/wdm ports, currently just
exposed as raw MMPort objects. Of course, you'll need a device with such
ports (got a Pantech UML290 here) and a recent enough kernel with
Björn's
For anyone interested, there's some work ('qmi-wdm' branch in the
upstream MM tree) to be able to grab qmi/wdm ports, currently just
exposed as raw MMPort objects. Of course, you'll need a device with
such ports (got a Pantech UML290 here) and a recent enough kernel with
Björn's qmi_wwan
Hey,
- Disabling the modem for power savings (using +CFUN=0). Also,
the command Z E0 V1 X4C1 +CMEE=1;+CFUN=1; was not properly parsed
(the modem just ignores +CMEE=1 and +CFUN=1), so I broke it for two
commands. While enabling the modem, it gives error for +CPMS command
for the
On 04/02/2012 09:16 PM, Joachim wrote:
I'm trying to connect using Huawei E169. I configured usb_modeswitch.
Then I created connection using nm-connection-editor. When I plug in the
modem I applet lists mobile connection I created, but I can't connect
(when I click it it does nothing).
Hey Nathan list,
I tried to simplify a bit the handling of the Bearer properties in MM;
the rework is available in the 'bearer-properties' branch in the
following git repo: git://gitorious.org/aleksander/modemmanager.git
Basically, the base MMBearer will keep a MMBearerProperties object
around,
Hey Thomas,
i had an active connection (latest MM_06 from git) with the iridium
modem but after a while, the modem disconnected. After that, the modem
was no longer detected by MM.
Then i tried to redetect serial modems but without success.
dbus-send --system --type=method_call --print-reply
Hey,
tried again to setup a iridium connection but now i get a lot of Not
getting signal quality, not registered yet messages and the connection
doesn't seem to work at the beginning. after some tries (i think 3x),
the connection worked. here are the logs:
Are there any problems with this
Hey Thomas,
I should have probably read the emails in order...
i tried to setup a connection with the iridium modem but the connection
couldn't be enabled. after that, the modem was disabled and no longer
detected by MM. I restarted MM then and the modem was detected again.
...
the Iridium Modem is not detected (latest git version from 06 branch)
when the modem is already connected and MM starts. This can happen
because the modem has an external power supply so the OS can restart but
the modem is still connected.
Is it possible to detect the state and disconnect the
That's 1/2 a lie, they support RSSI, which is the value they return from
AT+CSQ. RSSI is an arbitrary unit that's assumed to be linear in scale
(unlike dBm). CSQ is defined to be 0 - 31, and internally in NM that's
normalized to a 0...100 scale. Technically GetSignalQuality*does*
return
The ChromeOS connection manager would like to talk with both old-style
ModemManager (org.freedesktop.ModemManager) and new-style ModemManager
(org.freedesktop.ModemManager1) modem managers at the same time.
Unfortunately, the old header (mm-modem.h) is not compatible with the
new headers
Hey Marek,
I can't connect to 4G using Huawei E398 on Ubuntu 11.10. Connection to
3G work fine.
Are you planning to implement in the near future 4G network service in
network-manager? Can I help somehow?
There is work in progress in ModemManager to support LTE devices.
Which are the
Hoola,
I see that NM request signal quality from 3G modem. I need dbm or
similar. Any command line option while modem it is locked by NM.
I need obtain dbm or result of at+csq
You can query the signal quality retrieved by NM/MM directly using the
DBus interface and the 'dbus-send' command
Hey hey,
So Dan created a MM_06 branch the other day from git master. Whenever a
0.6 release comes out it will be with extended RS232 support, Cinterion
and Iridium plugins and some more things. MM_06 is compatible with MM_05.
Today I merged the '06-api' branch into git master. Unlucky name
A possible fix to handle the case where we don't know how much
we can
read would be to try to read the first bytes of the record (3 or
4 or 5
just in case) to get the full record length of the record,
assuming 1-3
bytes max for the
Hey Nathan,
On 03/01/2012 02:28 PM, Aleksander Morgado wrote:
-/* First byte is metadata; remainder is GSM-7 unpacked into octets;
convert to UTF8 */
+/* Bits in the first byte specify rules for name display */
+if (bin[0] == '\xFF' bin[1] == '\xFF
Hey,
A possible fix to handle the case where we don't know how much
we can
read would be to try to read the first bytes of the record (3 or
4 or 5
just in case) to get the full record length of the record,
assuming 1-3
bytes max for
Hey Nathan,
Also, if we do expose these two properties we also need to load and
expose the SPDI network list, or the properties will be useless.
Here's a patch to do that. There's a bit of annoying fighting with gchar
** and gdbus's idea of constness, but it seems reasonable
The '06-api' branch has a new property
(MM_PLUGIN_BASE_ALLOWED_SINGLE_AT) for MMPluginBase, which allows
specifying that only one AT port is expected in the modem [1]. If this
property is set, whenever the first AT port is grabbed, all the
remaining port probings will cancel their
On 03/09/2012 12:16 AM, Nathan Williams wrote:
There's a bit of annoying fighting with gchar ** and gdbus's idea of
constness, but it seems reasonable otherwise.
Just modify load_spdi_finish() (and parse_spdi()) to return a gchar **
(without any const); and then explicitly cast to (const gchar
Hey hey,
The new ModemManager codebase in the 06-api branch is almost fully
ready, and some of the plugins are even completely ported (e.g. Nokia,
Iridium, Motorola and Cinterion).
Any help, either writing the port of remaining plugins or testing
already ported plugins, is highly appreciated.
Hey hey hey,
NetworkManager can now be improved to support the new ModemManager1 DBus
interface implemented in the 06-api branch, directly using
GObject-friendly libmm-glib. Ideally, I guess that NM can be hacked to
temporarily support both the old ModemManager and the new ModemManager1
Hey,
This is required for properly displaying
local-operator-vs-home-provider information, per 3GPP
(31.102 section 4.1.2 on EF_SPN and 22.101 Annex A).
For anyone else checking, that's section 4.2.11 in release 11 of the
document.
Suggestions welcome on the long and somewhat unwieldy
Hey Dan Nathan,
If we did combine both bits into one property, then we'd get the
following logic:
enum {
DISPLAY_UNRESTRICTED = 0,
DISPLAY_REGISTERED = 1,
DISPLAY_SPN = 2
} DisplayName;
display = DISPLAY_UNRESTRICTED
if (registered network is well-known) {
if (b1 ==
it?
Cheers!
--
Aleksander
From 6959af8d54d25c3490372129a7022e0889b5fc05 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Thu, 9 Jun 2011 18:26:33 +0200
Subject: [PATCH] modem-manager: query desired IP timeout value
Different modem implementations in ModemManager are now able
+if (response-data[i] == '\r' response-data[i + 1] ==
'\n') {
+if (i 0)
+g_byte_array_remove_range (response, 0, i);
+else
+/* good, we're already started with CRLF */
+break;
The else + comment there doesn't
48ce30df846bb2a742943d7b4d4bb1d695cc0d9c Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Wed, 11 Jan 2012 01:33:05 +0100
Subject: [PATCH] at-serial-port: implement built-in echo/garbage removal
We expect the responses to start always with CRLF. We just remove anything
On 02/13/2012 09:33 PM, Andrew Bird (Sphere Systems) wrote:
Will this redesign allow you to change the udev rule assigned names
from
ID_MM_ZTE_PORT_TYPE_MODEM
to
ID_MM_PORT_TYPE_MODEM
etc? I don't think there can be any clash requiring a different namespace as
the items are fully
Hey Dan,
I really do like the new approach, and I would even include it for
0.5.x. Some comments below.
The core problem was that some devices need to specify a PPP port that's
*not* the primary port. In these cases the primary port always stays
open for command and status, while some other
On 02/13/2012 08:37 PM, Aleksander Morgado wrote:
Hey Dan,
I really do like the new approach, and I would even include it for
0.5.x. Some comments below.
I ported this new behaviour to a new '06-api-ports' branch upstream;
will wait for more comments before merging it into '06-api
Should I watch the cgit to get the latest patch against this weird
behaviour of
this specific modem?
Yes.
Dan
Hi, sorry for the question, do you have a schedule for this fix in master or
MM_05 branch?
I was hoping that Aleksander meant to do it and that he'd get to it
soon,
Any idea what command Gammu sends? Does it use PDU mode or text mode to
send it? Is it possible for you to get a log of the serial traffic when
using Gammu so we can compare to what ModemManager does?
Dan
Hi,
In attached you can find the gammu log for a successfully sent sms.
I had to
Hey,
I would like to inform you about my test result today.
I downloaded the master repository from the freedesktop git and I compiled it
successfully.
Note that MM_05 also has all latest fixes now.
So, the latest sms-get.py get both sms messages correctly from the modem,
which is
That CMGS command seems the proper one, so not sure why the ZTE modem
didn't like it. Could you run AT+CMGS=? in minicom and send back the
result?
I turned off the mobile internet connection.
Here it is:
root@antiX1 :~# echo -e AT+CPIN?\r /dev/ttyUSB1
root@antiX1 :~# echo -e
don't use GValueArrays there.
Cheers,
--
Aleksander
From 86cec854ed07848d2d0df9341d8f20d3c4d51616 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Tue, 7 Feb 2012 12:56:45 +0100
Subject: [PATCH] build: do not warn about using deprecated methods
GValueArray is deprecated
Hey hey,
I followed you advice, I downloaded the MM_05 branch and compiled in my
system. I did not changed (means: compiled) other things on the system, so,
the rest is in the same version I wrote above.
After the installation, I fixed a path problem (previously I compiled it with
On Ubuntu 11.10 there is problem with connection via modem Huawei E220.
On Ubuntu 11.10 the NetworkManager is in version 0.9.1.90-0ubuntu5.1
On Ubunto 11.04 there is version 0.8.4~git.20110319t175609.d14809b-0ubuntu3
The issue for Ubuntu was submitted:
If you just need to store a signed integer as the value of an entry in
the hash table, you can better use GINT_TO_POINTER (integer) and
GPOINTER_TO_INT (pointer), instead of packing the integer into a GValue.
I need it in a format that DBus will be okay with -- NetworkTimezone
is defined
I'm not sure why we would include leap seconds info here. Leap seconds
are adjustments to UTC itself, so if the time retrieved from
GetNetworkTime() is always UTC, there is no need for that, as far as I
can tell.
I'm including it because one of our modems (the Gobi) exports it as
part of
+
+property name=NetworkTimezone type=a{sv} access=read
+ tp:docstring
+The timezone data provided by the network. It may include one of
more
+of the following fields:
+
+'offset': offset of the timezone from UTC, in minutes (including DST,
+
+static GValue *
+int_to_gvalue (gint i)
+{
+GValue *v = g_slice_new0 (GValue);
+g_value_init (v, G_TYPE_INT);
+g_value_set_int (v, i);
+return v;
+}
+
+static void
+value_destroy (gpointer data)
+{
+GValue *v = (GValue *) data;
+g_value_unset (v);
+
On 07/31/2011 12:52 AM, Dan Williams wrote:
On Thu, 2011-06-30 at 18:18 -0400, Eric Shienbrood wrote:
I can look at doing that. What should we call it? I think MSISDN is a
GSM term. How does GetPhoneNumber() sound?
Hm, old message. Yes, that method sounds fine.
Where did this end up?
On Thu, 2011-06-30 at 18:18 -0400, Eric Shienbrood wrote:
I can look at doing that. What should we call it? I think MSISDN is a
GSM term. How does GetPhoneNumber() sound?
Hm, old message. Yes, that method sounds fine.
Where did this end up?
Also, AT+CNUM may report a list of numbers,
I believe we need a MMBearerType enum in the 0.6 API, so that we can
tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
bearer. This property would be redundant for 3GPP-only, CDMA-only or
POTS-only modems, but would be mandatory if we have a mixed
3GPP(LTE)+CDMA bearer.
I believe we need a MMBearerType enum in the 0.6 API, so that we can
tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
bearer. This property would be redundant for 3GPP-only, CDMA-only or
POTS-only modems, but would be mandatory if we have a mixed
3GPP(LTE)+CDMA bearer.
I believe we need a MMBearerType enum in the 0.6 API, so that we can
tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
bearer. This property would be redundant for 3GPP-only, CDMA-only or
POTS-only modems, but would be mandatory if we have a mixed
3GPP(LTE)+CDMA bearer.
I believe we need a MMBearerType enum in the 0.6 API, so that we can
tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
bearer. This property would be redundant for 3GPP-only, CDMA-only or
POTS-only modems, but would be mandatory if we have a mixed
3GPP(LTE)+CDMA bearer.
Hey Marcel,
I believe we need a MMBearerType enum in the 0.6 API, so that we can
tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
bearer. This property would be redundant for 3GPP-only, CDMA-only or
POTS-only modems, but would be mandatory if we have a mixed
Hey,
I believe we need a MMBearerType enum in the 0.6 API, so that we can
tell in CreateBearer() whether we want a 3GPP or CDMA (well, or POTS)
bearer. This property would be redundant for 3GPP-only, CDMA-only or
POTS-only modems, but would be mandatory if we have a mixed
3GPP(LTE)+CDMA bearer.
ac838b97bbd346da55a8748147999ac9a0bb6296 Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Wed, 11 Jan 2012 01:33:05 +0100
Subject: [PATCH] at-serial-port: implement built-in echo/garbage removal
We expect the responses to start always with CRLF. We just remove anything
that comes before
Hey Dan,
On Ubuntu 11.10 there is problem with connection via modem Huawei E220.
On Ubuntu 11.10 the NetworkManager is in version 0.9.1.90-0ubuntu5.1
On Ubunto 11.04 there is version 0.8.4~git.20110319t175609.d14809b-0ubuntu3
The issue for Ubuntu was submitted:
Hey Dan,
One of the things that annoys me when using ModemManager is that
whenever I plug in a modem, I need to wait for the modem to get all
ports probed before I can see the NM applet updated with the new
broadband-related menu elements. In the worst case, where the modem just
returns
Hey Jason,
One of the things that annoys me when using ModemManager is that
whenever I plug in a modem, I need to wait for the modem to get all
ports probed before I can see the NM applet updated with the new
broadband-related menu elements. In the worst case, where the modem
Hey,
One of the things that annoys me when using ModemManager is that
whenever I plug in a modem, I need to wait for the modem to get all
ports probed before I can see the NM applet updated with the new
broadband-related menu elements. In the worst case, where the modem just
returns errors
Hey!
One thing I do see is 'ATD*99***1***2#CR'. This does not match the
settings I entered in.
Mobile Broadband Settings:
Connection name: ATT Mobile
IPv4 Method: Automatic(PPP)
Mobile Broadband Number: *99***1#
Mobile Broadband APN: isp.cingular
Type: Any
Allow roaming
PPP Authentication
On 12/21/2011 07:00 PM, John Hibbs wrote:
One thing I do see is 'ATD*99***1***2#CR'. This does not match the
settings I entered in.
Mobile Broadband Settings:
Connection name: ATT Mobile
IPv4 Method: Automatic(PPP)
Mobile Broadband Number: *99***1#
Mobile Broadband APN: isp.cingular
Type: Any
On Thu, 2011-06-30 at 11:51 -0500, Dan Williams wrote:
On Wed, 2011-06-22 at 16:35 +0200, Aleksander Morgado wrote:
Hi all,
Some fixes related to power-up/power-down some modems are available
in
the 'power-up-check-needed' branch in the following Gitorious repo
[1]:
git
I guess I don't have a problem with merging them, although strictly
speaking they refer to different things - locks vs. the PINs needed to
unlock those locks.
Yeah, you're totally right... but at the end the PIN/PUK codes are
directly related to facilities. E.g SIM
I guess I don't have a problem with merging them, although strictly
speaking they refer to different things - locks vs. the PINs needed to
unlock those locks.
Yeah, you're totally right... but at the end the PIN/PUK codes are
directly related to facilities. E.g SIM facility, has
According to the DBus specs [1], no element within a DBus interface can
start with a digit... so org.freedesktop.ModemManager1.Modem.3gpp is a
bad name. :-/
I will temporarily fallback to use:
org.freedesktop.ModemManager1.Modem.Modem3gpp (along with
(For ChromeOS development, I have rigged up a black-box ModemManager
test system under autotest, which creates a fake gudev device and a
fake modem that responds to AT commands to test this kind of thing. It
might be interesting to adapt it into the MM build system somehow;
right now it's
This was the only code in ModemManager using g_error(), and not
appropriately, I think.
The codebase is still mixed on how to handle errors compiling regular
expressions; other places in this file use g_assert(), while the rest
of the code tends to report some kind of parse-failure error.
Hey,
According to the DBus specs [1], no element within a DBus interface can
start with a digit... so org.freedesktop.ModemManager1.Modem.3gpp is a
bad name. :-/
I will temporarily fallback to use:
org.freedesktop.ModemManager1.Modem.Modem3gpp (along with
Hey Dan ttuttle,
The 0.6 API in MM has 2 properties named ModemCapabilities and
CurrentCapabilities. The current ones will be the ones reported by
+GCAP, but how do we know the modem ones?
I am assuming here that the ModemCapabilities will be different to the
CurrentCapabilities only when the
Hey Eric Dan,
On Fri, 2011-11-11 at 15:10 -0500, Eric Shienbrood wrote:
Subject: [PATCH] Added new property to track which facility locks are
enabled.
The property EnabledFacilityLocks on the .Modem.Gsm.Card interface
is a bit mask that indicates which of the various personalization
codes
Hey hey,
I guess I don't have a problem with merging them, although strictly
speaking they refer to different things - locks vs. the PINs needed to
unlock those locks.
Yeah, you're totally right... but at the end the PIN/PUK codes are
directly related to facilities. E.g SIM facility, has PIN
On Tue, 2011-11-22 at 12:21 +0100, Marcel Holtmann wrote:
Actually the HTTP header makes a lot more sense since once you
received
the valid one, you can just terminate the HTTP request and do not have
to deal with downloading the whole file.
You can possibly do just a HTTP HEAD request,
i use a Fasttrack xTend FXT009 with an external power supply.
i use MM on an embedded device and the modem is connected over usb.
When i have an active connection with the modem, remove the power from
the embedded device (so MM has no chance to cleanup anything) and then i
restart the
i use latest git-snapshot from ModemManager with NM 0.8.4. I try to use
a Fastttrack XTend FXT009.
I'm unable to get a working connection (see MM-Log).
After the connection, the modem does not answer to any AT-commands (see
the end of MM-Log).
Hmm, maybe we're dialing too early?
Hey Eric,
Some comments inline below.
On Wed, 2011-10-19 at 15:42 -0400, Eric Shienbrood wrote:
From b129d263ec1674462c218b4ec91260cf082bf77e Mon Sep 17 00:00:00 2001
From: Eric Shienbrood e...@google.com
Date: Thu, 11 Aug 2011 13:58:59 -0400
Subject: [PATCH] Added new property to track
On Wed, 2011-10-19 at 15:42 -0400, Eric Shienbrood wrote:
From 7c718db20958c200bc9dcb086763bfe0ebb91399 Mon Sep 17 00:00:00 2001
From: Eric Shienbrood e...@google.com
Date: Thu, 14 Jul 2011 19:11:54 -0400
Subject: [PATCH] Correctly track the number of SIM PIN retries left.
There are other
Hi everyone,
I just pushed a new '06-api' [1] development branch in the upstream
ModemManager git repo. This branch will hold the port of ModemManager to
the new 0.6 API, using GDBus and also targeting the new multi-mode LTE
devices. At some point it will also include the new libmm-glib [2] and
Supported and Allowed modes are modified to be bitmasks of MM_MODEM_MODE
values,
and preference of a specific mode is now given in the new PreferredMode
property and as an extra argument to the SetAllowedModes() call.
* Supported Modes: bitmask specifying which modes are supported by the
Hi all,
The ObjectManager interface was recently added as a standard interface
in DBus:
http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager
For the 0.6 API, we could be using this interface instead of the
proposed GetDevices() method, the Modems property and
So the real problem here is that the Cinterion modem sends a NUL byte
before the CONNECT response:
[mm-at-serial-port.c:298] debug_log(): (ttyS1): -- 'ATD*99***1#CR'
modem-manager[2621]: debug [1317807408.548825]
[mm-at-serial-port.c:298] debug_log(): (ttyS1): -- '\0'
. It modifies the common serial
parser, so not something Cinterion-specific, but the change is quite
small and shouldn't affect other plugins.
Cheers,
--
Aleksander
From 9d56d7b55c55859e259d22476eef515e90d84a0a Mon Sep 17 00:00:00 2001
From: Aleksander Morgado aleksan...@lanedo.com
Date: Thu, 13 Oct 2011 14
Hey Thomas,
To reproduce, i do the following:
1 ) stop NM, MM and disconnect the modem from power supply
2 ) connect the modem to power supply
3 ) start MM: modem-manager --debug --log-level=DEBUG
4 ) start NM: /etc/init.d/network-manager start
5 ) nmcli con up uuid
Here is a set of changes to the proposed MM DBus API. Some of them were
already
discussed some time ago in the following thread:
https://mail.gnome.org/archives/networkmanager-list/2011-May/msg00162.html
[PATCH 1/8] api: include ScanDevices() and SetLogging() in the new manager
Hey hey,
Supported and Allowed modes are modified to be bitmasks of MM_MODEM_MODE
values,
and preference of a specific mode is now given in the new PreferredMode
property and as an extra argument to the SetAllowedModes() call.
* Supported Modes: bitmask specifying which modes are
These methods were available in the old API, and are needed in the new one.
---
new/org.freedesktop.ModemManager1.xml | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/new/org.freedesktop.ModemManager1.xml
b/new/org.freedesktop.ModemManager1.xml
index
SIM objects will be listed as independent objects in the DBus API, and the 'Sim'
property in a given modem object will specify which SIM object is in use.
---
new/org.freedesktop.ModemManager1.Modem.xml |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git
Here is a set of changes to the proposed MM DBus API. Some of them were already
discussed some time ago in the following thread:
https://mail.gnome.org/archives/networkmanager-list/2011-May/msg00162.html
[PATCH 1/8] api: include ScanDevices() and SetLogging() in the new manager API
[PATCH 2/8]
New 'Manufacturer', 'Model' and 'Revision properties are added, all being
read-only strings.
---
new/org.freedesktop.ModemManager1.Modem.xml | 37 +--
1 files changed, 18 insertions(+), 19 deletions(-)
diff --git a/new/org.freedesktop.ModemManager1.Modem.xml
Modems which only expose a single port will not be able to update the signal
quality value while in connected mode. The signal quality value reported in this
case, while the modem is connected, will be the last signal quality value read
before the connection.
The additional boolean value proposed
Supported and Allowed modes are modified to be bitmasks of MM_MODEM_MODE values,
and preference of a specific mode is now given in the new PreferredMode
property and as an extra argument to the SetAllowedModes() call.
* Supported Modes: bitmask specifying which modes are supported by the
Makes more sense to have the enum named just as 'mode', as it applies to both
Supported and Allowed.
---
new/org.freedesktop.ModemManager1.Modem.xml |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/new/org.freedesktop.ModemManager1.Modem.xml
501 - 600 of 664 matches
Mail list logo
