From: rhabarber1848 <rhabarber1848@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Support dbox in mainline, was: Re: [STATUS] v2009.11-rc1 is out
Date: Tue, 3 Nov 2009 11:03:19 +0000 (UTC) [thread overview]
Message-ID: <hcp2ln$4tg$1@ger.gmane.org> (raw)
In-Reply-To: m2r5sfzxzn.fsf@ohwell.denx.de
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
next prev parent reply other threads:[~2009-11-03 11:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 13:42 [U-Boot] [STATUS] v2009.11-rc1 is out Wolfgang Denk
2009-10-28 14:53 ` Paulraj, Sandeep
2009-10-28 15:58 ` Wolfgang Denk
2009-10-28 16:13 ` Paulraj, Sandeep
2009-10-31 17:57 ` Tom
2009-11-11 12:36 ` Albin Tonnerre
2009-11-03 8:04 ` rhabarber1848
2009-11-03 9:37 ` Detlev Zundel
2009-11-03 10:17 ` rhabarber1848
2009-11-03 10:47 ` Detlev Zundel
2009-11-03 11:03 ` rhabarber1848 [this message]
2009-11-03 10:41 ` rhabarber1848
2009-11-03 13:10 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hcp2ln$4tg$1@ger.gmane.org' \
--to=rhabarber1848@web.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox