From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Newbie: AT91SAM9260 NAND Boot
Date: Tue, 23 Feb 2010 15:40:52 +0000 (UTC) [thread overview]
Message-ID: <hm0su3$h9k$1@dough.gmane.org> (raw)
In-Reply-To: 815f0bd71002221951v606dbdddn381587fdd662e485@mail.gmail.com
On 2010-02-23, Roo <roo.watt@gmail.com> wrote:
> I am new to buildroot and have been given a AT91SAM9260 SOM to
> work with. The latest buildroot does not appear to include a
> defconfig for a NAND boot system.
Can you explain what a "NAND boot system" is?
When I boot an AT91SAM9xxx from NAND, I tell buildroot to build
a JFFS2 root image, a uImage kernel with MTD/JFFS2 support, put
the resulting kernel and root image into NAND, and configure U-Boot
to boot from NAND.
> I would like to use buildroot to build the rootfs, kernel and
> tools required for our application. I would appreciate any
> advice on where to start with this, is there any reason that a
> NAND boot defconfig does not exist currently?
Presumably because nobody has bothered to submit one.
> Will it be a difficult job to develop one?
I'm still not sure what you're after beyond selecting JFFS2 for
the root fs type and enabling MTD and JFFS2 support in the
kernel. Can you explain what it is you're missing?
--
Grant Edwards grante Yow! I just got my PRINCE
at bumper sticker ... But now
visi.com I can't remember WHO he
is ...
next prev parent reply other threads:[~2010-02-23 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 3:51 [Buildroot] Newbie: AT91SAM9260 NAND Boot Roo
2010-02-23 15:40 ` Grant Edwards [this message]
2010-02-23 23:15 ` Roo
2010-02-23 23:32 ` Grant Edwards
2010-02-23 22:51 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2010-02-23 21:22 Sagaert Johan
2010-02-23 23:30 ` Roo
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='hm0su3$h9k$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
/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