From: "Wold, Saul" <saul.wold@intel.com>
To: "armccurdy@gmail.com" <armccurdy@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: linux-firmware fetcher warnings
Date: Tue, 31 Oct 2017 23:19:45 +0000 [thread overview]
Message-ID: <1509491984.11491.36.camel@intel.com> (raw)
In-Reply-To: <CAJ86T=WwqN3H-KR5TYnvjG37XNvRVqdWug2o6dR5wiKEzygQ2Q@mail.gmail.com>
On Tue, 2017-10-31 at 14:35 -0700, Andre McCurdy wrote:
> The linux-firmware recipe is currently trying to fetch
> iwlwifi-8000C-19.ucode which according to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/15792
> 81
>
> is an unreleased firmware image from a unofficial fork of the main
> linux-firmware repo. The "iwlwifi-8000C-19.ucode" file isn't found in
> the current master branch of the iwlwifi linux-firmware repo (and
> doesn't seem to be there in the history either...).
>
Yeah seems like it got rebased away :-(!
> The mystery firmware image was added to the linux-firmware recipe by:
>
> http://git.openembedded.org/openembedded-core/commit/?id=8b3d3ac84f
> 787bf4ecccdcbcb97f2dac56acd45c
>
> Is this firmware still required? If so, should SRC_URI be updated to
> fetch it directly from downloads.yoctoproject.org?
I will do some research, it was needed for some hardware when it was
put into the meta-intel and then later we moved it into OE-Core.
Sau!
prev parent reply other threads:[~2017-10-31 23:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 21:35 linux-firmware fetcher warnings Andre McCurdy
2017-10-31 23:19 ` Wold, Saul [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=1509491984.11491.36.camel@intel.com \
--to=saul.wold@intel.com \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.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.