From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [v3 1/1] configs: add raspberrypi3 64bits defconfig
Date: Thu, 04 May 2017 09:24:53 +0200 [thread overview]
Message-ID: <87zietaxtm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170418155959.27129-1-gael.portay@savoirfairelinux.com> ("Gaël PORTAY"'s message of "Tue, 18 Apr 2017 11:59:59 -0400")
>>>>> "Ga?l" == Ga?l PORTAY <gael.portay@savoirfairelinux.com> writes:
> This configuration builds a 64bit image for RaspberryPi 3.
> Signed-off-by: Ga?l PORTAY <gael.portay@savoirfairelinux.com>
> ---
> Changes since v2:
> - Set Floating Point Unit to VFPv4 (Martin Bark)
> Changes since v1:
> - Symlink raspberrypi3-64 and update BR2_ROOTFS_POST_[BUILD|IMAGE]_SCRIPT
> - Add BR2_cortex_a53 architecture
> - Set BR2_TARGET_ROOTFS_EXT2_BLOCKS to 120000
> - Update kernel repository version
> diff --git a/configs/raspberrypi3_64_defconfig b/configs/raspberrypi3_64_defconfig
> new file mode 100644
> index 000000000..aa78c162b
> --- /dev/null
> +++ b/configs/raspberrypi3_64_defconfig
> @@ -0,0 +1,39 @@
> +BR2_aarch64=y
> +BR2_cortex_a53=y
> +BR2_ARM_FPU_VFPV4=y
> +
> +BR2_GCC_VERSION_6_X=y
> +BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
Any specific reason why you want to use gcc 6.x / glibc? We normally
don't do that in our defconfigs, and gcc 5 / uClibc works here with a
quick test - So I've removed it.
> +# Filesystem / image
> +BR2_TARGET_ROOTFS_EXT2=y
> +BR2_TARGET_ROOTFS_EXT2_4=y
> +BR2_TARGET_ROOTFS_EXT2_BLOCKS=120000
I was going to drop this EXT2_BLOCKS, but I did a test build and the
kernel config indeed enables so many modules that they don't fit in our
default size, so I've added a comment about that and committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-05-04 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 15:59 [Buildroot] [v3 1/1] configs: add raspberrypi3 64bits defconfig Gaël PORTAY
2017-05-01 23:34 ` Ricardo Martincoski
2017-05-04 7:24 ` Peter Korsgaard [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=87zietaxtm.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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