Hi Aki, > 2010/3/30 Denis Kenzior <denk...@gmail.com>: > > The answer is that exposing this as a property is not going to happen > > because it is fundamentally wrong. And in effect it already is exposed, > > e.g. the fact that modem object is present in oFono. You have several > > options here: > > So I think what you are saying is that if a modem object exists, it is > available. That is, the HW has been powered up and initialized > properly. And that the Powered property is about whether or not the > modem's cellular is active (RF on/off).
Powered is about whether the modem is useable. Today we don't make a distinction between tx/rx off with sim, tx/rx off without sim, or fully active. We need to look closely at whether enabling flight mode (e.g. SIM on, while TX/RX is off) makes sense. It is something we should consider, but challenging since most of the SIM attributes are exposed through atoms which won't be generally available when in Flight mode (e.g. SMSC address on SIM atom, MBDN on message waiting, etc) > > If this is the case, then I think it'll do. > > There is a corner case when the modem is borked and cannot be properly > powered but needs to be taken to a care point (not that that ever > happens IRL ;), and I would rather see this indicated explicitly > rather than implicitly by ModemManager returning an empty list of > modems. So finally someone tells me an actual use case, how hard was that? :) It is still possible to expose this information on the interface provided by your custom plugin, I'm against exposing this as a property on Modem interface. Regards, -Denis _______________________________________________ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
