From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/2] buildroot: target: Add Blackfin architecture support.
Date: Tue, 26 Mar 2013 09:15:16 +0100 [thread overview]
Message-ID: <20130326091516.36a042d2@skate> (raw)
In-Reply-To: <51514D57.1090907@mind.be>
Dear Arnout Vandecappelle,
On Tue, 26 Mar 2013 08:25:11 +0100, Arnout Vandecappelle wrote:
> Looks like you again choose a difficult patch set to try to upstream...
>
> After reading all the comments in this thread, I propose to split up
> the patch set as follows in order to get some progress on it.
>
> 1. Add blackfin CPU choice.
> This patch adds a Target CPU configuration option and uses it to select a
> -m option for gcc.
>
> 2. Introduce target CPU revision.
> Adds the possibility (in the general infrastructure, not
> blackfin-specific) to have a free-form CPU revision string and append it
> to the target CPU. Only Blackfin actually uses this option.
>
> 3. Introduce BINFMT_FLAT.
> Just introduce the symbol and add options in blackfin to select it.
I don't think we should introduce just BINFMT_FLAT, but also
BINFMT_FDPIC (we already have a FDPIC symbol) and BINFMT_ELF, for
completeness. So I would rephrase this item into "Introduce BINFMT_*
symbols and refactor the existing usage to use BINFMT_FDPIC/BINFMT_ELF".
> 4. Introduce package-specific BINFMT_FLAT options.
> I.e. <PKG>_FLAT_STACKSIZE
>
> 5. Introduce blackfin-specific Makefile
> Probably needs more work.
>
> 6. Introduce NOMMU symbol
> Probably needs more work.
I fully agree with Arnout's proposal here. Let's do it step by step, so
that we discuss one issue after the other, and gets things merged
progressively.
Sonic, would you mind reworking your patch set to split it as Arnout is
suggesting?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-26 8:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 9:01 [Buildroot] [PATCH v3 1/2] package: Makefile.in: Add target compilation flags for NOMMU architecture Sonic Zhang
2013-03-22 9:01 ` [Buildroot] [PATCH v3 2/2] buildroot: target: Add Blackfin architecture support Sonic Zhang
2013-03-22 14:54 ` Thomas Petazzoni
2013-03-25 11:33 ` Sonic Zhang
2013-03-25 11:47 ` Thomas De Schampheleire
2013-03-26 8:16 ` Sonic Zhang
2013-03-26 8:41 ` Thomas Petazzoni
2013-03-26 9:36 ` Sonic Zhang
2013-03-26 10:08 ` Thomas Petazzoni
2013-03-26 7:25 ` Arnout Vandecappelle
2013-03-26 8:15 ` Thomas Petazzoni [this message]
2013-03-28 8:20 ` Sonic Zhang
2013-03-28 8:56 ` Thomas Petazzoni
2013-03-29 9:50 ` Sonic Zhang
2013-03-22 14:29 ` [Buildroot] [PATCH v3 1/2] package: Makefile.in: Add target compilation flags for NOMMU architecture Thomas Petazzoni
2013-03-22 17:28 ` Thomas De Schampheleire
2013-03-25 7:11 ` Arnout Vandecappelle
2013-03-25 7:50 ` Sonic Zhang
2013-03-25 7:57 ` Sonic Zhang
2013-03-25 7:58 ` Thomas Petazzoni
2013-03-25 8:51 ` Sonic Zhang
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=20130326091516.36a042d2@skate \
--to=thomas.petazzoni@free-electrons.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