---
Makefile.am |3 +
examples/provision.c | 198 ++
2 files changed, 201 insertions(+), 0 deletions(-)
create mode 100644 examples/provision.c
diff --git a/Makefile.am b/Makefile.am
index 0f330a7..d57509d 100644
--- a/Makefile.am
+++
Hi Jukka,
> Makefile.am |3 +
> examples/provision.c | 198
> ++
> 2 files changed, 201 insertions(+), 0 deletions(-)
> create mode 100644 examples/provision.c
>
> diff --git a/Makefile.am b/Makefile.am
> index 0f330a7..d57509d 1006
Hello
On Tue, 2011-01-11 at 22:48 -0800, ext Marcel Holtmann wrote:
> > + if (sim != NULL) {
> > + ofono_sim_read(sim, SIM_EFSPN_FILEID,
> > + OFONO_SIM_FILE_STRUCTURE_TRANSPARENT,
> > + sim_spn_read_cb, req);
> > + return;
Hi Jukka,
On 01/12/2011 01:41 AM, Jukka Saunamaki wrote:
> Hello
>
> On Tue, 2011-01-11 at 22:48 -0800, ext Marcel Holtmann wrote:
>>> + if (sim != NULL) {
>>> + ofono_sim_read(sim, SIM_EFSPN_FILEID,
>>> + OFONO_SIM_FILE_STRUCTURE_TRANSPARENT,
>>> +
Hello
On Wed, 2011-01-12 at 10:46 -0600, Denis Kenzior wrote:
> > ...SIM EF-SPN...
>
> You're correct that netreg is the only consumer. There was no need for
> anyone else to see this information. However, this begs the question,
> why do you need the SPN data?
Some virtual operators are usin
Hi Jukka,
On 01/13/2011 12:36 AM, Jukka Saunamaki wrote:
> Hello
>
> On Wed, 2011-01-12 at 10:46 -0600, Denis Kenzior wrote:
>>> ...SIM EF-SPN...
>>
>> You're correct that netreg is the only consumer. There was no need for
>> anyone else to see this information. However, this begs the question
Hello Denis,
On Thu, 2011-01-13 at 09:57 -0600, Denis Kenzior wrote:
> > Some virtual operators are using the same MCC/MNC as their host, or some
> > operators have several different trade names, and these can have
> > different access settings (at least different UI visible name).
> > SPN in SIM
On Friday 14 January 2011 08:53:03 ext Jukka Saunamaki, you wrote:
> Alternative is of cause to make provisioning synchronous, but that would
> limit what plugin can do (like asking SPN with ofono_sim_read())
Just because the plugin would be synchronous won't magically fix the "physical"
race con
Hi Jukka,
> > > Some virtual operators are using the same MCC/MNC as their host, or some
> > > operators have several different trade names, and these can have
> > > different access settings (at least different UI visible name).
> > > SPN in SIM typically tells these cases apart. This is why I i
Hi ,
> > I was not sure if all MVNOs have their own MNC, but in any case some
> > operators use different trade names. Off the top of my hat I know our
> > local Finnish operators Elisa and Sonera use trade names like Kolumbus
> > and TeleFinland, and their name shown in UI needs to be correct.
>
Hi Jukka,
> > > I was not sure if all MVNOs have their own MNC, but in any case some
> > > operators use different trade names. Off the top of my hat I know our
> > > local Finnish operators Elisa and Sonera use trade names like Kolumbus
> > > and TeleFinland, and their name shown in UI needs to b
Hi
On Fri, 2011-01-14 at 14:44 +0100, ext Marcel Holtmann wrote:
> Hi Jukka,
>
> > > > I was not sure if all MVNOs have their own MNC, but in any case some
> > > > operators use different trade names. Off the top of my hat I know our
> > > > local Finnish operators Elisa and Sonera use trade name
Hi Jukka,
> > > > > I was not sure if all MVNOs have their own MNC, but in any case some
> > > > > operators use different trade names. Off the top of my hat I know our
> > > > > local Finnish operators Elisa and Sonera use trade names like Kolumbus
> > > > > and TeleFinland, and their name shown
On Friday 14 January 2011 16:10:27 ext Marcel Holtmann, you wrote:
> > Yes, that is how our previous UIs have done it, and I guess our UX
> > designers like it in the future too.
>
> I would advise the UI against using the name from the context
> information and better using the one from the netwo
Hi Jukka,
On 01/14/2011 12:53 AM, Jukka Saunamaki wrote:
> Hello Denis,
>
> On Thu, 2011-01-13 at 09:57 -0600, Denis Kenzior wrote:
>>> Some virtual operators are using the same MCC/MNC as their host, or some
>>> operators have several different trade names, and these can have
>>> different acces
Hi Remi,
> > > Yes, that is how our previous UIs have done it, and I guess our UX
> > > designers like it in the future too.
> >
> > I would advise the UI against using the name from the context
> > information and better using the one from the network registration
> > instead.
>
> Well that wou
Hello
On Sat, 2011-01-15 at 02:30 +0100, Marcel Holtmann wrote:
> > > I would advise the UI against using the name from the context
> > > information and better using the one from the network registration
> > > instead.
> >
> > Well that would make sense... Therefore the operators don't do it ;-)
17 matches
Mail list logo
