Re: [PATCH] telit: don't ignore AT ports without an explicit port type hint tag

2017-03-16 Thread Aleksander Morgado
On Sat, Mar 11, 2017 at 1:29 PM, Aleksander Morgado wrote: > The telit plugin is based on two main ways of checking the purpose of > each port: udev tags flagging specific interfaces (with info taken > from Windows .inf drivers), or otherwise using AT#PORTCFG? to query >

Re: [PATCH] telit: don't ignore AT ports without an explicit port type hint tag

2017-03-13 Thread Dan Williams
On Sat, 2017-03-11 at 13:29 +0100, Aleksander Morgado wrote: > The telit plugin is based on two main ways of checking the purpose of > each port: udev tags flagging specific interfaces (with info taken > from Windows .inf drivers), or otherwise using AT#PORTCFG? to query > the modem about that

Re: [PATCH] telit: don't ignore AT ports without an explicit port type hint tag

2017-03-12 Thread Daniele Palmas
Hi Aleksander, 2017-03-11 13:29 GMT+01:00 Aleksander Morgado : > The telit plugin is based on two main ways of checking the purpose of > each port: udev tags flagging specific interfaces (with info taken > from Windows .inf drivers), or otherwise using AT#PORTCFG? to

[PATCH] telit: don't ignore AT ports without an explicit port type hint tag

2017-03-11 Thread Aleksander Morgado
The telit plugin is based on two main ways of checking the purpose of each port: udev tags flagging specific interfaces (with info taken from Windows .inf drivers), or otherwise using AT#PORTCFG? to query the modem about that information. If none of those applies, the port is ignored by default.