Hello!
Out of curiosity - how did it happen the USB port isn't wired? Plain curiosity.
:)
Enrico
On Mon, 18 Nov 2019, Andrés Calderón wrote:
Date: Mon, 18 Nov 2019 17:50:43
From: Andrés Calderón
To: modemmanager-devel@lists.freedesktop.org
Subject: Is there support for modem with a single
Hey
>
> "Couldn't refresh signal quality: 'No AT port available to run command'"
>
The previous log message is expected once the TTY goes into connected mode.
> Can ModemManager work with a single physical UART port? any guide here?
>
Yes it can, you should not need any special setup to handle
Hi,
I'm connected to a modem with a *single* serial port (Simcom SIM5320A with
the USB port unwired)
I can connect to Internet using the old way (writing my own chat scripts).
But I couldn't do it using modemmanager. I have a lot of error messages
from ModemManeger like that:
"Couldn't refresh
>
> But if you wanted to, you
> could pass --enable-plugins=X,Y,Z or something and end up with a
> smaller binary.
I like that. It put's the optimization in the hands of the builder which
seems more than fair to have integrator's figure out what goes in
or out & dependency chains. It also will
Hey Dan!
> > > > Is there any benefit in keeping per-vendor plugins installed as
> > > > separate .so files and loaded during runtime?
> > >
> > > I think it'd be a shame to lose this architecture. On embedded
> > > systems saving resources is always desirable and I remove
> > > all vendor
On Sun, 2019-11-17 at 15:16 +0100, Aleksander Morgado wrote:
> > > Is there any benefit in keeping per-vendor plugins installed as
> > > separate .so files and loaded during runtime?
> >
> > I think it'd be a shame to lose this architecture. On embedded
> > systems saving resources is always
Ok, I'll now will try to see if i can break it.
BTW - is there any plan to try backporting MM OpenWRt feeds to 19.07? A good
number of feeds is being backported it seems, so it may still be possible.
On Mon, 18 Nov 2019, Aleksander Morgado wrote:
Date: Mon, 18 Nov 2019 12:25:39
From:
Hey!
> Aleksander and Bjørn, I am CC'ing you since this question came up reading
> your discussion about udev rules usage.
>
> So, modems discovery mechanism in ModemManager is implemented via
> --report-kernel-event.
> And we have --report-kernel-event-auto-scan as well.
>
> the current method
Hello guys!
Aleksander and Bjørn, I am CC'ing you since this question came up reading your
discussion about udev rules usage.
So, modems discovery mechanism in ModemManager is implemented via
--report-kernel-event.
And we have --report-kernel-event-auto-scan as well.
the current method of
