Differences

This shows you the differences between two versions of the page.

--- doc:appunti:hardware:freerunner_debian [2011/11/01 08:47] – [Idle notification: timeouts and signals] niccolo
+++ doc:appunti:hardware:freerunner_debian [2011/11/01 16:23] (current) – [GSM/GPRS] niccolo
@@ Line 230: / Line 230: @@
   - The GSM modem gets powered-on with ''RequestResource''.
-  - APN, login and password are entered.
   - Register on the GSM network.
+  - APN, login and password are entered.
   - Check PDP status and start the connection.
@@ Line 245: / Line 245: @@
 ("active",{})
 MDBUS2> org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.PDP.DeactivateContext
+MDBUS2> org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device  org.freesmartphone.GSM.Network.Unregister
 </code>
@@ Line 487: / Line 488: @@
 ==== WiFi broken in openmoko-panel-plugin ====
-The **fso-deviced-openmoko** should be patched because the sysfs path to control the WiFi power changed in kernel 2.6.34. See **[[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647003|Debian bug #647003]]**.
+The **fso-deviced-openmoko** before 0.9.5+git20110805-2 has a bug (the WiFi power sysfs path changed in kernel 2.6.34), see **[[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647003|Debian bug #647003]]**.
 Also **''openmoko-panel-plugin''** must be patched to use the new FSO DBus interface. I will release that patched version soon.
@@ Line 667: / Line 668: @@
 Idle status is one of the following: **''busy''**, **''idle''**, **''idle_dim''**, **''idle_prelock''**, **''lock''** and **''suspend''**. To prevent the device entering a state, set its timeout to **''-1''** (see the note below). If a state is disabled, the subsequent states are never reached.
-**NOTE**: to set a timeout of **''-1''** you cannot use the command line because **''-1''** is interpreted as an option. We can use the interactive mode of ''mdbus2'':
+**NOTE**: to set a timeout of **''-1''** you cannot use the command line because **''-1''** is interpreted as an option. We can use the interactive mode of ''mdbus2'' (terminate with Ctrl-D):
 <code>