Re: [PATCH] u-blox: ignore non-AT ttyACM interfaces

2018-04-30 Thread Aleksander Morgado
On Tue, Apr 10, 2018 at 7:30 PM, Matthew Starr wrote: > For the TOBY-R2, LISA-R2, and LARA-R2, the only valid AT ports are > ttyACM0, ttyACM1, and ttyACM2. All other ttyACM ports cause MM to > wait 20-30 seconds probing the port on startup. > > Ignoring the non-AT ttyACM

Re: [PATCH] u-blox: ignore non-AT ttyACM interfaces

2018-04-11 Thread Aleksander Morgado
> > Until the GPS support is added into the u-blox plugin or something like the > ID_MM_GPS_PORT flag is added, could MM safely just ignore the GPS port like > in this patch? Once support is added, the flagging of the GPS ports can be > changed/removed. Right now there is a 20 second timeout

RE: [PATCH] u-blox: ignore non-AT ttyACM interfaces

2018-04-11 Thread Matthew Starr
> -Original Message- > From: Aleksander Morgado [mailto:aleksan...@aleksander.es] > Sent: Wednesday, April 11, 2018 3:21 AM > To: Dan Williams > Cc: Matthew Starr; modemmanager-devel@lists.freedesktop.org > Subject: Re: [PATCH] u-blox: ignore non-AT ttyACM interfac

Re: [PATCH] u-blox: ignore non-AT ttyACM interfaces

2018-04-11 Thread Dan Williams
Sent: Tuesday, April 10, 2018 1:17 PM > > > > To: Matthew Starr; modemmanager-devel@lists.freedesktop.org > > > > Subject: Re: [PATCH] u-blox: ignore non-AT ttyACM interfaces > > > > > > > > On Tue, 2018-04-10 at 17:30 +, Matthew Starr wrote: > > > >

RE: [PATCH] u-blox: ignore non-AT ttyACM interfaces

2018-04-11 Thread Matthew Starr
> -Original Message- > From: Reinhard Speyerer [mailto:rs...@arcor.de] > Sent: Tuesday, April 10, 2018 4:23 PM > To: Matthew Starr > Cc: Dan Williams; modemmanager-devel@lists.freedesktop.org > Subject: Re: [PATCH] u-blox: ignore non-AT ttyACM interfaces > > On Tu

Re: [PATCH] u-blox: ignore non-AT ttyACM interfaces

2018-04-11 Thread Aleksander Morgado
> A number of plugins do this, like mbm or Cinterion. But unfortunately > the ublox plugin doesn't support GPS yet, and it turns out we can't yet > prevent those known GPS ports from being probed either since they get > tagged during the "grab" phase after probing. So nevermind... (though >

Re: [PATCH] u-blox: ignore non-AT ttyACM interfaces

2018-04-10 Thread Dan Williams
On Tue, 2018-04-10 at 19:58 +, Matthew Starr wrote: > > -Original Message- > > From: Dan Williams [mailto:d...@redhat.com] > > Sent: Tuesday, April 10, 2018 1:17 PM > > To: Matthew Starr; modemmanager-devel@lists.freedesktop.org > > Subject: Re: [PATCH

Re: [PATCH] u-blox: ignore non-AT ttyACM interfaces

2018-04-10 Thread Dan Williams
On Tue, 2018-04-10 at 17:30 +, Matthew Starr wrote: > For the TOBY-R2, LISA-R2, and LARA-R2, the only valid AT ports are > ttyACM0, ttyACM1, and ttyACM2. All other ttyACM ports cause MM to > wait 20-30 seconds probing the port on startup. > > Ignoring the non-AT ttyACM ports allows MM to not

[PATCH] u-blox: ignore non-AT ttyACM interfaces

2018-04-10 Thread Matthew Starr
For the TOBY-R2, LISA-R2, and LARA-R2, the only valid AT ports are ttyACM0, ttyACM1, and ttyACM2. All other ttyACM ports cause MM to wait 20-30 seconds probing the port on startup. Ignoring the non-AT ttyACM ports allows MM to not wait 20-30 seconds probing and therefore startup much faster with