From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/4] package/freescale-imx/firmware-imx: Add option for all i.MX FW needs
Date: Tue, 30 Jun 2020 14:08:29 +0200 [thread overview]
Message-ID: <20200630140829.14425eac@windsurf> (raw)
In-Reply-To: <20200630115341.GA791671@p1g2>
On Tue, 30 Jun 2020 13:53:41 +0200
Gary Bisson <gary.bisson@boundarydevices.com> wrote:
> > +config BR2_PACKAGE_FIRMWARE_IMX_VPU_CODA
> > + bool
> > + depends on BR2_PACKAGE_FIRMWARE_IMX
> > + default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX27ADS
> > + default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX37_3STACK
> > + default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX50
> > + default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX51
> > + default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX53
> > + default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX6Q
> > +
> > +config BR2_PACKAGE_FIRMWARE_IMX_VPU_MALONE
> > + bool
> > + depends on BR2_PACKAGE_FIRMWARE_IMX
> > + default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8
> > + default y if BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8X
>
> So here you are either copying all the VPU Malone blob or all the VPU
> CODA blob no matter the platform being used?
>
> Since we cleaning things up, I'd rather have a generic
> BR2_PACKAGE_FIRMWARE_IMX_VPU config for all the platforms that require a
> VPU blob (from firmware-imx).
> Then in the .mk I'd only copy the VPU blob associated to the platform
> selected (mx27, mx6, mx8 etc).
> That way we don't embed imx27 blob when we build for imx6. As someone
> mentioned in the previous, there's no need to embeds blobs we know are
> useless.
Could you list which blobs are relevant for each platform, so we get a
sense of what is needed and what is not ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-30 12:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 8:25 [Buildroot] [PATCH v2 0/4] package/freescale-imx: clean-up proposal Stephane Viau
2020-06-29 8:25 ` [Buildroot] [PATCH v2 1/4] package/freescale-imx: Move DDR FW choice down to firmware-imx package Stephane Viau
2020-06-29 8:25 ` [Buildroot] [PATCH v2 2/4] package/freescale-imx/firmware-imx: Add option for all i.MX FW needs Stephane Viau
2020-06-30 11:53 ` Gary Bisson
2020-06-30 12:08 ` Thomas Petazzoni [this message]
2020-06-30 12:18 ` Gary Bisson
2020-06-30 12:26 ` Thomas Petazzoni
2020-06-30 12:54 ` Gary Bisson
2020-06-29 8:25 ` [Buildroot] [PATCH v2 3/4] package/freescale-imx/firmware-imx: Clean up the image/target semantic Stephane Viau
2020-06-30 11:59 ` Gary Bisson
2020-06-30 12:09 ` Thomas Petazzoni
2020-06-29 8:25 ` [Buildroot] [PATCH v2 4/4] package/freescale-imx/firmware-imx: Fix sdma/vpu firmware install path Stephane Viau
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=20200630140829.14425eac@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