From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] meta-intel.inc: Enable linux-intel and 4.9 by default for meta-intel hardware
Date: Tue, 07 Feb 2017 06:45:23 -0800 [thread overview]
Message-ID: <1486478723.26702.27.camel@linux.intel.com> (raw)
In-Reply-To: <CAMKF1spjcD8X=oxK4HHeO05PxRsn_ieRoDhpA3QpNOxKLXCbtg@mail.gmail.com>
On Mon, 2017-02-06 at 13:02 -0800, Khem Raj wrote:
> On Mon, Feb 6, 2017 at 12:59 PM, Saul Wold <sgw@linux.intel.com>
> wrote:
> >
> > Enable the linux-intel production kernel for meta-intel by default
> > for 4.9,
> > this will enable using the Intel production kernel.
> >
> > This is a well tested 4.9 tree that will start to include
> > additional
> > support for the Apollolake and Joule hardware.
> >
> > Signed-off-by: Saul Wold <sgw@linux.intel.com>
> > ---
> > conf/machine/include/meta-intel.inc | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/conf/machine/include/meta-intel.inc
> > b/conf/machine/include/meta-intel.inc
> > index 21587fb..eb759c4 100644
> > --- a/conf/machine/include/meta-intel.inc
> > +++ b/conf/machine/include/meta-intel.inc
> > @@ -9,8 +9,8 @@
> > #
> >
> > # Soft set linux-yocto as preferred kernel like x86-base.inc
> > -PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto"
> > -PREFERRED_VERSION_linux-yocto ?= "4.8%"
> > +PREFERRED_PROVIDER_virtual/kernel ?= "linux-intel"
>
> whats the difference between linux-yocto and linux-intel ?
>
Sorry for sending this to the wrong list.
This is a valid question, the difference will be faster integration and
better testing /validation of upstream (or possibly pending upstream )
patches for Intel Hardware.
Since the kernel will be coming from an Intel Source, it will be fully
tested on more hardware that the current linux-yocto kernel gets tested
against.
The update rate maybe about the same, with security updates as needed
for more severe issues
As other vendors maintain kernels for their meta-vendor specific layer,
Intel has chosen to maintain an Intel kernel based on the current LTS
version (4.9) plus upstreamed patches. All content will be backports
from internally maintained tracking trees being regularly updated.
meta-intel will likely continue to contain the linux-yocto-<latest> for
a non-LTS kernel.
Hope that clarifies this.
Sau!
> >
> > +PREFERRED_VERSION_linux-intel ?= "4.9%"
> >
> > # for Xserver older than 1.13.0
> > OLD_XSERVER_X86_EXT = "xserver-xorg-extension-dri \
> > --
> > 2.7.4
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2017-02-07 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 20:59 [PATCH 1/2] iucode-tool: Add support for MUSL Saul Wold
2017-02-06 20:59 ` [PATCH] linux-intel: Add the linux-intel kernel recipe Saul Wold
2017-02-06 20:59 ` [PATCH 2/2] libva-intel-driver: Update to 1.7.3 Saul Wold
2017-02-06 20:59 ` [PATCH 2/2] meta-intel.inc: Enable linux-intel and 4.9 by default for meta-intel hardware Saul Wold
2017-02-06 21:02 ` Khem Raj
2017-02-07 14:45 ` Saul Wold [this message]
2017-02-07 16:50 ` Khem Raj
2017-02-07 17:47 ` Saul Wold
2017-02-06 21:29 ` ✗ patchtest: failure for "linux-intel: Add the linux-int..." and 1 more (rev2) Patchwork
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=1486478723.26702.27.camel@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 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.