linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: John Rigby <jcrigby@gmail.com>
To: Kenneth Johansson <kenneth@southpole.se>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: fastboot.
Date: Fri, 29 May 2009 14:45:44 -0600	[thread overview]
Message-ID: <4b73d43f0905291345p5a87f763m4a080a662feed214@mail.gmail.com> (raw)
In-Reply-To: <4b73d43f0905291330i67c20bd3y2fa3f1a127077b74@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2551 bytes --]

One more thing.  You can get another speed up if you can do burst reads from
NOR.  This requires using the fifo in the local bus controller.  On the
ADS5121 board you need a cpld change to increment the address lines.  With
the cpld as shipped you end up reading bursts that have the first 4 bytes
repeated because the address lines do not increment.  I don't know if this
is feature or bug with the 5121 but I do know you can work around it in the
cpld.

With burst access working you should be able to speed up the kernel copy and
also the jffs2 mount and filesystem access.

I also found that coping an uncompressed kernel was faster than
decompressing a compressed kernel.  But your mileage may vary if you have
the data cache on.  I found that working around all the problems with
turning data cache on were going to take more time than I had.

John

On Fri, May 29, 2009 at 2:30 PM, John Rigby <jcrigby@gmail.com> wrote:

> Kenneth,
>
> I did some fastboot work for 5121 a few months ago.  U-boot, kernel and
> JFFS2 rootfs in NOR.  My reset to userland time was 2.0 seconds, where
> userland was first command executed in first rc.whatever file, so it
> included the time for /sbin/init to get up and start running the rc scripts.
>
> I did some profiling and noticed that the JFFS2 boot time was a significant
> hunk (not just the first time but everytime).  I ran sumtool on the JFFS2
> image and it dropped 600 ms from the boot time so my final time was 1.4
> seconds.  The sumtool program has been around for a few years but it was
> news to mean when I found it.
>
> John
>
>
> On Fri, May 29, 2009 at 5:13 AM, Kenneth Johansson <kenneth@southpole.se>wrote:
>
>> http://www.cambridgewireless.co.uk/news/article/default.aspx?objid=36792
>>
>> Anybody know what they mean by booting here.
>>
>> I have started the ads5121 board using u-boot and kernel in NOR flash
>> and root file system on a compact flash card connected to the IDE
>> interface in 2.05 second until init is started from the rootfs.
>>
>> This was fast enough for what was needed I did not try to optimize
>> further but since I already was in the domain where changes impacted
>> only a few milliseconds I have a hard time imagining going down to less
>> than a second.
>>
>> So I guess the only way is to skip u-boot and run linux kernel directly
>> out of NOR. Anyone know what MontaVista is doing ??
>>
>> _______________________________________________
>> Linuxppc-dev mailing list
>> Linuxppc-dev@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>>
>
>

[-- Attachment #2: Type: text/html, Size: 3462 bytes --]

      reply	other threads:[~2009-05-29 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 11:13 fastboot Kenneth Johansson
2009-05-29 20:30 ` fastboot John Rigby
2009-05-29 20:45   ` John Rigby [this message]

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=4b73d43f0905291345p5a87f763m4a080a662feed214@mail.gmail.com \
    --to=jcrigby@gmail.com \
    --cc=kenneth@southpole.se \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).