From: Joe <zentrale.at.work@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How is the RM9200 status of buildroot ?
Date: Wed, 09 Jan 2008 08:35:15 +0100 [thread overview]
Message-ID: <47847933.2010902@gmail.com> (raw)
In-Reply-To: <01ce01c8524a$65be7fa0$080514ac@atmel.com>
We're using a custom RM9200 board (parallel flash) also with buildroot,
and i would like to specify some of the "limitations" Ulf mentioned if
on parallel flash:
- Kernel won't work created by buildroot. We've moved to build one using
the buildroot toolchain, sources are vanilla + the victor patches + some
small fixes concerning the PHY
- U-Boot is the same, but for you are on a custom board, you'll always
have to "tune" the bootloader, i think.
- I would suggest to stick with the OABI. We've given EABI more than
just a try and kept running into a whole lotta trouble.
- Most "standard apps" will work: bash, busybox, gcc - for evereything
else, we compile in-target here.
Hope that helps a little, Joe
--
Sepp "ZaP" Holzmayr
please reply to:
zentrale.at.work at gmail.com
watch out for:
www.rocksociety.de
next prev parent reply other threads:[~2008-01-09 7:35 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
2008-01-09 7:35 ` Joe [this message]
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=47847933.2010902@gmail.com \
--to=zentrale.at.work@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