Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: ibai.erkiaga-elorza@amd.com, michal.simek@amd.com,
	thomas.petazzoni@bootlin.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 01/10] package/binutils-bare-metal: new package
Date: Mon, 16 Oct 2023 12:11:11 +0200	[thread overview]
Message-ID: <20231016121111.480b6b4c@booty> (raw)
In-Reply-To: <20230924151205.2099293-1-neal.frager@amd.com>

Hi Neal, Ibai,

On Sun, 24 Sep 2023 16:11:56 +0100
Neal Frager <neal.frager@amd.com> wrote:

> +# if toolchain is for microblazeel-xilinx, apply Xilinx patch set
> +ifeq ($(BR2_PACKAGE_HOST_TOOLCHAIN_BARE_METAL_ARCH),"microblazeel-xilinx")
> +HOST_BINUTILS_BARE_METAL_EXTRA_DOWNLOADS = https://github.com/Xilinx/meta-xilinx/archive/refs/tags/xlnx-rel-v2023.1.tar.gz
> +
> +define HOST_BINUTILS_BARE_METAL_EXTRACT_PATCHES
> +  mkdir -p $(@D)/patches
> +  tar -xf $(HOST_BINUTILS_BARE_METAL_DL_DIR)/xlnx-rel-v2023.1.tar.gz \
> +      --strip-components=5 \
> +      -C $(@D)/patches \
> +      meta-xilinx-xlnx-rel-v2023.1/meta-microblaze/recipes-devtools/binutils/binutils
> +endef
> +HOST_BINUTILS_BARE_METAL_POST_EXTRACT_HOOKS += HOST_BINUTILS_BARE_METAL_EXTRACT_PATCHES

I think all the patches needed to build zynqmp firmwares are now in
mainline, right? (which is a great thing!!) If it is the case, then you
should probably remove all this tarball mangling and just add the
relevant patches as regular package/*/*.patch files, both for binutils
and for gcc.

> +
> +define HOST_BINUTILS_BARE_METAL_APPLY_LOCAL_PATCHES
> +	$(APPLY_PATCHES) $(@D) $(@D)/patches *.patch;
> +endef
> +HOST_BINUTILS_BARE_METAL_POST_PATCH_HOOKS += HOST_BINUTILS_BARE_METAL_APPLY_LOCAL_PATCHES
> +endif #ifeq ($(BR2_PACKAGE_HOST_TOOLCHAIN_BARE_METAL_ARCH),"microblazeel-xilinx")
> +
> +# Don't build documentation. It takes up extra space / build time,
> +# and sometimes needs specific makeinfo versions to work
> +HOST_BINUTILS_BARE_METAL_CONF_ENV += MAKEINFO=true
> +HOST_BINUTILS_BARE_METAL_MAKE_OPTS += MAKEINFO=true
> +HOST_BINUTILS_BARE_METAL_INSTALL_OPTS += MAKEINFO=true install
> +
> +HOST_BINUTILS_BARE_METAL_CONF_OPTS = \
> +	--target=$(BR2_PACKAGE_HOST_TOOLCHAIN_BARE_METAL_ARCH)-elf \

As pointed out in v3, this patch series is not bisectable due to the
chicken-egg loop on BR2_PACKAGE_HOST_TOOLCHAIN_BARE_METAL_ARCH, which
is added in patch 4 and used in patches 1-3. I don't know how this
could be better handled, thus if the maintainers have no objections I
also won't have any.

Otherwise LGTM.

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-10-16 10:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 15:11 [Buildroot] [PATCH v4 01/10] package/binutils-bare-metal: new package Neal Frager via buildroot
2023-09-24 15:11 ` [Buildroot] [PATCH v4 02/10] package/gcc-bare-metal: " Neal Frager via buildroot
2023-10-16 10:11   ` Luca Ceresoli via buildroot
2023-09-24 15:11 ` [Buildroot] [PATCH v4 03/10] package/newlib-bare-metal: " Neal Frager via buildroot
2023-10-16 10:11   ` Luca Ceresoli via buildroot
2023-09-24 15:11 ` [Buildroot] [PATCH v4 04/10] toolchain/toolchain-bare-metal: new toolchain Neal Frager via buildroot
2023-10-16 10:11   ` Luca Ceresoli via buildroot
2023-10-18 12:46     ` Frager, Neal via buildroot
2023-10-19  7:19       ` Luca Ceresoli via buildroot
     [not found]         ` <MN0PR12MB6004F504CD8806653C2D244BA0D4A@MN0PR12MB6004.namprd12.prod.outlook.com>
2023-10-19  8:13           ` Frager, Neal via buildroot
2023-09-24 15:12 ` [Buildroot] [PATCH v4 05/10] boot/zynqmp-firmware: new boot firmware Neal Frager via buildroot
2023-10-16 10:11   ` Luca Ceresoli via buildroot
2023-09-24 15:12 ` [Buildroot] [PATCH v4 06/10] boot/uboot.mk: new zynqmp pmufw build option Neal Frager via buildroot
2023-10-16 10:12   ` Luca Ceresoli via buildroot
2023-09-24 15:12 ` [Buildroot] [PATCH v4 07/10] configs/zynqmp*: build pmufw source Neal Frager via buildroot
2023-10-16 10:12   ` Luca Ceresoli via buildroot
2023-09-24 15:12 ` [Buildroot] [PATCH v4 08/10] boot/versal-firmware: new boot firmware Neal Frager via buildroot
2023-10-16 10:12   ` Luca Ceresoli via buildroot
2023-09-24 15:12 ` [Buildroot] [PATCH v4 09/10] configs/versal_vck190_defconfig: build plm and psmfw source Neal Frager via buildroot
2023-10-16 10:12   ` Luca Ceresoli via buildroot
2023-09-24 15:12 ` [Buildroot] [PATCH v4 10/10] package/versal-firmware: remove package Neal Frager via buildroot
2023-10-16 10:12   ` Luca Ceresoli via buildroot
2023-10-16 10:11 ` Luca Ceresoli via buildroot [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=20231016121111.480b6b4c@booty \
    --to=buildroot@buildroot.org \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=michal.simek@amd.com \
    --cc=neal.frager@amd.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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