From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] linux-firmware package : files not copied to TARGET_DIR
Date: Tue, 8 Jan 2019 15:39:07 +0100 [thread overview]
Message-ID: <20190108153907.2b18149f@windsurf> (raw)
In-Reply-To: <6de3a002-7c43-9658-507b-5a44f57386d0@gmx.com>
Hello,
On Tue, 8 Jan 2019 14:17:24 +0100, David Picard wrote:
> I am using the CONFIG_E100 kernel driver, which needs
> e100/d102e_ucode.bin from package linux-firmware for chipset Intel
> 82551IT Fast Ethernet Controller.
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/e100
>
> I selected BR2_PACKAGE_LINUX_FIRMWARE in Buildroot, but none of the
> options in the submenu. The file I need is actually present in the
> package build directory, but is not installed.
Well, if you don't enable any of the options in the linux-firmware
submenu, then no firmware gets installed.
> I was thinking of making a custom patch for linux-firmware.mk to copy
> just the one file I need. What do you think ?
That's what you need to do: add an option in
package/linux-firmware/Config.in for your firmware, and add the
necessary code in package/linux-firmware/linux-firmware.mk to add the
firmware to the LINUX_FIRMWARE_FILES variable when the option is
enabled. Don't forget to update LINUX_FIRMWARE_ALL_LICENSE_FILES
accordingly if needed. And to submit the resulting patch!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-08 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 9:43 [Buildroot] linux-firmware package : files not copied to TARGET_DIR David Picard
2019-01-08 12:49 ` Thomas Petazzoni
2019-01-08 13:17 ` David Picard
2019-01-08 14:39 ` Thomas Petazzoni [this message]
2019-01-09 8:00 ` David Picard
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=20190108153907.2b18149f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.