Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Fabio Estevam <festevam@gmail.com>,
	Fabrice Goucem <fabrice.goucem@oss.nxp.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/imx6ullevk_defconfig: bump Linux to 6.6.4 and U-Boot to 2023.10
Date: Sat, 09 Dec 2023 16:10:54 +0100	[thread overview]
Message-ID: <878r63pg1t.fsf@48ers.dk> (raw)
In-Reply-To: <801a7ae9-e6cf-40bf-8250-6a9a36b1b67c@benettiengineering.com> (Giulio Benetti's message of "Sat, 9 Dec 2023 16:06:44 +0100")

>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:

 > Hi Peter,
 > On 09/12/23 15:57, Peter Korsgaard wrote:
 >>>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:
 >> > Let's also enable NXP firmware package to let latest SDMA
 >> firmware to be
 >> > loaded. To achieve this we also need to enable dynamic eudev to let it
 >> > to load the firmware.
 >> Why is that? I thought request_firmware() nowadays didn't need any
 >> help
 >> from user space to fetch files from /lib/firmware?
 >> Is it because this is requested very early before the rootfs is
 >> mounted?

 > Exactly, if the driver is built-in Linux it's too early to search rootfs
 > because it's not mounted.

 > Of course during drivers' probe()s and all kernel calls using dma will
 > use ROM SDMA Firmware until SDMA Firmware is loaded from rootfs so those
 > calls will have worse performances.
 > Of course NXP Firmware can't be embedded into Linux because it's
 > proprietary and license doesn't allow us to do that.

OK. Committed after extending the commit message to explain that, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-12-09 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 12:07 [Buildroot] [PATCH] configs/imx6ullevk_defconfig: bump Linux to 6.6.4 and U-Boot to 2023.10 Giulio Benetti
2023-12-07 12:07 ` [Buildroot] [PATCH] configs/freescale_imx6ullevk_defconfig: bump Linux and U-Boot to lf-6.1.36-2.1.0 Giulio Benetti
2023-12-07 12:24 ` [Buildroot] [PATCH] configs/imx6ullevk_defconfig: bump Linux to 6.6.4 and U-Boot to 2023.10 Fabio Estevam
2023-12-09 14:57 ` Peter Korsgaard
2023-12-09 15:06   ` Giulio Benetti
2023-12-09 15:10     ` Peter Korsgaard [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=878r63pg1t.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fabrice.goucem@oss.nxp.com \
    --cc=festevam@gmail.com \
    --cc=giulio.benetti@benettiengineering.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