All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 00/20] meta-intel: new chiefriver BSP and supporting recipes
Date: Wed, 23 May 2012 15:31:37 -0500	[thread overview]
Message-ID: <1337805097.32464.52.camel@elmorro> (raw)
In-Reply-To: <CADkTA4Mx2CPG1SzF63Wyx7mRL9y+fC2CUuBZ=-_GPUPXE4N-eA@mail.gmail.com>

On Wed, 2012-05-23 at 17:26 -0300, Bruce Ashfield wrote:
> On Wed, May 23, 2012 at 4:52 PM,  <tom.zanussi@intel.com> wrote:
> > From: Tom Zanussi <tom.zanussi@intel.com>
> >
> > This patchset implements a new BSP for the 'Chief River' platform, which
> > consists of the Intel Ivy Bridge processor and Panther Point PCH.  It
> > assumes that the Ivy Bridge integrated graphics are being used.
> >
> > It also adds a few new recipes related to video acceleration which are
> > modified versions of oe-core or yocto meta-demo recipes (ffmpeg,
> > yasm-native, gstreamer-vaapi), along with tweaks needed to work with
> > intel video acceleration components.
> >
> > There are also some new intel-specific video acceleration components
> > (libva-1.0.15, intel-driver-1.0.15, va-intel) either needed for video
> > acceleration on Intel platforms, or allowing for easier integration
> > with the existing meta-intel BSPs.  These finally allow the chiefriver,
> > sugarbay, and crownbay BSPs to share a common set of video components,
> > and have been tested with all three.
> >
> > Finally, there's a new recipe for the Intel Local Manageability Service
> > (LMS), which allows Intel BSPs to access the Intel Active Management
> > Technology (AMT) firmware via the Intel Management Engine Interface (MEI),
> > which is used by the Chief River BSP.
> 
> For some reason gmail dropped most of this series on me. Just so I'm sure,
> is there a board description as part of this series for the kernel
> tree ? Or is that
> still pending ?
> 

