Re: [PATCH] build: allow configuring filter policy to be used in the init files

2018-04-10 Thread Dan Williams
On Tue, 2018-04-10 at 15:08 +0200, Aleksander Morgado wrote: > Distributions wanting to use a different filter policy than the > DEFAULT one were advised to patch themselves the corresponding init > files. > > We now allow doing this directly at configure time by using a new >

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] u-blox: ignore non-AT ttyACM

Re: em7565 QDLoader

2018-04-10 Thread Russ Westrem
russ@russ-Studio-1745:/tmp$ sudo qmi-firmware-update --update-qdl -d 1199:9090 SWI9X50C_01.05.01.00.cwe SWI9X50C_01.05.01.00_GENERIC_001.028_000.nvu error: No serial device found to run QDL update operation russ@russ-Studio-1745:/tmp$ sudo qmi-firmware-update --update-qdl -d 1199

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

[PATCH] build: allow configuring filter policy to be used in the init files

2018-04-10 Thread Aleksander Morgado
Distributions wanting to use a different filter policy than the DEFAULT one were advised to patch themselves the corresponding init files. We now allow doing this directly at configure time by using a new `--with-filter-policy=[POLICY]' option that accepts one of "default", "strict", "paranoid"