From: Saul Wold <sgw@linux.intel.com>
To: Lai Eddy <eddy.lai.tw@gmail.com>
Cc: "meta-intel@yoctoproject.org" <meta-intel@yoctoproject.org>,
Yocto Discussion <yocto@yoctoproject.org>
Subject: Re: [meta-intel] meta-intel has been split into meta-dpdk and meta-intel-qat
Date: Wed, 27 Sep 2017 23:13:29 -0700 [thread overview]
Message-ID: <1506579209.7331.26.camel@linux.intel.com> (raw)
In-Reply-To: <CACrgodfgYaFmxyD0xP5aG7nnp5RsBfJseUBqTqL9QbeO6nZf6g@mail.gmail.com>
On Thu, 2017-09-28 at 11:32 +0800, Lai Eddy wrote:
> is this mean I don't need meta-intel anymore? (but still can be found
> in the git)
> just choose to use meta-dpdk and/or meta-intel-qat
>
If you are building an Intel target, I would suggest you still use
meta-intel.
The DPDK and QAT are specificly breaking out software middleware that
might not be needed for all meta-intel MACHINES.
Sau!
> 2017-09-28 11:27 GMT+08:00 Saul Wold <sgw@linux.intel.com>:
> > In an effort to create more consistency in Yocto Project layer, we
> > are
> > splitting the meta-intel to remove some application/libraries that
> > should really be in their own layers.
> >
> > The new meta-dpdk will serve as a place for the Linux Foundation's
> > DPDK
> > project to host meta-data.
> >
> > The meta-intel-qat will carry the Quick Assist Technology libraries
> > and
> > associated applications.
> >
> > They are both hosted at https://git.yoctoproject.org
> >
> >
> > Sau!
> > --
> > _______________________________________________
> > meta-intel mailing list
> > meta-intel@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-intel
>
>
prev parent reply other threads:[~2017-09-28 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 3:27 meta-intel has been split into meta-dpdk and meta-intel-qat Saul Wold
2017-09-28 3:32 ` [meta-intel] " Lai Eddy
2017-09-28 6:13 ` 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=1506579209.7331.26.camel@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=eddy.lai.tw@gmail.com \
--cc=meta-intel@yoctoproject.org \
--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.