Yeah, still forthcoming - I didn't post it because you're on vacation (I
assume that's still correct).  I think Darren and I wanted to
consolidate the kernel stuff anyway, so it'll come with that...

I also may have some further tweaks as well, so for all those reasons,
don't worry about it quite yet. ;-)

Tom

> Cheers,
> 
> Bruce
> 
> >
> > The following changes since commit a62c485edffed30ea95658760948fd50925adfb0:
> >  Darren Hart (1):
> >        linux-yocto_3.0: Update KMACHINE and KBRANCH to play nice with new kerntools
> >
> > are available in the git repository at:
> >
> >  git://git.yoctoproject.org/meta-intel.git tzanussi/chiefriver.v1
> >  http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/chiefriver.v1
> >
> > Tom Zanussi (20):
> >  meta-chiefriver: new layer for Chief River (Ivy Bridge/Panther Point)
> >    systems
> >  meta-intel: add gstreamer-vaapi_git recipe
> >  meta-intel: new libva-1.0.15 recipe
> >  meta-intel: new intel-driver-1.0.15 recipe
> >  ffmpeg: new recipe
> >  ffmpeg: add --enable-vaapi
> >  ffmpeg: add --enable-gpl
> >  yasm: new recipe
> >  ffmpeg: add --enable-yasm
> >  gst-ffmpeg: add bbappend for external ffmpeg
> >  gst-va-intel: add conditional vaapi implementation
> >  va-intel: new package
> >  gst-va-intel: clarify DESCRIPTION
> >  meta-intel: remove video acceleration from emgd XSERVER
> >  meta-chiefriver: use gst-va-intel and va-intel
> >  meta-sugarbay: use gst-va-intel and va-intel
> >  meta-crownbay: use gst-va-intel and va-intel and gst-va-mixvideo
> >  lms: new recipe
> >  meta-chiefriver: use lms
> >  meta-chiefriver: use the mei kernel feature
> >
> >  .../amt/lms/atnetworktool-printf-fix.patch         |   14 +++
> >  common/recipes-bsp/amt/lms_7.1.20.bb               |   42 ++++++++
> >  common/recipes-multimedia/ffmpeg/ffmpeg.inc        |  108 ++++++++++++++++++++
> >  common/recipes-multimedia/ffmpeg/ffmpeg_0.7.12.bb  |   44 ++++++++
> >  .../gstreamer/gst-ffmpeg_0.10.13.bbappend          |    2 +
> >  .../recipes-multimedia/gstreamer/gst-va-intel.bb   |   15 +++-
> >  .../gstreamer/gstreamer-vaapi_git.bb               |   26 +++++
> >  .../libva/libva-intel-driver.inc                   |   24 +++++
> >  .../libva/libva-intel-driver_1.0.15.bb             |    8 ++
> >  common/recipes-multimedia/libva/libva_1.0.15.bb    |    8 ++
> >  common/recipes-multimedia/libva/va-intel.bb        |   20 ++++
> >  common/recipes-support/yasm/yasm_1.1.0.bb          |   17 +++
> >  conf/machine/include/ia32-base.inc                 |    4 -
> >  meta-chiefriver/COPYING.MIT                        |   17 +++
> >  meta-chiefriver/README                             |  107 +++++++++++++++++++
> >  meta-chiefriver/README.sources                     |   17 +++
> >  meta-chiefriver/conf/layer.conf                    |   10 ++
> >  meta-chiefriver/conf/machine/chiefriver.conf       |   19 ++++
> >  .../formfactor/formfactor/chiefriver/machconfig    |    3 +
> >  .../recipes-bsp/formfactor/formfactor_0.0.bbappend |    3 +
> >  .../tasks/task-core-tools-profile.bbappend         |    2 +
> >  .../xserver-xf86-config/chiefriver/xorg.conf       |   26 +++++
> >  .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |    3 +
> >  .../linux/linux-yocto-rt_3.2.bbappend              |    8 ++
> >  .../recipes-kernel/linux/linux-yocto_3.2.bbappend  |   10 ++
> >  meta-crownbay/conf/machine/crownbay.conf           |    6 +-
> >  meta-sugarbay/conf/machine/sugarbay.conf           |    4 +
> >  27 files changed, 561 insertions(+), 6 deletions(-)
> >  create mode 100644 common/recipes-bsp/amt/lms/atnetworktool-printf-fix.patch
> >  create mode 100644 common/recipes-bsp/amt/lms_7.1.20.bb
> >  create mode 100644 common/recipes-multimedia/ffmpeg/ffmpeg.inc
> >  create mode 100644 common/recipes-multimedia/ffmpeg/ffmpeg_0.7.12.bb
> >  create mode 100644 common/recipes-multimedia/gstreamer/gst-ffmpeg_0.10.13.bbappend
> >  create mode 100644 common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb
> >  create mode 100644 common/recipes-multimedia/libva/libva-intel-driver.inc
> >  create mode 100644 common/recipes-multimedia/libva/libva-intel-driver_1.0.15.bb
> >  create mode 100644 common/recipes-multimedia/libva/libva_1.0.15.bb
> >  create mode 100644 common/recipes-multimedia/libva/va-intel.bb
> >  create mode 100644 common/recipes-support/yasm/yasm_1.1.0.bb
> >  create mode 100644 meta-chiefriver/COPYING.MIT
> >  create mode 100644 meta-chiefriver/README
> >  create mode 100644 meta-chiefriver/README.sources
> >  create mode 100644 meta-chiefriver/conf/layer.conf
> >  create mode 100644 meta-chiefriver/conf/machine/chiefriver.conf
> >  create mode 100644 meta-chiefriver/recipes-bsp/formfactor/formfactor/chiefriver/machconfig
> >  create mode 100644 meta-chiefriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
> >  create mode 100644 meta-chiefriver/recipes-core/tasks/task-core-tools-profile.bbappend
> >  create mode 100644 meta-chiefriver/recipes-graphics/xorg-xserver/xserver-xf86-config/chiefriver/xorg.conf
> >  create mode 100644 meta-chiefriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
> >  create mode 100644 meta-chiefriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
> >  create mode 100644 meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
> >
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> 
> 
> 




  reply	other threads:[~2012-05-23 20:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 19:52 [PATCH 00/20] meta-intel: new chiefriver BSP and supporting recipes tom.zanussi
2012-05-23 19:52 ` [PATCH 01/20] meta-chiefriver: new layer for Chief River (Ivy Bridge/Panther Point) systems tom.zanussi
2012-05-23 19:52 ` [PATCH 02/20] meta-intel: add gstreamer-vaapi_git recipe tom.zanussi
2012-05-23 19:52 ` [PATCH 03/20] meta-intel: new libva-1.0.15 recipe tom.zanussi
2012-05-23 19:52 ` [PATCH 04/20] meta-intel: new intel-driver-1.0.15 recipe tom.zanussi
2012-05-23 19:52 ` [PATCH 05/20] ffmpeg: new recipe tom.zanussi
2012-05-23 19:52 ` [PATCH 06/20] ffmpeg: add --enable-vaapi tom.zanussi
2012-05-23 19:52 ` [PATCH 07/20] ffmpeg: add --enable-gpl tom.zanussi
2012-05-23 19:52 ` [PATCH 08/20] yasm: new recipe tom.zanussi
2012-05-23 19:52 ` [PATCH 09/20] ffmpeg: add --enable-yasm tom.zanussi
2012-05-23 19:52 ` [PATCH 10/20] gst-ffmpeg: add bbappend for external ffmpeg tom.zanussi
2012-05-23 19:52 ` [PATCH 11/20] gst-va-intel: add conditional vaapi implementation tom.zanussi
2012-05-23 19:52 ` [PATCH 12/20] va-intel: new package tom.zanussi
2012-05-23 19:52 ` [PATCH 13/20] gst-va-intel: clarify DESCRIPTION tom.zanussi
2012-05-23 19:52 ` [PATCH 14/20] meta-intel: remove video acceleration from emgd XSERVER tom.zanussi
2012-05-23 19:52 ` [PATCH 15/20] meta-chiefriver: use gst-va-intel and va-intel tom.zanussi
2012-05-23 19:52 ` [PATCH 16/20] meta-sugarbay: " tom.zanussi
2012-05-23 19:52 ` [PATCH 17/20] meta-crownbay: use gst-va-intel and va-intel and gst-va-mixvideo tom.zanussi
2012-05-23 19:52 ` [PATCH 18/20] lms: new recipe tom.zanussi
2012-05-23 19:52 ` [PATCH 19/20] meta-chiefriver: use lms tom.zanussi
2012-05-23 19:52 ` [PATCH 20/20] meta-chiefriver: use the mei kernel feature tom.zanussi
2012-05-23 20:26 ` [PATCH 00/20] meta-intel: new chiefriver BSP and supporting recipes Bruce Ashfield
2012-05-23 20:31   ` Tom Zanussi [this message]
2012-05-23 20:47     ` Bruce Ashfield

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=1337805097.32464.52.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=bruce.ashfield@gmail.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.