From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/imx-sc-firmware: bump to version 1.2.1
Date: Sun, 22 Dec 2019 14:24:21 +0100 [thread overview]
Message-ID: <20191222142421.13cd522c@windsurf> (raw)
In-Reply-To: <bb1e9dbdd73a1e0b8fead464ddf9fa83@cotds.org>
Hello,
On Wed, 18 Dec 2019 22:22:08 +0100
Julien Olivain <juju@cotds.org> wrote:
> I agree with you that we can't really force a single version for all
> boards. Exposing a choice of version (like for Kernel, U-Boot, ATF)
> seems a good trade-of (this is what I had in mind in [1]).
>
> For i.MX packages, several packages are in that case: I think mainly
> about imx-sc-firmware, firmware-imx and imx-gpu-viv.
>
> The only problem I see right now is that from one version to
> another, the build recipe might slightly change. We saw that recently
> in [2]. This means we can't have a single recipe and a free
> _CUSTOM_VERSION config option.
>
> What about having a KConfig "choice" list of few supported versions,
> also showing NXP BSP name, to help i.MX defconfig maintainers to
> select the right version ? That would allow the package recipe to
> adjust commands for a given version.
>
> For example, for the imx-sc-firmware, the list of choices would be:
> - 1.1.4 (4.14.78_1.0.0)
> - 1.2.1 (4.14.98_2.0.0)
> - 1.2.2 (4.19.35_1.0.0)
> - 1.2.7.1 (4.19.35_1.1.0)
>
> What do you think about this approach?
In general, we don't really like to have too much version selection for
components, because it makes the maintenance difficult, and it is also
more difficult for users as they have to know which version to use.
However, for the specific case of this firmware package, I don't really
see any other option than what you're proposing.
One question is: how does it work if one wants to use the upstream
Linux kernel?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-22 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 13:04 [Buildroot] [PATCH 1/1] package/imx-sc-firmware: bump to version 1.2.1 Julien Olivain
2019-12-18 13:10 ` Fabio Estevam
2019-12-18 13:23 ` Julien Olivain
2019-12-18 13:27 ` Fabio Estevam
2019-12-18 21:22 ` Julien Olivain
2019-12-18 21:40 ` Fabio Estevam
2019-12-22 13:24 ` Thomas Petazzoni [this message]
2019-12-22 14:31 ` Fabio Estevam
2019-12-22 14:34 ` Peter Korsgaard
2019-12-22 14:38 ` Fabio Estevam
2019-12-18 13:28 ` Fabio Estevam
2019-12-22 13:22 ` Thomas Petazzoni
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=20191222142421.13cd522c@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