SD boot resume status

[Andy Green]

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

Hi folks -

Suspend / resume is working for SD Boot allowing for the current LCM
resume issues.

But even with the config option to allow "UNSAFE RESUME", on resume the
*logical* ext2 filesystem is corrupted from the Linux side, even when
mounted read-only.  (We get complaints about bad inode flags and so on
after resume which seem to come from -EIO from somewhere)  The *actual*
ext2 filesystem on the SD card partition is not corrupted at all, as we
would expect mounted ro.

Since we write nothing back to the card when mounted ro, and the MMC
stack resume and "UNSAFE" resume actions seem to complete correctly, I
dunno where that comes from.  I will printk() in the MMC stack to find
the source of the -EIO.

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

iD8DBQFHxrSAOjLpvpq7dMoRAiKcAJ97ghS5ITGsZhfjwmmrM4+4Po8UzwCfVKSd
oqAGqDP+fsWn3c+XQ0gWauo=
=Sdl7
-----END PGP SIGNATURE-----