From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Charles Hardin <ckhardin@gmail.com>
Cc: Refik Tuzakli <tuzakli.refik@gmail.com>,
Gary Bisson <bisson.gary@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/firmware-imx: ensure the linux firmware is installed first
Date: Mon, 10 Jul 2023 20:50:49 +0200 [thread overview]
Message-ID: <20230710205049.419f4fea@windsurf> (raw)
In-Reply-To: <20230620170922.3722-1-ckhardin@gmail.com>
On Tue, 20 Jun 2023 10:09:22 -0700
Charles Hardin <ckhardin@gmail.com> wrote:
> There was imx SDMA firmware in the base linux-firmware package at
> one time, but the firmware-imx is updated with the latest versions
> from NXP releases.
>
> This just ensures a dependency is set so that the imx package will
> always come later in case an overlap occurs again.
>
> Signed-off-by: Chares Hardin <ckhardin@gmail.com>
> Signed-off-by: Charles Hardin <ckhardin@gmail.com>
> ---
> package/freescale-imx/firmware-imx/firmware-imx.mk | 4 ++++
> 1 file changed, 4 insertions(+)
Applied to master, thanks.
That being said, the BR2_PER_PACKAGE_DIRECTORIES=y mechanism requires
that packages don't overwrite files installed by other packages, so at
some point, this will have to be revisited. But this issue exists for
many other packages anyway, and we are far from having addressed all
those issues.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-10 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 17:09 [Buildroot] [PATCH 1/1] package/firmware-imx: ensure the linux firmware is installed first Charles Hardin
2023-06-28 7:55 ` Gary Bisson
2023-07-10 18:50 ` Thomas Petazzoni via buildroot [this message]
2023-08-25 12:53 ` Peter Korsgaard
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=20230710205049.419f4fea@windsurf \
--to=buildroot@buildroot.org \
--cc=bisson.gary@gmail.com \
--cc=ckhardin@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tuzakli.refik@gmail.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