The following series adds support for the LCD panel on the ATSTK1000. To use this, you must first apply both of the following series:
http://lists.denx.de/pipermail/u-boot/2008-September/039826.html http://lists.denx.de/pipermail/u-boot/2008-September/039833.html
I'm a bit unsure what to do about this. While I certainly want LCD support out of the box on all boards that support it, this patchset brings the U-Boot image size dangerously close to 128k, which is the space we currently have available with the current MTD partitioning layout hardcoded into the kernel. With NAND flash support added on top of this, the ATSTK1006 image ends up at almost 150k, and there are still other features I'd like to support in the future, e.g. libfdt, Hush parser, USB, etc.
So this means I can either merge this as-is but disabled by default (which is bad from a testing perspective), disable some other features, or change the partitioning. Doing the latter will also make it possible to introduce redundant environment, but it means current kernels will break.
Since the ATSTK1000 doesn't actually ship with a filesystem in flash by default, the breakage will probably be limited to a handful of customized boards, but people who have done this kind of customization probably won't like that the flash layout changes behind their back.
What do everyone think about this? Is redundant environment and a boatload of features worth breaking compatibility with current kernels?
Haavard
I would prefer more testing over user/developer compability.
But if you resize the partition for u-boot be sure to resize to 256k and not 192k, since this would cause a lot more problems than needed for us using flash chips with 128k block size. Not a big problem but an issue.
I would love to see USB support implemented.
Regards Eirik Aanonsen