Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bram Vlerick <bram.vlerick@openpixelsystems.org>
Cc: Gary Bisson <bisson.gary@gmail.com>,
	Refik Tuzakli <tuzakli.refik@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/freescale-imx/firmware-imx: allow ddr firmware version override
Date: Tue, 23 Aug 2022 23:39:35 +0200	[thread overview]
Message-ID: <20220823233935.047ae825@windsurf> (raw)
In-Reply-To: <20220816070517.2770099-1-bram.vlerick@openpixelsystems.org>

Hello Bram,

On Tue, 16 Aug 2022 09:05:17 +0200
Bram Vlerick <bram.vlerick@openpixelsystems.org> wrote:

> Add support for selecting a specific version of the DDR firmware
> version. For example Variscite's imx8mp-var-dart SOM requires the
> "_202006" version of the lpddr4_pmu_train_* binaries.
> 
> Signed-off-by: Bram Vlerick <bram.vlerick@openpixelsystems.org>
> ---
>  package/freescale-imx/firmware-imx/Config.in  | 10 +++++
>  .../firmware-imx/firmware-imx.mk              | 39 +++++++++++++------
>  2 files changed, 37 insertions(+), 12 deletions(-)

Thanks for this new iteration, which I have applied to our next branch.
This means this change will not be in Buildroot 2022.08, but in
Buildroot 2022.11.

Thanks again for your contribution!

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

      reply	other threads:[~2022-08-23 21:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  7:05 [Buildroot] [PATCH v2 1/1] package/freescale-imx/firmware-imx: allow ddr firmware version override Bram Vlerick
2022-08-23 21:39 ` Thomas Petazzoni 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=20220823233935.047ae825@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bisson.gary@gmail.com \
    --cc=bram.vlerick@openpixelsystems.org \
    --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