public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] boot-up time optimization. Where to start?
Date: Tue, 03 May 2011 10:08:44 +0200	[thread overview]
Message-ID: <4DBFB80C.70101@denx.de> (raw)
In-Reply-To: <201105030848.17576.alexander.stein@systec-electronic.com>

On 05/03/2011 08:48 AM, Alexander Stein wrote:

Hi Alexander,

> Am Montag, 2. Mai 2011, 19:00:47 schrieb Wolfgang Denk:
>> In message <201105021640.27241.alexander.stein@systec-electronic.com> you 
> wrote:
>>> Ok, let me be more precise on this.
>>> We used U-Boot v2010.09 on a custom board running on an I.MX35 (ARM1136).

The i.MX35 is supported in u-boot mainline. As I can suppose, you start
from the mx35pdk to port your code, probably you have good chances to
use the last u-boot code. And then to send patches for your board,
too... ;-)

> 
>> 2. This is an ARM board.
>>
>> 3. This is an old version before cache support for ARM was added.
> 
> This specific version was selected due to relocation problems on ARM.

The mx35pdk board is supported in u-boot mainline using relocation.

> expect the dcache doesn't have that big influence on the named code part as 
> the environment is already in RAM.

Check in the mailing list, the numbers reported by people who measured
the influence of cache say there is a big difference, specially when big
chunks of code is copied, that is copying the kernel from storage before
booting.

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2011-05-03  8:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 13:39 [U-Boot] boot-up time optimization. Where to start? Simon Schwarz
2011-04-27 14:37 ` Tabi Timur-B04825
2011-04-27 15:10 ` Eric Cooper
2011-04-27 15:27 ` Mike Frysinger
2011-04-27 15:59 ` Alexander Stein
2011-04-27 16:37   ` Mike Frysinger
2011-04-27 19:08   ` Wolfgang Denk
     [not found]     ` <BANLkTimQzo7mMMb0DjqX0c78pcNHnDXPLg@mail.gmail.com>
2011-04-27 21:19       ` Wolfgang Denk
2011-04-28  8:12         ` Simon Schwarz
2011-05-02 14:40     ` Alexander Stein
2011-05-02 15:31       ` Detlev Zundel
2011-05-02 16:07         ` Alexander Stein
2011-05-02 16:19           ` Detlev Zundel
2011-05-02 17:02           ` Wolfgang Denk
2011-05-02 17:00       ` Wolfgang Denk
2011-05-03  6:48         ` Alexander Stein
2011-05-03  8:08           ` Stefano Babic [this message]
2011-05-05  5:32           ` Wolfgang Denk
2011-05-05  7:06             ` Alexander Stein
2011-05-05  7:27               ` Wolfgang Denk
2011-05-06  8:54               ` Stefano Babic
2011-05-05 18:10             ` Charles Manning
2011-05-05 20:18               ` Simon Glass
2011-05-09 10:49                 ` Detlev Zundel
2011-05-10  7:29                   ` Simon Schwarz
2011-05-11  5:12                   ` Simon Glass
2011-04-27 19:07 ` 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=4DBFB80C.70101@denx.de \
    --to=sbabic@denx.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