From: Konstantin Kletschke <lists@ku-gbr.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] decrease boot time
Date: Fri, 11 Feb 2005 23:30:35 +0100 [thread overview]
Message-ID: <20050211223035.GA10412@ku-gbr.de> (raw)
Hi Folks!
I am trying to improve boot time of my linux system on my motorola i.MX
system as much as possible. Therefore I tried to omit the copying and
decompressing the linux kernel image ba using XIP, but the code runs
slower in the (slower) flash and boot time increased.
I wonder how to make use of sync burst mode with u-boot in conjunction
eith linux. Today I switched on CFG_CMD_CACHE (I use u-boot-1.1.1) but I
wonder if u-boot knows that it should cache the area above 0x10000000.
Hm... I think the way the linux kernel starts itself is not making use
of any implementation of burst mode of the flash device. It copies a
small amount of bytes and decompresses them.
Could it be possible to make use of burst mode by copying the compressed
image into RAM by u-boot (i.e. bursting) and start the kernel in RAM
then? The decompressing and copying would be faster then...
How do I disable serial support in u-boot? My u-boot is currently 60k
big, in my opinion a simple bootloader which does something like
memsetup and starting kernel afterwards should not be much bigger than
10k. Or is that wrong?
I tried to disable serial support but several functions in common/
(serial_get* for example) are calling functions in
cpu/arm920t/imx_serial.c. Do I have to "#ifdef" any occurences of these
functions?
REgards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next reply other threads:[~2005-02-11 22:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 22:30 Konstantin Kletschke [this message]
2005-02-11 23:28 ` [U-Boot-Users] decrease boot time Grant Likely
[not found] ` <20050212200503.GA11316@ku-gbr.de>
2005-02-12 21:02 ` Grant Likely
2005-02-12 22:30 ` Wolfgang Denk
2005-02-13 13:14 ` Konstantin Kletschke
2005-02-15 14:50 ` Konstantin Kletschke
2005-02-13 13:02 ` Konstantin Kletschke
2005-02-14 8:36 ` Grant Likely
2005-02-12 0:34 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-02-12 22:52 Wolfgang Denk
2005-02-13 13:33 ` Konstantin Kletschke
2005-02-14 12:26 ` Konstantin Kletschke
2005-02-14 13:41 ` Konstantin Kletschke
2005-02-14 19:44 ` Wolfgang Denk
[not found] <20050212200931.GB11316@ku-gbr.de>
[not found] ` <20050212223043.98E11C1430@atlas.denx.de>
2005-02-13 13:31 ` Konstantin Kletschke
2005-02-13 15:17 ` Wolfgang Denk
2005-02-13 13:38 ` Konstantin Kletschke
2005-02-13 15:20 ` Wolfgang Denk
2005-02-14 12:11 ` Konstantin Kletschke
2005-02-14 12:26 ` 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=20050211223035.GA10412@ku-gbr.de \
--to=lists@ku-gbr.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