From: Ludovic Desroches <ludovic.desroches@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to add a board with Buildroot 2011.02
Date: Thu, 10 Mar 2011 15:48:40 +0100 [thread overview]
Message-ID: <4D78E4C8.2060009@atmel.com> (raw)
In-Reply-To: <20110308224225.1d924c40@surf>
On 3/8/2011 10:42 PM, Thomas Petazzoni wrote:
> The policy I'd like to see is to not add several skeletons to the
> mainline Buildroot tree, or at least not skeleton that are
> board-specific. But of course, it's only my opinion, and as a community
> project, the opinion of others also count.
>
> So, there are three cases :
>
> *) The changes needed compared to the official skeleton can be
> directly integrated into this official skeleton, because they make
> sense in a generic way. In this case, send some patches on the
> official skeleton, and we'll discuss them.
>
> *) The changes needed are interesting outside of the specifities of a
> particular hardware platform (and I think it's generally the case),
> then we can add a generic Buildroot option that will adjust the
> official skeleton as needed at build time. This is for example
> something that is being done for choosing between static /dev,
> devtmpfs, udev or mdev. It could be done for other customizations.
>
> *) The changes needed are very board-specific and cannot be considered
> as generic enough to be configuration options, in that case, what
> I'd suggest is a post-build script (BR2_ROOTFS_POST_BUILD_SCRIPT)
> that modifies the target filesystem, potentially by copying files
> from the board/<manufacturer>/<boardname> folder.
>
> Don't hesitate to discuss on the list the modifications you need on the
> skeleton, so that we can sort out together into which of the following
> three cases your modifications fall
Actually, I will no more need a specific skeleton for the moment.
Previous patches done on it are no more needed.
Thanks for this explanation, I will follow your advices if I need to add
some changes.
Regards
Ludovic Desroches
prev parent reply other threads:[~2011-03-10 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 16:44 [Buildroot] How to add a board with Buildroot 2011.02 Desroches, Ludovic
2011-03-08 21:42 ` Thomas Petazzoni
2011-03-09 7:59 ` Thomas De Schampheleire
2011-03-10 14:48 ` Ludovic Desroches [this message]
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=4D78E4C8.2060009@atmel.com \
--to=ludovic.desroches@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