[PATCH 0/3] Qi booting control from rootfs

Andy Green andy at openmoko.com
Mon Nov 24 09:49:49 CET 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:

| Actually the battery was 100% full ( double checked before and
| immediately after regaining access, so this is ruled out.

Oh well.

|     NOR boot can theoretically be affected by some things like
inherited PMU
|     state but in fact on GTA02 I use NOR U-Boot to update Qi during
|     development and there's no problems.  Besides there's nothing funny
|     about Qi PMU settings.
|
|  That's how I updated, too , so then I really wonder what had happened
| -  and how to get back in a sane state should this happen again!

The only paths into screwing up NOR boot I can imagine would be boot
itself getting trashed via PMU somehow or the GSTATUS2 / 3 being set
making it look like resume with bogus resume address.  But if it existed
I would expect to have seen that after some hundreds of
boot-NOR/flash-Qi/test/boot-NOR/flash-Qi cycles here, and NOR boot has
always been as reliable as my power arrangements.

So no doubt you experienced unhappy events but it's hard to see how Qi
is implicated... of course that's not much of an explanation either.

- -Andy

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

iEYEARECAAYFAkkqaq0ACgkQOjLpvpq7dMqhbwCfdHZRzt+dNJXZkh4zWUPLS9rq
N7oAn3FgtiDJ96IbvLfGukmaROyHfBP1
=7hNt
-----END PGP SIGNATURE-----



More information about the openmoko-kernel mailing list