Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Newbie: AT91SAM9260 NAND Boot
Date: Tue, 23 Feb 2010 23:51:25 +0100	[thread overview]
Message-ID: <87tyt7d0r6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <815f0bd71002221951v606dbdddn381587fdd662e485@mail.gmail.com> (Roo's message of "Tue, 23 Feb 2010 14:51:37 +1100")

>>>>> "Roo" == Roo  <roo.watt@gmail.com> writes:

Hi,

 Roo> I would like to use buildroot to build the rootfs, kernel and tools
 Roo> required for our application. I would appreciate any advice on where
 Roo> to start with this, is there any reason that a NAND boot defconfig
 Roo> does not exist currently? Will it be a difficult job to develop one? I
 Roo> know that there is a rootsf image and kernel image at at91.com but I
 Roo> see more value in supporting the latest buildroot particularly as I
 Roo> would like to integrate our own packages.

It shouldn't be much of a problem. Basically you just need to decide
what pakcages you want to include and then what kind of filesystem you
want to use on your NAND flash (E.G. jffs2), and then configure that.

 Roo> Also can anyone advise whether there are issues building on a
 Roo> 64bit host?  Any advice appreciated.

No, I only use 64bit machines.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2010-02-23 22:51 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
2010-02-23 23:15   ` Roo
2010-02-23 23:32     ` Grant Edwards
2010-02-23 22:51 ` Peter Korsgaard [this message]
  -- 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=87tyt7d0r6.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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