From: Aras Vaichas <arasv@magellan-technology.com>
To: linux-embedded@vger.kernel.org
Subject: AT91SAM9G20 design and boot times
Date: Thu, 11 Jun 2009 13:43:18 +1000 [thread overview]
Message-ID: <ed62800906102043m723911d8t1968174201ba7fbb@mail.gmail.com> (raw)
In-Reply-To: <ed62800906102037q71f2a6bdq835793a1ac36c41b@mail.gmail.com>
Hi,
we're designing our next generation RFID reader and I'm planning on
using the AT91SAM9G20 in the next design. We currently use the
AT91RM9200.
Can I get some feedback from people with regards to general design
configurations that affect the boot time with respect to this CPU (or
the AT91SAM9260)
Some questions are:
* what is your boot time? What is the time from power-on to kernel
running, how long does the kernel take to run until init starts, and
how long does init take?
* what is your system hardware configuration? CPU+NAND, CPU+NOR+NAND,
CPU+DATAFLASH+NAND?
* do you boot everything from the NAND or do you use a combination of
Dataflash/NOR and NAND?
* do you use U-Boot, or a minimal custom bootloader that copies a
kernel image from NAND to SDRAM and then executes it?
* do you mount a small partition of the NAND to begin with and then
mount the rest later?
* do you have a monolithic kernel, or is it split into minimal with
modules loaded from, say, JFFS2 on NAND?
* are you using JFFS2 or UBIFS?
Any info is much appreciated, thank you!
regards,
Aras Vaichas
next parent reply other threads:[~2009-06-11 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ed62800906102037q71f2a6bdq835793a1ac36c41b@mail.gmail.com>
2009-06-11 3:43 ` Aras Vaichas [this message]
2009-06-11 12:48 ` AT91SAM9G20 design and boot times Nicolas Ferre
2009-06-11 13:58 ` Robin Getz
2009-06-12 14:06 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-15 6:32 ` Marc Pignat
2009-06-12 18:37 ` AT91SAM9G20 design and power (was and boot times) Christian Gagneraud
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=ed62800906102043m723911d8t1968174201ba7fbb@mail.gmail.com \
--to=arasv@magellan-technology.com \
--cc=linux-embedded@vger.kernel.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).