From: Jonathan Dumaresq <jdumaresq@cimeq.qc.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Where to add/locate board support?
Date: Thu, 17 Jan 2008 09:56:44 -0500 [thread overview]
Message-ID: <01ab01c85919$2cdfd460$6e00a8c0@JONATHAN> (raw)
In-Reply-To: <478F6BA3.9000204@gmail.com>
A small info can help you to do it.
http://www.linux4sam.org/twiki/bin/view/Linux4SAM/BuildRoot
It's targeted for sam9 CPU, but the principle is the same. I'm in the same
boat of you. We have received our new custom board with the rm9200 and try
to get thing working in the right way.
Regards
Jonathan
-----Message d'origine-----
De?: buildroot-bounces at uclibc.org [mailto:buildroot-bounces at uclibc.org] De
la part de Joe
Envoy??: 17 janvier 2008 09:52
??: buildroot at uclibc.org
Objet?: [Buildroot] Where to add/locate board support?
Hi all!
Currently i'm in the task of adding support for our custom board to
buildroot, hence my question:
Where is the right place to add it? As we're using a RM9200 CPU, it
could be located below target/devices/Atmel, for the folders in
target/devices look to me more like CPUI vendors, not board vendors. Or
should it got to target/devices/our_company_name/our_board_name?
But that would seem pretty oversized to me, for we're on really low
production count, but i'd relly like to get things done right in the
buildroot-way...
Thanks, Joe
--
Sepp "ZaP" Holzmayr
please reply to:
zentrale.at.work at gmail.com
watch out for:
www.rocksociety.de
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2008-01-17 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 14:52 [Buildroot] Where to add/locate board support? Joe
2008-01-17 14:56 ` Jonathan Dumaresq [this message]
2008-01-17 15:59 ` Bernhard Fischer
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='01ab01c85919$2cdfd460$6e00a8c0@JONATHAN' \
--to=jdumaresq@cimeq.qc.ca \
--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