Re: [RFC] Exposing profiles (provisioned contexts) in the API

2021-01-19 Thread Giacinto Cifelli
Hi Aleksander, On Tue, Jan 19, 2021 at 11:06 AM Aleksander Morgado wrote: > > Hey Giacinto, > > > > > for Cinterion modems that support the profiles, there is a special > > command to read them (ATI61, no mbim equivalent, maybe qmi but I > > wouldn't know it; and an at^scfg? option to read the

Re: [RFC] Exposing profiles (provisioned contexts) in the API

2021-01-19 Thread Aleksander Morgado
Hey Giacinto, > > for Cinterion modems that support the profiles, there is a special > command to read them (ATI61, no mbim equivalent, maybe qmi but I > wouldn't know it; and an at^scfg? option to read the current one) as a > list and would fit well with option 2. > The second option would also

Re: [RFC] Exposing profiles (provisioned contexts) in the API

2021-01-13 Thread Aleksander Morgado
Hey, > I picked the single property for the initial implementation so that MM > would notify consumers when the profiles list changed via OTA update. > If we are moving to a D-Bus method to list them instead, then we > should preserve this behavior somewhere else (i.e. a separate signal). >

[RFC] Exposing profiles (provisioned contexts) in the API

2021-01-12 Thread Aleksander Morgado
Hey all, Eric wrote an initial draft of the API to expose profiles (provisioned contexts) in DBus here: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/179 The initial implementation he wrote relies on a read-only "Profiles" property exposed in the 3GPP interface,