Re: Fwd: Cinterion plugin patch

On Wed, Nov 30, 2016 at 10:16:42AM +0100, Aleksander Morgado wrote: > On Mon, Nov 28, 2016 at 10:41 PM, Reinhard Speyerer wrote: > > using CID 1 when this CID could be used for RAT LTE when used with > > AT!SCACT or AT^SWWAN may generally be problematic for the following > >

Re: Fwd: Cinterion plugin patch

On Mon, Nov 28, 2016 at 10:41 PM, Reinhard Speyerer wrote: > using CID 1 when this CID could be used for RAT LTE when used with > AT!SCACT or AT^SWWAN may generally be problematic for the following > reason: when the mobile is registering to LTE CID 1 is used by most > mobiles to

Re: Fwd: Cinterion plugin patch

Hi Reinhard > Can we please get back QMI as an alternative to AT^SWWAN & CDC ECM for the > next PLS8 firmware update FYI we told Gelmalto that, for us, moving away from QMI seemed like a step in the wrong direction. It seems like they want to support building modules with chipsets from other

Re: Fwd: Cinterion plugin patch

On Mon, Nov 28, 2016 at 08:23:23PM +0100, Aleksander Morgado wrote: > On Mon, Nov 28, 2016 at 7:03 PM, matthew stanger wrote: > >> Ah, yeah. If the plugin does its own logic to select which CID to use, > >> it should not rely on the parent's connection status check. In our >

Re: Fwd: Cinterion plugin patch

> > Ah, yeah. If the plugin does its own logic to select which CID to use, > it should not rely on the parent's connection status check. In our > case, though, I think we should default back to letting the generic > logic decide the CID to use (i.e. don't fix to use the CIDs 1 and 3). > If we do

Re: Fwd: Cinterion plugin patch

On Sun, Nov 27, 2016 at 4:27 AM, matthew stanger wrote: > Sorry I sent that last email a little prematurely, was still targeting my > email client and ctrl-entered for another window. You can disregard that > second comment, I see what you did for IP config. Last little

Re: Fwd: Cinterion plugin patch

Sorry I sent that last email a little prematurely, was still targeting my email client and ctrl-entered for another window. You can disregard that second comment, I see what you did for IP config. Last little things: /* Get a tet port to setup the connection on */ > > > net* There is also

Re: Fwd: Cinterion plugin patch

Code looks awesome (*¬*), so much to learn for me. A few comments which are all trivial and really don't need to be included but in attempt to be as detailed as you > > > * The PDP context mapping is as suggested by Cinterion, although it looks > like > * this isn't strictly enforced by the

Re: Fwd: Cinterion plugin patch

On Fri, 25 Nov 2016 21:16:55 +0100 Reinhard Speyerer wrote: > On Fri, Nov 25, 2016 at 10:13:08AM +0100, Aleksander Morgado wrote: > > Hey Reinhard & Matthew, > > > > On Thu, Nov 24, 2016 at 10:34 PM, Reinhard Speyerer wrote: > > [...] > > > PLS8-E REVISION

Re: Fwd: Cinterion plugin patch

On Fri, Nov 25, 2016 at 09:55:41AM +, Andrew Bird wrote: > On Fri, 25 Nov 2016 10:13:08 +0100 > Aleksander Morgado wrote: > > > Hey Reinhard & Matthew, > > > > > > One further difference I noticed is that USSD responses for AT+CSCS="GSM" > > > contain a

Re: Fwd: Cinterion plugin patch

> > Ah, understood. I probably have at home the 01.x version which is the > one I tested QMI with. Are there steps somewhere on how to upgrade a > PLS8 to a newer firmware? Yes the 1.x vs. 2.x & 3.x are very different and further it seems Cinterion is going to drop QMI from all their new modems

Re: Fwd: Cinterion plugin patch

On Fri, 25 Nov 2016 10:13:08 +0100 Aleksander Morgado wrote: > Hey Reinhard & Matthew, > > One further difference I noticed is that USSD responses for AT+CSCS="GSM" > > contain a non-standard \xx escaping for non-printable characters (unless > > I missed some recent

Re: Fwd: Cinterion plugin patch

On Thu, Nov 24, 2016 at 11:58:28AM +0100, Aleksander Morgado wrote: > [...] > BTW; I'm worried that we're binding the logic too much to a specific > device with 2 interfaces; I've seen some online AT command reference > that doesn't even talk about the third parameter to specify interface > index

Re: Fwd: Cinterion plugin patch

On Thu, Nov 24, 2016 at 6:04 PM, matthew stanger wrote: > Uggg I am very sorry but that patch is not the right patch. It has none of > the fixes I worked on :(. Very sorry and terribly embarrassed. As soon as I > get back to my home computer I will mail out the correct one.

Re: Fwd: Cinterion plugin patch

Uggg I am very sorry but that patch is not the right patch. It has none of the fixes I worked on :(. Very sorry and terribly embarrassed. As soon as I get back to my home computer I will mail out the correct one. I'd avoid doing any work on this one for the next 24h. On Thu, Nov 24, 2016 at 8:54

Re: Fwd: Cinterion plugin patch

Alexsander, I'm traveling right now will test as soon as I get back tomorrow. On Nov 24, 2016 2:58 AM, "Aleksander Morgado" wrote: > Hey Matthew, > > On Wed, Nov 23, 2016 at 10:28 PM, Aleksander Morgado > wrote: > > Great work! it looks

Re: Fwd: Cinterion plugin patch

Hey Matthew, On Wed, Nov 23, 2016 at 10:28 PM, Aleksander Morgado wrote: > Great work! it looks really good now, although there are some small > things that could still be fixed. Let me prepare a branch with your > patch and I'll include some additional patches for you

Re: Fwd: Cinterion plugin patch

On Sun, Nov 20, 2016 at 7:26 PM, matthew stanger wrote: > Ok, so clearly I'm not as fast as I wish, but another patch never the less. > This should be pretty close but I'll keep at it if there are any changes > still needed so let me know :). Here are the changes since the

Re: Fwd: Cinterion plugin patch

Ok, so clearly I'm not as fast as I wish, but another patch never the less. This should be pretty close but I'll keep at it if there are any changes still needed so let me know :). Here are the changes since the first patch of this chain: Converted Enum types from all caps to camel case. Changed

Re: Fwd: Cinterion plugin patch

Hey! This looks much much better :) See comments next, in no particular order. On Mon, Oct 24, 2016 at 7:13 AM, matthew stanger wrote: > Here is finally the update... to the above code reviewed patch. A big thank > you Dan and Aleksander for the detail in the review it was