All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: "Tom Rini" <trini@konsulko.com>,
	"Andre Przywara" <andre.przywara@arm.com>,
	"Marek Behún" <marek.behun@nic.cz>,
	"Peter Robinson" <pbrobinson@gmail.com>,
	"Matthias Brugger" <mbrugger@suse.com>,
	"Heinrich Schuchardt" <heinrich.schuchardt@canonical.com>,
	"Samuel Holland" <samuel@sholland.org>,
	u-boot@lists.denx.de, "Jagan Teki" <jagan@amarulasolutions.com>,
	"Alex G ." <mr.nuke.me@gmail.com>,
	"Artem Lapkin" <email2tema@gmail.com>,
	"Priyanka Jain" <priyanka.jain@nxp.com>,
	"Sughosh Ganu" <sughosh.ganu@linaro.org>
Subject: Re: [PATCH v4 1/4] tools: Separate image types which depend on OpenSSL
Date: Fri, 22 Oct 2021 19:11:05 +0200	[thread overview]
Message-ID: <20211022171105.zlhmxvhtstr6vao2@pali> (raw)
In-Reply-To: <87v91pnh08.fsf@yucca>

On Friday 22 October 2021 09:47:35 Vagrant Cascadian wrote:
> do some boards use board-specific tools as part of their build processes?

Lot of boards are using mkimage for generating final U-Boot binary.

Prior U-Boot 2021.10 all 32-bit mvebu boards used own specific version
of mkimage to generate final U-Boot binary. mkimage had own compile time
options (defined in board include header files) which generated unique
./tools/mkimage binary, specific for just one board.

Since U-Boot 2021.10 now all 32-bit mvebu boards are using one common
mkimage binary. So you can even do defconfig for some x86 board, build
mkimage binary and then you can use this mkimage binary also for
building final mvebu (arm) U-Boot binary.

Side effect of this change was hard dependency on openssl, but we are
discussing how to solve and remove that hard dependency.

I do not know if there are any processors, SoCs or boards which require
board-specific version of some tool (e.g. mkimage) in U-Boot 2021.10.

  reply	other threads:[~2021-10-22 17:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20  2:44 [PATCH v4 0/4] sunxi: TOC0 image type support Samuel Holland
2021-10-20  2:44 ` [PATCH v4 1/4] tools: Separate image types which depend on OpenSSL Samuel Holland
2021-10-20  7:29   ` Pali Rohár
2021-10-20 13:29     ` Andre Przywara
2021-10-20 13:47       ` Pali Rohár
2021-10-20 14:14         ` Samuel Holland
2021-10-21 12:33           ` Marek Behún
2021-10-21 13:00           ` Marek Behún
2021-10-21 13:01             ` Pali Rohár
2021-10-22  1:25             ` Samuel Holland
2021-10-22 10:09             ` Heinrich Schuchardt
2021-10-22 14:59               ` Marek Behún
2021-10-22 15:09                 ` Tom Rini
2021-10-22 15:56                   ` Andre Przywara
2021-10-22 16:22                     ` Tom Rini
2021-10-22 16:47                       ` Vagrant Cascadian
2021-10-22 17:11                         ` Pali Rohár [this message]
2021-10-22 17:20                         ` Andre Przywara
2021-10-22 19:46                           ` Vagrant Cascadian
2021-10-27 17:11                             ` Tom Rini
2021-10-27 20:11                               ` Peter Robinson
2021-10-28 15:44                   ` Matthias Brugger
2021-10-20  2:44 ` [PATCH v4 2/4] tools: mkimage: Add Allwinner TOC0 support Samuel Holland
2021-10-20 23:49   ` Andre Przywara
2021-10-20  2:44 ` [PATCH v4 3/4] sunxi: Support SPL in both eGON and TOC0 images Samuel Holland
2021-10-20 23:49   ` Andre Przywara
2021-10-20  2:44 ` [PATCH v4 4/4] sunxi: Support building a SPL as a TOC0 image Samuel Holland
2021-10-20 23:50   ` Andre Przywara

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=20211022171105.zlhmxvhtstr6vao2@pali \
    --to=pali@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=email2tema@gmail.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=jagan@amarulasolutions.com \
    --cc=marek.behun@nic.cz \
    --cc=mbrugger@suse.com \
    --cc=mr.nuke.me@gmail.com \
    --cc=pbrobinson@gmail.com \
    --cc=priyanka.jain@nxp.com \
    --cc=samuel@sholland.org \
    --cc=sughosh.ganu@linaro.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=vagrant@debian.org \
    /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.