diff options
| author | Aleksander Morgado <aleksander@lanedo.com> | 2013-10-08 10:15:57 +0200 |
|---|---|---|
| committer | Aleksander Morgado <aleksander@lanedo.com> | 2013-10-08 10:15:57 +0200 |
| commit | 564b3610fd6e4060bc36c2cf568b2305aaf6ea19 (patch) | |
| tree | 09ab6d9079abcb37c563dc0c25c1042c6302bae7 | |
| parent | a006761c7159594c6c3fade53eb2326393510a2a (diff) | |
TODO: remove already implemented or no longer applicable items
| -rw-r--r-- | TODO | 45 |
1 files changed, 0 insertions, 45 deletions
@@ -1,46 +1,4 @@ - --------------------------------------------------------------------------------- - * Documentation: libmm-glib - -libmm-glib should have its own gtk-doc based documentation setup in -docs/reference. This task involves setting up the gtk-doc build under docs/, -as well as including all missing gtk-doc comments in the sources. - - --------------------------------------------------------------------------------- - * Documentation: libmm-common - -libmm-common is the common library used both by libmm-glib and the ModemManager -daemon. Some of its bits must be considered internal, like the server-side -specific code generated by gdbus-codegen; but lots of other bits are to be -considered public and therefore documented with gtk-doc. This task involves -setting up the gtk-doc build under docs/, as well as including all missing -gtk-doc comments in the sources. - - --------------------------------------------------------------------------------- - * Documentation: debugging tips - -Provide a section for debugging tips in the ModemManager documentation. - - --------------------------------------------------------------------------------- - * GObject introspection - -Either with libmm-common or libmm-glib, we should provide GObject Introspection -support for the libraries. libmm-glib is just a small layer on top of -libmm-common, so maybe the introspection can be done at libmm-common level -directly. - - --------------------------------------------------------------------------------- - * Firmware - -ModemManager should implement the Firmware interface if modems allow to change -firmware on-the-fly. - - -------------------------------------------------------------------------------- * Contacts @@ -144,8 +102,5 @@ example to update the signal quality value or check registration status. ** QMI: in NAS >= 1.8 we don't have the operator name given in the registration status queries, we'll need to get it with "NAS Get PLMN Name". - ** QMI: For the operator ID provisioned in the SIM, should we be using "Get - Home Network"? - ** QMI: mark the modem as invalid if we lose the QMI and/or WWAN ports. For example, we should handle 'sudo rmmod qmi_wwan && sudo modprobe qmi_wwan' |