From: gluedig@gmail.com
To: ofono@ofono.org
Subject: Re: Telit LE910V1 - LTE only modem
Date: Mon, 20 Mar 2017 14:32:43 +0100 [thread overview]
Message-ID: <3cec3e92-bd40-b261-a593-57f98d54ed96@gmail.com> (raw)
In-Reply-To: <18b346e6-dee3-a7bd-058b-a4b9586a94d6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2606 bytes --]
On 03/20/2017 02:19 PM, Lukasz Nowak wrote:
> Hi Piotr, Denis,
>
> With the qmimodem patch I was able to bring the LE910-SVG modem on-line.
> But I had to do two things:
>
> 1. The gprs driver was never getting attached.
> a) This statement in src/gprs.c, gprs_netreg_update()
> if (ofono_netreg_get_technology(gprs->netreg) ==
> ACCESS_TECHNOLOGY_EUTRAN)
> /*
> * For LTE we set attached status only on successful
> * context activation.
> */
> return;
> means that the gprs->driver_attached is never set to true.
> If I remove this piece of code, the gprs->driver->set_attached() gets called, and that
> gets everything attached and working.
>
> b) I can see, that another path to it would be:
> qmimodem/gprs.c create_nas_cb() calls qmi_service_register(QMI_NAS_SS_INFO_IND, ss_info_notify)
> But then, ss_info_notify() is never called. I think that the modem is quick enough to register
> to the network before qmi_service_register(QMI_NAS_SS_INFO_IND) is called.
>
> c) Denis, you mentioned that I need to call ofono_gprs_cid_activated()
> Which piece of code should do that? qmimodem/network-registration.c or plugins/gobi.c?
>
>
> 2. qmimodem/network-registration.c:extract_ss_info() seems to be getting a corrupted
> operator name:
> plmn->desc_len = 3
> plmn->desc[] = { 0x56, 0xfd, 0x15 }
> The first byte seems correct ('V' for Verizon), but the other two are wrong (later on, dbus
> aborts the entire ofono process, saying this is not a valid utf-8 string).
> plmn->mcc and plmn->mnc are correct (311:480 - US:Verizon)
>
> Have you ever seen anything like that?
> If I replace the invalid characters, everything works ok. But I imagine this is not
> the right way to handle this.
>
Hi,
I have observed that as well for some networks/sims.
I assume this is due some idiosyncrasy of Telit's QMI implementation.
And since I was not able to obtain any help form Telit regarding QMI
(not even documentation) I accepted that and patched extract_ss_info to
rewrite plmm->desc as "mcc:mnc".
>
> Thanks for all your help with this.
>
> Lukasz
>
>
>
> On 16/03/17 09:32, Piotr Haber wrote:
>> Hi Lukasz,
>>
>> I have never useg LE910-SVG but I have used LE910-EUG which is also V1 LE910 modem.
>> It uses QMI interface and is End-of-life product according to Telit.
>> Below is a patch I used to add support for it, maybe it will help you.
>>
>> Modem is not recognized automatically, you need to point ofono to use correct driver
>> by setting ENV{OFONO_DRIVER}="le910" in udev.
>>
>>
>>
next prev parent reply other threads:[~2017-03-20 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 18:35 Telit LE910V1 - LTE only modem Lukasz Nowak
2017-03-16 9:32 ` Piotr Haber
2017-03-16 9:32 ` [PATCH] support Telit LE910 modem Piotr Haber
2017-03-16 12:57 ` Telit LE910V1 - LTE only modem Lukasz Nowak
2017-03-20 13:19 ` Lukasz Nowak
2017-03-20 13:32 ` gluedig [this message]
2017-03-20 14:39 ` Denis Kenzior
2017-03-20 16:46 ` Lukasz Nowak
2017-03-20 23:39 ` Denis Kenzior
2017-03-21 17:50 ` Lukasz Nowak
2017-03-21 18:57 ` Denis Kenzior
2017-03-22 18:23 ` Lukasz Nowak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3cec3e92-bd40-b261-a593-57f98d54ed96@gmail.com \
--to=gluedig@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox