Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] linux-firmware: Break out some additional firmware
Date: Tue, 22 Mar 2016 14:56:30 -0700	[thread overview]
Message-ID: <1458683790.18406.33.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYn1aCCqk5=QV1iug+Zqz1s-=c2iF=mhZSaU6EOPAeR4A@mail.gmail.com>

On Tue, 2016-03-22 at 21:27 +0000, Burton, Ross wrote:
> 
> On 22 March 2016 at 18:13, Saul Wold <sgw@linux.intel.com> wrote:
> > +             ${PN}-iwlwifi-7265D ${PN}-iwlwifi-8000C ${PN}-
> > iwlwifi-8265 \
> > 
> opkg doesn't like this one bit:
> 
> | linux-firmware-iwlwifi-7265D
> | *** Error: Package name  contains illegal characters, (other than
> [a-z0-9.+-])
> 
Gah, no CAPS?  Sorry I did not do the full package specturm tests.

> Also, what Otavio said about splitting out - is C vs D a model thing
> or a version thing?
> 
I could merge them, I chose not to because it seems like it was more of
a model difference vs a version difference, since there were
overlapping version numbers.  The difference is the Dual band version,
I think.

Sau!

> Ross


  reply	other threads:[~2016-03-22 21:56 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
2016-03-22 21:27   ` Burton, Ross
2016-03-22 21:56     ` Saul Wold [this message]
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=1458683790.18406.33.camel@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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