From: Saul Wold <sgw@linux.intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] linux-firmware: Break out some additional firmware
Date: Tue, 22 Mar 2016 14:58:01 -0700 [thread overview]
Message-ID: <1458683881.18406.35.camel@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKrtzYwE-Y2pCD7wCMcwY9CVixxAg+dmNJkL2o=CQrmL=w@mail.gmail.com>
On Tue, 2016-03-22 at 18:07 -0300, Otavio Salvador wrote:
> Hello Saul,
>
> First I would like to thank you to manage this upgrade and
> refactoring. This recipe was indeed requiring some love and you did a
> great job.
>
I want to go further, but not before the release, I am thinking of some
mappings and automation to have all the firmware packaged in smaller
blobs, but will require some name mapping I think.
Sau!
> On Tue, Mar 22, 2016 at 3:13 PM, Saul Wold <sgw@linux.intel.com>
> wrote:
> >
> > This breaks out new firmware from the iwlwifi firmware along with
> > the i915 graphics firmware.
> >
> > Signed-off-by: Saul Wold <sgw@linux.intel.com>
> > ---
> > .../linux-firmware/linux-firmware_git.bb | 25
> > +++++++++++++++++++---
> > 1 file changed, 22 insertions(+), 3 deletions(-)
> >
> > diff --git a/meta/recipes-kernel/linux-firmware/linux-
> > firmware_git.bb b/meta/recipes-kernel/linux-firmware/linux-
> > firmware_git.bb
> > index 04d9471..6f6581a 100644
> > --- a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
> > +++ b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
> > @@ -224,6 +224,9 @@ PACKAGES =+ "${PN}-ralink-license ${PN}-ralink
> > \
> > ${PN}-iwlwifi-6050-4 ${PN}-iwlwifi-6050-5 \
> As done in the other one, this might make sense to consolidate into a
> single one.
>
> >
> > ${PN}-iwlwifi-7260 \
> > ${PN}-iwlwifi-7265 \
> > + ${PN}-iwlwifi-7265D ${PN}-iwlwifi-8000C ${PN}-
> > iwlwifi-8265 \
> Does it make sense to split D out ? I think adding it inside the
> former might avoid too much fragmentation.
>
next prev parent reply other threads:[~2016-03-22 21:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 18:13 [PATCH 0/4] linux-firmware update and cleanup Saul Wold
2016-03-22 18:13 ` [PATCH 1/4] linux-firmware: Update to latest HEAD Saul Wold
2016-03-22 18:13 ` [PATCH 2/4] linux-firmware: Collapse iwlwifi firmware blobs for 7260 and 7265 Saul Wold
2016-03-22 18:13 ` [PATCH 3/4] linux-firmware: Clean-up and sync license data Saul Wold
2016-03-22 18:13 ` [PATCH 4/4] linux-firmware: Break out some additional firmware Saul Wold
2016-03-22 21:07 ` Otavio Salvador
2016-03-22 21:58 ` Saul Wold [this message]
2016-03-22 21:27 ` Burton, Ross
2016-03-22 21:56 ` Saul Wold
2016-03-22 22:37 ` Burton, Ross
2016-03-22 22:51 ` Paul Eggleton
2016-03-22 23:09 ` Phil Blundell
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=1458683881.18406.35.camel@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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