Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] sunxi-mali-mainline: add support for arm64(aarch64) architecture and r8p1 blob version.
Date: Wed, 22 Aug 2018 13:21:13 +0200	[thread overview]
Message-ID: <20180822132113.78b0d190@windsurf> (raw)
In-Reply-To: <20180822000648.23314-2-giulio.benetti@micronovasrl.com>

Hello,

On Wed, 22 Aug 2018 02:06:47 +0200, Giulio Benetti wrote:
> Blobs for arm64(aarch64) and r8p1 version are now available at Bootlin
> Github.
> 
> So:
> - Bump version to latest commit:
> For arm64 architecture and r8p1 version.
> 
> git shortlog --no-merges cb3e8ece9b2c3a70cbeb3204cd6f30eceaa32023..
> Giulio Benetti (1):
>       Reorder folders splitting includes and libraries.
> 
> Maxime Ripard (6):
>       Move binaries to an arch subfolder
>       Make x11 binaries path consistent
>       Add r6p2 arm wayland blobs
>       Add r6p2 arm64 blobs
>       Add r8p1 fbdev blobs
>       Add r8p1 arm64 fbdev blobs
> 
> - Add support for them also under arm64(aarch64) architecture copying the
> right blobs according to architecture(arm or arm64) checking if BR2_arm
> or BR2_aarch64 is enabled.
> Only BR2_arm needs to provide BR2_ARM_EABIHF, so check must be done only
> in that case.
> - Mali-blobs repository folder layout has been reordered, so modify path
> when copying headers and libraries.
> - When copying libraries copy only *.so* files to avoid useless files to
> end into target folder.
> 
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
> ---
>  package/sunxi-mali-mainline/Config.in             |  6 ++++--
>  .../sunxi-mali-mainline/sunxi-mali-mainline.mk    | 15 ++++++++++-----
>  2 files changed, 14 insertions(+), 7 deletions(-)

This could have been three patches: one bumping the version, one adding
support for the r8p1 version, and one adding support for aarch64. But
OK, I've applied as is, as the patch wasn't too large. But for your
next contributions, please make sure to split them in logical changes.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-22 11:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22  0:06 [Buildroot] [PATCH v2 0/2] sunxi-mali-mainline*: add arm64 build support and Giulio Benetti
2018-08-22  0:06 ` [Buildroot] [PATCH v2 1/2] sunxi-mali-mainline: add support for arm64(aarch64) architecture and r8p1 blob version Giulio Benetti
2018-08-22 11:21   ` Thomas Petazzoni [this message]
2018-08-22  0:06 ` [Buildroot] [PATCH v2 2/2] sunxi-mali-mainline-driver: bump version and add support for building on arm64(aarch64) Giulio Benetti
2018-08-22 11:29   ` Thomas Petazzoni
2018-08-22 18:37     ` Giulio Benetti
2018-08-22 19:26       ` Thomas Petazzoni
2018-08-24 19:10         ` Giulio Benetti
2018-08-24 19:58           ` Thomas Petazzoni
2018-08-24 21:14           ` Yann E. MORIN
2018-08-24 21:28             ` Giulio Benetti
2018-08-24 21:39               ` Yann E. MORIN
2018-08-26 21:36         ` Giulio Benetti

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=20180822132113.78b0d190@windsurf \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox