-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Am Sonntag 27 Juli 2008 13:46:09 schrieb Andy Green: |> and |> then if it's different from ours, there's likely something we should |> steal from it, or it from us. | | This is the current diff:
Thanks for the diff. | -# CONFIG_IKCONFIG is not set | +CONFIG_IKCONFIG=y | +CONFIG_IKCONFIG_PROC=y We should do that as well. | +CONFIG_YAFFS_FS=y | +CONFIG_YAFFS_YAFFS1=y | +CONFIG_YAFFS_9BYTE_TAGS=y | +CONFIG_YAFFS_YAFFS2=y | +CONFIG_YAFFS_AUTO_YAFFS2=y | +# CONFIG_YAFFS_DISABLE_LAZY_LOAD is not set | +CONFIG_YAFFS_CHECKPOINT_RESERVED_BLOCKS=10 | +# CONFIG_YAFFS_DISABLE_WIDE_TNODES is not set | +# CONFIG_YAFFS_ALWAYS_CHECK_CHUNK_ERASED is not set | +CONFIG_YAFFS_SHORT_NAMES_IN_RAM=y I'm going to pass on YAFFS, I looked at it briefly some months ago when we removed it. It just added to our patch load and we don't use it on GTA* so far, and look to be headed in a direction away from it. Otherwise it's neutral. | +CONFIG_SQUASHFS=m We should have that, look useful. |> I worry about it because the various things tied to races causing |> migraines are all exquisitely sensitive to config. | | Right. I hope that enabling some additional features do not harm wrt. | suspend/resume though. I think you're right with these, esp if nobody used YAFFS for example. I'll ste- uh - take a lead from those other two ideas though as soon as I cleared the current towering inferno of patches. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiMakAACgkQOjLpvpq7dMqIyACdE1j0C/gCsgq+iCw7kus+Qjpv Q6IAn0txFyQBBKbBRP41JwQT0uuHWY70 =TacY -----END PGP SIGNATURE-----
