Am Tue, 03 Nov 2009 11:47:08 +0100 schrieb Detlev Zundel:
After unpacking U-Boot 2009.08 these files are copied into the source tree: http://cvs.tuxbox.org/tuxbox/boot/u-boot-tuxbox/
Ah uh, I would even offer some help in the process (like adding a branch in the u-boot-testing repository), but this instruction is somewhat unspecific, i.e. I see three boards being supported. If we want to get the support mainline, we should start with only one of them - including only the neccessary changes, i.e. cpu/ppc4xx/serial_sicc.c is very likely not relevant for the dbox :)
the Dreambox files are not used atm, they were added 5 years ago, I never cared about them.
The IPBox stuff is used with U-Boot 1.2.0, I do not have plans to upgrade to a more recent U-Boot version because I do not have the hardware for testing.
So only the Dbox is left, and yes, merging it will be fun;)
Our code includes functions to read files (config, logos) from a JFFS2 partition, display LCD and framebuffer logos during boot, some unfinished support for booting from HDD and loading kernels from Squashfs partitions.
The Squashfs code is based on Squashfs 3.0, it can not be upgrade to 3.3 or 4.x because we use Linux 2.4.37.6, where Squashfs > 3.0 is not available.
Squashfs support in U-Boot also includes optional LZMA support, but not the LZMA 4.65-based code from U-Boot, but LZMA 4.40 included in fs/ squashfs/. It is therefore not possible to link both LZMA libs into U- Boot at compile time. This is not needed for us because the root filesystem is either Squashfs/LZMA-4.40 or JFFS2/LZMA-4.65.
As hinted before, I do not have much C skills to do necessary cleanups nor do I want to be mentioned as official maintainer ;)
But the code is in use for many years by lots of users so technically there should not be many problems.
Cheers, rhabarber1848