Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] How is the RM9200 status of buildroot ?
Date: Wed, 9 Jan 2008 00:00:02 +0100	[thread overview]
Message-ID: <01ce01c8524a$65be7fa0$080514ac@atmel.com> (raw)
In-Reply-To: 05f701c85243$52e4c530$6e00a8c0@JONATHAN


> Hi all,
> 
> 
> 
> I juste started my new custom board and the cpu seem to work. I would like
> to start building my root file system and my file system. I would like to
> know if the buildroot for the RM9200 is working or I have to use something
> else ?
> 
> 
> 
> Regards
> 
> 
> 
> Jonathan
> 

Since I introduced the AT91RM9200 support I should answer.

The goal of the AT91RM9200 buildroot was to get 
AT45DB642 dataflash supported properly.

If your board is using a parallel flash, there will be some limitations.
Default configurations for linux won't work (but you can easily create your own)
The U-Boot version has never been tested with recent parallel flash.
There is no at91bootstrap/dataflashboot, so you have to rely
on U-Boot to copy itself to SDRAM, not hard but not tested.

Buildroot contains applications which run and others which doesn't,
so you have to figure out why.
Some applications will run using the uclibc toolchain built by buildroot,
and others will only run if you use an external glibc based toolchain.

To get a basic system running is very easy, compared to other build systems I tested.

Twas some time since I loaded the AT91RM9200 on a target, since
I mostly spend time on the AT91SAM926x nowadays,
but if you find a problem, they can usually be fixed quite fast.


Best Regards
Ulf Samuelsson

  reply	other threads:[~2008-01-08 23:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 22:10 [Buildroot] How is the RM9200 status of buildroot ? Jonathan Dumaresq
2008-01-08 23:00 ` Ulf Samuelsson [this message]
2008-01-09  7:35   ` Joe
2008-01-09  7:59     ` Ulf Samuelsson
2008-01-09  8:29       ` Joe
2008-01-09 15:44   ` Jonathan Dumaresq
2008-01-09 17:02     ` Joe
     [not found]   ` <000001c852cc$8bd69100$6e00a8c0@JONATHAN>
2008-01-09 18:26     ` Ulf Samuelsson
2008-01-09 19:51       ` Jonathan Dumaresq
     [not found]         ` <027601c8531e$73c08420$6103170a@atmel.com>
2008-01-10 14:57           ` Jonathan Dumaresq
2008-01-12 13:28             ` Jorge S.
2008-01-12 16:19               ` Ulf Samuelsson
2008-01-14 16:50                 ` Jorge S.
2008-01-14 19:49                   ` Ulf Samuelsson
2008-01-13 12:43               ` Thomas Lundquist

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='01ce01c8524a$65be7fa0$080514ac@atmel.com' \
    --to=ulf@atmel.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