Disallowing draining until bricking

Andy Green andy at openmoko.com
Thu Jul 17 17:07:01 CEST 2008

Hash: SHA1

Somebody in the thread at some point said:

| (Is there a smiley symbol for biting one's tongue?)

- ---->  (8-Ep)~

| Is there anyway we can record a reason for the last shutdown?  Something
| we can set in the flash, that u-boot can fetch?  I'm just thinking about
| the somewhat-outstanding resume-fails-after-30-minutes-suspended
| problem, and how one might distinguish a purposeful power-off from a
| failure to resume.

Good point... normally, the userspace stuff will catch the battery
failure at a higher threshold than this "emergency shutdown" and the
shutdown will be controlled, we could write something to a NV log then.

What we can do with the emergency way is write something to some "user"
registers in pcf50633, that is held up even by the backup battery.  I'll
poke at it a bit.

GSM failure to resume is completely outstanding (and not in a good way)
as I can't make it happen with my normal setup.  I will come back to it
shortly using a normal rootfs and see what happens.  I didn't run out of
ideas to attack it as soon as I can reproduce it although they get
increasingly painful.

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the openmoko-kernel mailing list