From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/meson: fix cpu_family format
Date: Sun, 16 Dec 2018 11:58:41 +0100 [thread overview]
Message-ID: <20181216115841.0708cd69@windsurf.home> (raw)
In-Reply-To: <87pnu1an4d.fsf@tkos.co.il>
Hello,
On Sun, 16 Dec 2018 10:31:46 +0200, Baruch Siach wrote:
> So it seems:
>
> git grep 'select BR2_ARCH_IS_64' -- arch/
> arch/Config.in: select BR2_ARCH_IS_64
> arch/Config.in: select BR2_ARCH_IS_64
> arch/Config.in: select BR2_ARCH_IS_64
> arch/Config.in: select BR2_ARCH_IS_64
> arch/Config.in: select BR2_ARCH_IS_64
> arch/Config.in: select BR2_ARCH_IS_64
> arch/Config.in: select BR2_ARCH_IS_64
> arch/Config.in: select BR2_ARCH_IS_64
> arch/Config.in.riscv: select BR2_ARCH_IS_64
All other architectures have separate top-level options for their
32-bit and 64-bit variants. I.e i386 vs x86-64, arm vs. arm64, mipsel
vs. mipsel64, etc.
For RISC-V, since the kernel supports both 32-bit and 64-bit as a
single architecture, we decided to do the same in Buildroot, and have a
single top-level BR2_riscv option.
> Not sure what the reason for that is. riscv is also special in that
> there is no support for its 32bit variant in Buildroot.
Mark has already sent patches adding support for RISC-V 32-bit, they
are in patchwork, waiting for testing/review/merge.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-16 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 7:13 [Buildroot] [PATCH 1/1] package/meson: fix cpu_family format james.hilliard1 at gmail.com
2018-12-16 7:38 ` Baruch Siach
2018-12-16 8:07 ` James Hilliard
2018-12-16 8:31 ` Baruch Siach
2018-12-16 10:58 ` Thomas Petazzoni [this message]
2018-12-16 10:59 ` Thomas Petazzoni
2018-12-16 11:04 ` James Hilliard
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=20181216115841.0708cd69@windsurf.home \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.