Re: [PATCH 1/2] modem-helpers: if operator not in UCS2, see if already valid UTF-8

2017-04-15 Thread Colin Helliwell
> On 14 April 2017 at 23:15 Aleksander Morgado wrote: > > On Fri, Apr 14, 2017 at 4:57 PM, Colin Helliwell > > wrote: > > > Might have hung this off the wrong thread, but it's along the same lines. > > I've just noticed that whilst

Re: [PATCH 1/2] modem-helpers: if operator not in UCS2, see if already valid UTF-8

2017-04-14 Thread Colin Helliwell
Might have hung this off the wrong thread, but it's along the same lines. I've just noticed that whilst the mmcli status now decodes the operator, the --sim status doesn't: # mmcli -m 0 ... 3GPP | imei: '358606050452806' | enabled locks: 'none' |

Re: [PATCH 1/2] modem-helpers: if operator not in UCS2, see if already valid UTF-8

2017-04-02 Thread Aleksander Morgado
On 01/04/17 06:01, Dan Williams wrote: > On Sat, 2017-03-25 at 21:39 +0100, Aleksander Morgado wrote: >> The method doing the operator name normalization takes as input the >> current configured modem charset. If this is UCS2, we will now just >> assume this is a hint: the string may or may not

Re: [PATCH 1/2] modem-helpers: if operator not in UCS2, see if already valid UTF-8

2017-03-31 Thread Dan Williams
On Sat, 2017-03-25 at 21:39 +0100, Aleksander Morgado wrote: > The method doing the operator name normalization takes as input the > current configured modem charset. If this is UCS2, we will now just > assume this is a hint: the string may or may not come in hex/UCS2. > > This logic makes the

[PATCH 1/2] modem-helpers: if operator not in UCS2, see if already valid UTF-8

2017-03-25 Thread Aleksander Morgado
The method doing the operator name normalization takes as input the current configured modem charset. If this is UCS2, we will now just assume this is a hint: the string may or may not come in hex/UCS2. This logic makes the custom operator name loading in Huawei unneeded, if the modem is