From: Saul Wold <saul.wold@intel.com>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Could you help to have a look at BUG 660
Date: Wed, 02 Mar 2011 18:23:58 -0800 [thread overview]
Message-ID: <4D6EFBBE.5040004@intel.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A334FC309@shsmsx501.ccr.corp.intel.com>
On 03/02/2011 05:43 PM, Xu, Dongxiao wrote:
> Hi Richard and Saul,
>
> Could you help to have a review of BUG 660?
>
> http://bugzilla.pokylinux.org/show_bug.cgi?id=660
>
> BUG 660 is about missing kernel firmware in poky-image-minimal.
>
> As from most of the machine configuration files in current poky, including
> igep0030.conf, "kernel-modules" and "linux-firmware-sd8686" are part of
> "MACHINE_EXTRA_RRECOMMENDS", like:
>
> MACHINE_EXTRA_RRECOMMENDS = " kernel-modules linux-firmware-sd8686"
>
> However for poky-image-minimal, only "MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS" is
> included. If the kernel module and firmware files are indeed necessary for
> successful boot, we can add them into minimal image.
>
> Any comment on that?
>
> Thanks,
> Dongxiao
Dongxiao,
It seems that the igep machines have been moved to meta-extras now,
which is the place for machines that are being depreciated. If the bug
is just against igep then we can close this, if there is a more general
situation, then firmware files that are required to boot need to be
moved to the MACHINE_ESSENTIAL_EXTRA_RRECOMMEDS as that would be the
right place.
If you want to fix the meta-extra/igep you can add the
MACHINE_ESSENTIAL_EXTRA_RRCOOMENTS instead of MACHINE_EXTRA_RRECOMMEDS?
Sau!
prev parent reply other threads:[~2011-03-03 2:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 1:43 Could you help to have a look at BUG 660 Xu, Dongxiao
2011-03-03 2:23 ` Saul Wold [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=4D6EFBBE.5040004@intel.com \
--to=saul.wold@intel.com \
--cc=dongxiao.xu@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.