From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] toolchain: add sparc64 architecture support
Date: Fri, 28 Aug 2015 20:22:24 +0200 [thread overview]
Message-ID: <20150828202224.2f12a93c@free-electrons.com> (raw)
In-Reply-To: <20150811203709.GA9885@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Tue, 11 Aug 2015 22:37:09 +0200, Waldemar Brodkorb wrote:
> Introduce sparc64 architecture to buildroot.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> arch/Config.in | 12 +++++++++++-
> arch/Config.in.sparc | 9 +++++++--
> toolchain/toolchain-buildroot/Config.in | 3 ++-
> 3 files changed, 20 insertions(+), 4 deletions(-)
Are you willing to help fixing the autobuilder failures that will be
found on this new architecture? I'm fine with supporting additional
architectures, but Sparc64 seems unlikely to be used in embedded
contexts, so my concern is that it may be just a "demo support". But of
course, if you're fine with helping with autobuilder issues (which you
are already doing with lots of uClibc issues), I'll be happy to merge
this.
One question below, though.
> diff --git a/arch/Config.in.sparc b/arch/Config.in.sparc
> index cc10e8d..faf4a11 100644
> --- a/arch/Config.in.sparc
> +++ b/arch/Config.in.sparc
> @@ -1,7 +1,8 @@
> choice
> prompt "Target Architecture Variant"
> - depends on BR2_sparc
> - default BR2_sparc_v8
> + depends on BR2_sparc || BR2_sparc64
> + default BR2_sparc_v8 if BR2_sparc
> + default BR2_sparc_v9 if BR2_sparc64
> help
> Specific CPU variant to use
>
> @@ -9,10 +10,13 @@ config BR2_sparc_v8
> bool "v8"
> config BR2_sparc_leon3
> bool "leon3"
> +config BR2_sparc_v9
> + bool "v9"
This means that v8, leon3 or v9 can be selected for either SPARC or
SPARC64. Are SPARCv8 or Leon3 really 64 bit capable CPU variants?
> endchoice
>
> config BR2_ARCH
> default "sparc" if BR2_sparc
> + default "sparc64" if BR2_sparc64
>
> config BR2_ENDIAN
> default "BIG"
> @@ -20,3 +24,4 @@ config BR2_ENDIAN
> config BR2_GCC_TARGET_CPU
> default "leon3" if BR2_sparc_leon3
> default "v8" if BR2_sparc_v8
> + default "ultrasparc" if BR2_sparc_v9
Why not using v9 here? It's a valid -mcpu value:
'-mcpu=CPU_TYPE'
Set the instruction set, register set, and instruction scheduling
parameters for machine type CPU_TYPE. Supported values for
CPU_TYPE are 'v7', 'cypress', 'v8', 'supersparc', 'hypersparc',
'leon', 'sparclite', 'f930', 'f934', 'sparclite86x', 'sparclet',
'tsc701', 'v9', 'ultrasparc', 'ultrasparc3', 'niagara', 'niagara2',
'niagara3', and 'niagara4'.
We will have to add one SPARC64 toolchain to the autobuilders to test
this architecture. Maybe an external toolchain built by Buildroot is
the best option.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-28 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 20:37 [Buildroot] [PATCH 1/2] toolchain: add sparc64 architecture support Waldemar Brodkorb
2015-08-27 18:27 ` Waldemar Brodkorb
2015-08-28 18:22 ` Thomas Petazzoni [this message]
[not found] ` <20150829074104.GB8475@waldemar-brodkorb.de>
2015-08-29 8:11 ` Thomas Petazzoni
2015-10-08 14:08 ` Gustavo Zacarias
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=20150828202224.2f12a93c@free-electrons.com \
--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