From: Shinya Kuribayashi <skuribay@pobox.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC 0/2] Add support for bootstrap stage and compressed U-Boot image
Date: Sat, 04 Dec 2010 11:32:14 +0900 [thread overview]
Message-ID: <4CF9A82E.8030005@pobox.com> (raw)
In-Reply-To: <201011301535.09312.luigi.mantellini@idf-hit.com>
Hi,
On 11/30/2010 11:35 PM, Luigi 'Comio' Mantellini wrote:
> Look the following benchmark (qemu-mips board):
>
> U-Boot Vanilla
> 179600 bytes u-boot.bin
>
> Bootstrap code w/o compresion (memcpy)
> 189224 bytes u-boot-bootstrap.bin
> --> size 105%
>
> Bootstrap code using BZIP2 compression
> 114388 bytes u-boot-bootstrap.bin
> -->size 64%
>
> Bootstrap code using GZIP compression
> 114204 bytes u-boot-bootstrap.bin
> -->size 64%
>
> Bootstrap code using LZMA compression
> 89456 bytes u-boot-bootstrap.bin
> -->size 50% <-- BEST
>
> Bootstrap code using LZO compression
> 104388 bytes u-boot-bootstrap.bin
> -->size 58%
Personally, I don't much care about the size of U-Boot bin itself
(179kB or 104kB), but it depends. And I'd like to see how much boot
time of U-Boot improved on your environment.
> >> The following patches introduce the bootstrap support that enable to have a
>> compressed U-Boot image. The bootstrap code supports the uncompressed as
>> well as compressed payloads, using LZMA, GZIP, BZIP2 and LZO.
>>
>> Actually I developed just the mips version (using qemu-mips board)...
>>
>> Please see the Patch #1 for the required defines to enable the required
>> features.
Not having a closer look at the patch yet, some general comments:
* Two patches posted, but contains multiple logical changes:
- CONFIG_BOOTSTRAP* build infrastructure (main body)
- common: Introduce console_bootstrap
- MIPS: Separate _machine_restart() and do_reset() into reset.c
- MIPS: config.mk: Append -g debug option to PLATFORM_CPPFLAGS,
which is already provided by $(TOPDIR)/config.mk.
- MIPS: qemu_mips: bootstrap support enablement (experimental)
Please break into logical changes, please.
* '_bootstrap' suffixed files are almost identical to the original
ones:
- arch/mips/cpu/reset{,_bootstrap}.c
- arch/mips/cpu/start{,_bootstrap}.S
- board/qemu-mips/u-boot{,_bootstrap}.lds
Is there any way not to duplicate them? Do we really need to have
_bootstrap files separated?
Once this bootstrap feature approved as general U-Boot feature, I'd
like to take MIPS-related changes.
Thanks,
Ralf
next prev parent reply other threads:[~2010-12-04 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 10:30 [U-Boot] [RFC 0/2] Add support for bootstrap stage and compressed U-Boot image luigi.mantellini at idf-hit.com
2010-11-30 10:30 ` [U-Boot] [RFC 1/2] Add support for bootstrap stage that allows to have a compressed U-Boot image. The final image will named "u-boot-bootstrap" luigi.mantellini at idf-hit.com
2010-12-04 3:05 ` Mike Frysinger
2010-11-30 10:30 ` [U-Boot] [RFC 2/2] Add support for bootstrap stage to QEMU-MIPS board luigi.mantellini at idf-hit.com
2010-11-30 14:35 ` [U-Boot] [RFC 0/2] Add support for bootstrap stage and compressed U-Boot image Luigi 'Comio' Mantellini
2010-12-04 2:32 ` Shinya Kuribayashi [this message]
2010-12-04 2:42 ` Shinya Kuribayashi
2010-12-04 11:12 ` Luigi Mantellini
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=4CF9A82E.8030005@pobox.com \
--to=skuribay@pobox.com \
--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