On Thu, Feb 16, 2017 at 1:31 PM, Colin Helliwell
wrote:
>
> I'm back on this, trying to do it properly. I've removed by mod to
> mm-plugin.c, and added a udev tag
>
> G_MODULE_EXPORT MMPlugin *
> mm_plugin_create (void)
> {
> static const gchar *subsystems[] =
On Thu, Feb 16, 2017 at 2:24 PM, Colin Helliwell
wrote:
>>> (By the way - the configure summary is reporting "ModemManager 1.7.0"?)
>>
>>That is normal. The version in git master is 1.7.x; the next stablemajor
>>release will be 1.8.0.
>
> Is there a schedule for
On 16 February 2017 at 11:23 colin.helliw...@ln-systems.com wrote:
>
> I’m doing quite a bit of debug of a plugin, and simply copying the new .so
> into the plugins directory. Oh, and also rebuilding the ModemManager now and
> again.
>
> This did work a few times, but I’ve got a situation
> On 15 February 2017 at 08:49 Aleksander Morgado
> wrote:
>
>> (By the way - the configure summary is reporting "ModemManager 1.7.0"?)
>
>That is normal. The version in git master is 1.7.x; the next stablemajor
>release will be 1.8.0.
Is there a schedule for
On Thu, Feb 16, 2017 at 12:23 PM, wrote:
> I’m doing quite a bit of debug of a plugin, and simply copying the new .so
> into the plugins directory. Oh, and also rebuilding the ModemManager now and
> again.
>
> This did work a few times, but I’ve got a situation
> On 15 February 2017 at 18:04 Aleksander Morgado
> wrote:
>
...
>
> The purpose of ID_MM_PHYSDEV_UID is to have the user provide a "unique
> id" which may be used as name when referencing a modem, e.g. "mmcli -m
> NAME"; but that also serves the purpose of binding
> On 14 February 2017 at 23:07 Aleksander Morgado
> wrote:
>
> On Tue, Feb 14, 2017 at 10:51 AM, Colin Helliwell
>
> wrote:
>
> > > > > I'm not confident of correctly interpreting the regex in
> > > > > smong_query_ready() (let
On Thu, Feb 16, 2017 at 11:22 AM, Colin Helliwell
wrote:
>> > > > > I'm not confident of correctly interpreting the regex in
>> > > > > smong_query_ready() (let alone fixing it properly!), but I wonder if
>> > > > > the SMONG problem is that it's getting an
Im am trying to lock to 4g only.
Modes| supported: 'allowed: 2g, 3g, 4g; preferred: none'
|current: 'allowed: 2g, 3g, 4g; preferred: none'
root@LEDE:~# mmcli -m 0 --set-allowed-modes=4g
error: couldn't set current modes:
On Thu, Feb 16, 2017 at 4:29 PM, Russ Westrem
wrote:
> Im am trying to lock to 4g only.
>
> Modes| supported: 'allowed: 2g, 3g, 4g; preferred: none'
>|current: 'allowed: 2g, 3g, 4g; preferred: none'
>
>
>
> root@LEDE:~# mmcli -m 0
On Feb 16, 2017 2:00 PM, "Dan Williams" wrote:
On Thu, 2017-02-16 at 17:36 +0100, Aleksander Morgado wrote:
> On Thu, Feb 16, 2017 at 4:29 PM, Russ Westrem
> wrote:
> > Im am trying to lock to 4g only.
> >
> > Modes| supported: 'allowed:
11 matches
Mail list logo