From: Chris Trobridge <christrobridge@hotmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Installing only part of linux-firmware
Date: Tue, 9 Feb 2016 10:15:45 +0000 [thread overview]
Message-ID: <DUB130-W324DDADF2A42496E8D4656DAD60@phx.gbl> (raw)
In-Reply-To: <CAJTo0LZxoT8b433vJtJi7wZSfwWCcAXC77N3WFJkj3pzaLsNVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
I have been pondering linux-firmware recently too.
I have a device fitted that requires the 'iwlwifi-7260' firmware.
This was working but the current driver is requesting versions 13 to 10 of the firmware, in that order.The current (master) poky recipe has versions 8 and 9.The source repo (I believe, https://github.com/OpenELEC/iwlwifi-firmware/tree/master/firmware) has versions up to 17 now.
I can likewise add newer versions of firmware but do you ever prune out old versions? In this case is seems that the choice of firmware limited by the drivers specified by that version of yocto (via the kernel).
Regards,Chris
From: ross.burton@intel.com
Date: Mon, 8 Feb 2016 08:58:32 +0000
To: opensource@keylevel.com
CC: yocto@yoctoproject.org
Subject: Re: [yocto] Installing only part of linux-firmware
On 7 February 2016 at 21:49, Chris Tapp <opensource@keylevel.com> wrote:
I’ve now done this by creating a bbappend for linux-firmware:
PACKAGES =+ "${PN}-rtl_nic"
FILES_${PN}-rtl_nic = " \
/lib/firmware/rtl_nic/* \
“
Does what I want, but is that the best way of doing it?
This is the best way for you now.
That's exactly why the recipe has quite a lot of subpackages, feel free to submit more upstream.
Ross
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[-- Attachment #2: Type: text/html, Size: 2619 bytes --]
next prev parent reply other threads:[~2016-02-09 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 16:50 Installing only part of linux-firmware Chris Tapp
2016-02-07 21:49 ` Chris Tapp
2016-02-08 8:58 ` Burton, Ross
2016-02-09 10:15 ` Chris Trobridge [this message]
2016-02-09 13:39 ` Chris Trobridge
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=DUB130-W324DDADF2A42496E8D4656DAD60@phx.gbl \
--to=christrobridge@hotmail.com \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.org \
/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.