Hi Jonas,
On 04/22/2019 12:33 PM, Jonas Bonn wrote:
Hi Denis,
On 22/04/2019 17:52, Denis Kenzior wrote:
What is actually different for uBlox that requires such a drastic
approach? Right now I'm seeing a duplication of CMER/CIEV and NITZ
logic. Not much else.
For the TOBY L4 I hit this:
ofono_error("This driver is not setup with Signal Strength reporting"
" via CIND indications, please write proper netreg"
" handling for this device");
This device requires _polling_ ECSQ to get this info (no async signal
strenght reporting). Other uBlox models don't have this issue.
You have to be kidding... Sigh.
So we need to have UBLOX_TOBY_L4, UBLOX_TOBY_L2, etc. "vendor" types to
differentiate not only the vendor but the model. Is that ok? Not
enough to warrant a custom driver?
We used to have UBLOX_L2 prior to
e70789534efc62d31112f54e42c0d249bed93b37. So I don't really mind. If
you can do the l_container_of polymorphism going nicely, that's fine
with me as well.
Is NITZ really a thing? I interpreted it as "No immediate timezone"...
NITZ stands for: Network Identity & Time Zone. And yes, it is a 'thing'
and part of the 3GPP standards for at least 15 years.
/Jonas
Regards,
-Denis
_______________________________________________
ofono mailing list
[email protected]
https://lists.ofono.org/mailman/listinfo/ofono
