[meta-intel] [PATCH V2 0/3] meta-intel/common: Upgrade DPDK to v1.7.0

2014-09-17 Thread sreeju . armughanx . selvaraj 
From: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com

Hi All,


This series of patches consists below:

1. Upgraded the DPDK to the latest version v1.7.0

2. Added an include file based on the recipe for dpdk_1.6.0r2

3. Cherry picked patches to fix the test case failure of example app
ring_pmd_autotest

4. Cherry picked patch to fix the installation failure of example app
ip_pipeline

5. Added MACHINE_EXTRA_RRECOMMENDS to enable DPDK by default for Romley.

---
Version 2 Changes:

PATCH V2 1/3:
* No changes.

PATCH V2 2/3:
* As suggested by Ross, removed the patch which hard coded to exclude the
compilation of dpdk_qat and vhost, Instead of that added enable / disable
mechanism for dependancies qat and fuse using PACKAGECONFIG.

* Also added the config variables for example app dpdk_qat and vhost.
It can be set to enable or disable based on PACKAGECONFIG content.

PATCH V2 3/3:
* No changes


Please review the patch and help to merge in to meta-intel:master and
meta-intel:daisy

Thanks and Regards,
Sreeju

The following changes since commit 174f6c90d1fdc87b6d0ed846902b1b63d6c79dc5:

  meta-crystalforest: Update README with new build settings (2014-08-27 
15:37:02 -0500)

are available in the git repository at:

  git://git.yoctoproject.org/meta-intel-contrib sreeju/daisy/intel-bsp-common
  
http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=sreeju/daisy/intel-bsp-common

Sreeju Selvaraj (3):
  meta-intel/common: Add include file for DPDK
  meta-inte/common: Upgrade DPDK to v1.7.0
  meta-romley: DPDK v1.7.0 support for Romley machine config

 common/recipes-extended/dpdk/dpdk.inc  | 139 
 ...d-config-variables-to-enable-disable-dpdk.patch |  40 +++
 ...examples-pipeline-build-with-all-examples.patch |  33 ++
 ...e-extra-devices-creation-with-vdev-option.patch |  43 +++
 .../dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch | 379 +
 common/recipes-extended/dpdk/dpdk_1.6.0r2.bb   | 150 +---
 common/recipes-extended/dpdk/dpdk_1.7.0.bb |  41 +++
 meta-romley/conf/machine/romley-ivb.conf   |   4
 meta-romley/conf/machine/romley.conf   |   5
 9 files changed, 699 insertions(+), 135 deletions(-)
 create mode 100644 common/recipes-extended/dpdk/dpdk.inc
 create mode 100644 
common/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-Add-config-variables-to-enable-disable-dpdk.patch
 create mode 100644 
common/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-pipeline-build-with-all-examples.patch
 create mode 100644 
common/recipes-extended/dpdk/dpdk/dpdk-1.7.0-ring-remove-extra-devices-creation-with-vdev-option.patch
 create mode 100644 
common/recipes-extended/dpdk/dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch
 create mode 100644 common/recipes-extended/dpdk/dpdk_1.7.0.bb

-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [PATCH V2 1/3] meta-intel/common: Add include file for DPDK

2014-09-17 Thread sreeju . armughanx . selvaraj 
From: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com

Added include file dpdk.inc to share the common functionality
based on dpdk_1.6.0r2

Added a new variable EXAMPLE_BUILD_DIR. this points to apps build
directory which is different in dpdk v1.6.0r2 and v1.7.0.
User of dpdk.inc has to define EXAMPLE_BUILD_DIR for the
installation of example apps

Signed-off-by: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com
---
 common/recipes-extended/dpdk/dpdk.inc| 139 +
 common/recipes-extended/dpdk/dpdk_1.6.0r2.bb | 150 +++
 2 files changed, 154 insertions(+), 135 deletions(-)
 create mode 100644 common/recipes-extended/dpdk/dpdk.inc

diff --git a/common/recipes-extended/dpdk/dpdk.inc 
b/common/recipes-extended/dpdk/dpdk.inc
new file mode 100644
index 000..ef369df
--- /dev/null
+++ b/common/recipes-extended/dpdk/dpdk.inc
@@ -0,0 +1,139 @@
+DESCRIPTION = Intel(r) Data Plane Development Kit
+HOMEPAGE = http://dpdk.org;
+LICENSE = BSD  LGPLv2  GPLv2
+LIC_FILES_CHKSUM = file://LICENSE.GPL;md5=751419260aa954499f7abaabaa882bbe
+
+
+RDEPENDS_${PN} += python-subprocess
+
+inherit module
+
+export MODULE_DIR=/lib/modules/${KERNEL_VERSION}/kernel/drivers/net
+export RTE_SDK = ${S}
+export RTE_TARGET=${TARGET_ARCH}-ivshmem-${TARGET_OS}app-gcc
+export ICP_ROOT = ${PKG_CONFIG_SYSROOT_DIR}/usr/include
+export ICP_LIB_ROOT= ${PKG_CONFIG_SYSROOT_DIR}/usr/lib
+export RTE_KERNELDIR = ${STAGING_KERNEL_DIR}
+export INSTALL_PATH = ${prefix}/dpdk
+
+
+do_configure () {
+   #
+   ### default value for prefix is usr, unsetting it, so it
+   ### will not be concatenated in ${RTE_TARGET}/Makefile
+   ### which will cause compilation failure
+   #
+   unset prefix
+
+   make O=$RTE_TARGET T=$RTE_TARGET config
+
+}
+
+
+do_compile () {
+   unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
+
+   cd ${S}/${RTE_TARGET}
+   oe_runmake EXTRA_LDFLAGS= --sysroot=${STAGING_DIR_HOST} \
+  EXTRA_CFLAGS= --sysroot=${STAGING_DIR_HOST} \
+  CROSS=${TARGET_PREFIX} \
+  prefix=  LDFLAGS=  WERROR_FLAGS=-w V=1
+
+}
+
+
+do_install () {
+
+   install -m 0755 -d  ${D}/${INSTALL_PATH} \
+   ${D}/${INSTALL_PATH}/doc \
+   ${D}/${INSTALL_PATH}/tools \
+   ${D}/${INSTALL_PATH}/${RTE_TARGET} \
+   ${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
+   ${D}${includedir} \
+   ${D}${includedir}/arch \
+   ${D}${includedir}/exec-env \
+   ${D}${libdir} \
+   ${D}${MODULE_DIR}
+
+   install -m 0755 ${S}/${RTE_TARGET}/kmod/igb_uio.ko  
${D}${MODULE_DIR}/
+   install -m 0755 ${S}/${RTE_TARGET}/kmod/rte_kni.ko  
${D}${MODULE_DIR}/
+
+   install -m 640 ${S}/${RTE_TARGET}/lib/*.a   ${D}${libdir}
+
+   install -m 640 ${S}/${RTE_TARGET}/.config   
${D}/${INSTALL_PATH}/${RTE_TARGET}/
+   install -m 640 ${S}/${RTE_TARGET}/include/*.h   
${D}${includedir}/
+   install -m 640 ${S}/${RTE_TARGET}/include/arch/*
${D}${includedir}/arch/
+   install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*
${D}${includedir}/exec-env/
+   install -m 0755 ${S}/tools/*.py 
${D}/${INSTALL_PATH}/tools/
+
+
+   #Install test applications
+   install -m 0755 ${S}/${RTE_TARGET}/app/test 
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+   install -m 0755 ${S}/${RTE_TARGET}/app/testpmd  
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+   install -m 0755 ${S}/${RTE_TARGET}/app/dump_cfg 
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+   install -m 0755 ${S}/${RTE_TARGET}/app/cmdline_test 
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+
+
+   # Install example applications
+   # It is expected that user of this include file should define 
EXAMPLES_BUILD_DIR
+   for app in ${S}/examples/*
+   do
+   case `basename ${app}` in
+   dpdk_qat | vhost | vhost_xen | Makefile ) continue
+   ;;
+   l2fwd-ivshmem)
+   install -m 0755 ${app}/guest/${EXAMPLES_BUILD_DIR}/app/guest
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+   install -m 0755 ${app}/host/${EXAMPLES_BUILD_DIR}/app/host  
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+   continue
+   ;;
+   multi_process)
+   install -m 0755 
${app}/client_server_mp/mp_client/${EXAMPLES_BUILD_DIR}/app/mp_client   
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+   install -m 0755 
${app}/client_server_mp/mp_server/${EXAMPLES_BUILD_DIR}/app/mp_server

[meta-intel] [PATCH V2 3/3] meta-romley: DPDK v1.7.0 support for Romley machine config

2014-09-17 Thread sreeju . armughanx . selvaraj 
From: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com

Added MACHINE_EXTRA_RRECOMMENDS to include dpdk v1.7.0 support
for romley machiine, so that dpdk will be enabled by default
for Romley. Also included the dpdk example package, so that
user can use example apps to exercise the DPDK libraries.

Signed-off-by: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com
---
 meta-romley/conf/machine/romley-ivb.conf | 4 
 meta-romley/conf/machine/romley.conf | 5 +
 2 files changed, 9 insertions(+)

diff --git a/meta-romley/conf/machine/romley-ivb.conf 
b/meta-romley/conf/machine/romley-ivb.conf
index af52897..e130068 100644
--- a/meta-romley/conf/machine/romley-ivb.conf
+++ b/meta-romley/conf/machine/romley-ivb.conf
@@ -18,3 +18,7 @@ XSERVER ?= ${XSERVER_X86_BASE} \
${XSERVER_X86_EXT} \
   ${XSERVER_X86_MATROX_MGA} \

+PREFERRED_VERSION_dpdk ?= 1.7.0%
+MACHINE_EXTRA_RRECOMMENDS += dpdk \
+ dpdk-examples \
+ 
diff --git a/meta-romley/conf/machine/romley.conf 
b/meta-romley/conf/machine/romley.conf
index ed52a1e..a814fc3 100644
--- a/meta-romley/conf/machine/romley.conf
+++ b/meta-romley/conf/machine/romley.conf
@@ -18,3 +18,8 @@ XSERVER ?= ${XSERVER_X86_BASE} \
${XSERVER_X86_EXT} \
   ${XSERVER_X86_MATROX_MGA} \

+PREFERRED_VERSION_dpdk ?= 1.7.0%
+MACHINE_EXTRA_RRECOMMENDS += dpdk \
+ dpdk-examples \
+ 
+
-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH V2 3/3] meta-romley: DPDK v1.7.0 support for Romley machine config

2014-09-17 Thread Kamble, Nitin A 
Hi Sreeju,

Aren¹t there other BSPs such as crystalforest which can utilize the DPDK
feature?

Nitin


On 9/17/14, 7:20 AM, sreeju.armughanx.selva...@intel.com
sreeju.armughanx.selva...@intel.com wrote:

From: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com

Added MACHINE_EXTRA_RRECOMMENDS to include dpdk v1.7.0 support
for romley machiine, so that dpdk will be enabled by default
for Romley. Also included the dpdk example package, so that
user can use example apps to exercise the DPDK libraries.

Signed-off-by: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com
---
 meta-romley/conf/machine/romley-ivb.conf | 4 
 meta-romley/conf/machine/romley.conf | 5 +
 2 files changed, 9 insertions(+)

diff --git a/meta-romley/conf/machine/romley-ivb.conf
b/meta-romley/conf/machine/romley-ivb.conf
index af52897..e130068 100644
--- a/meta-romley/conf/machine/romley-ivb.conf
+++ b/meta-romley/conf/machine/romley-ivb.conf
@@ -18,3 +18,7 @@ XSERVER ?= ${XSERVER_X86_BASE} \
${XSERVER_X86_EXT} \
  ${XSERVER_X86_MATROX_MGA} \

+PREFERRED_VERSION_dpdk ?= 1.7.0%
+MACHINE_EXTRA_RRECOMMENDS += dpdk \
+dpdk-examples \
+
diff --git a/meta-romley/conf/machine/romley.conf
b/meta-romley/conf/machine/romley.conf
index ed52a1e..a814fc3 100644
--- a/meta-romley/conf/machine/romley.conf
+++ b/meta-romley/conf/machine/romley.conf
@@ -18,3 +18,8 @@ XSERVER ?= ${XSERVER_X86_BASE} \
${XSERVER_X86_EXT} \
  ${XSERVER_X86_MATROX_MGA} \

+PREFERRED_VERSION_dpdk ?= 1.7.0%
+MACHINE_EXTRA_RRECOMMENDS += dpdk \
+dpdk-examples \
+
+
-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH V2 3/3] meta-romley: DPDK v1.7.0 support for Romley machine config

2014-09-17 Thread Burton, Ross 
On 17 September 2014 15:20,  sreeju.armughanx.selva...@intel.com wrote:
 Added MACHINE_EXTRA_RRECOMMENDS to include dpdk v1.7.0 support
 for romley machiine, so that dpdk will be enabled by default
 for Romley. Also included the dpdk example package, so that
 user can use example apps to exercise the DPDK libraries.

I went through this with the guy who submitted the 1.7 recipes.

On their own, the DPDK packages are useless as the user needs to
compile their application with them.  What you're basically doing is
forcing a library onto *every* image for that machine, even ones that
don't want to use DPDK.  Please don't do that.

Ross
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 0/5] Commits for retirement of EMGD based BSPs

2014-09-17 Thread Tom Zanussi 
On Fri, 2014-09-05 at 19:46 -0700, nitin.a.kam...@intel.com wrote:
 From: Nitin A Kamble nitin.a.kam...@intel.com
 
 These commits remove the proprietary EMGD based BSPs and all the supporti
 needed for these from the meta-intel layer.
 

Pulled into meta-intel/master.

 Thanks,
 Nitin
 
 The following changes since commit 50abd223b626fc7508e24b55fc1b22c7b3a66e97:
 
   meta-intel BSPs: enable microcode loading support for images (2014-09-04 
 08:46:42 -0500)
 
 are available in the git repository at:
 
   git://git.yoctoproject.org/meta-intel-contrib nitin/misc
   http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/misc
 
 Nitin A Kamble (5):
   Remove emenlow machine support
   Remove crownbay machine support
   Remove fri2 machine support
   Remove all the changes related to the proprietary EMGD graphics driver
   Remove the xserver-xorg-1.9.3 recipe and it's files
 
  classes/emgd-gl.bbclass|  11 -
  .../Intel-software-license-emgd-1.14   |  42 --
  .../Intel-software-license-emgd-1.16   |  42 --
  .../Intel-software-license-emgd-1.18   |  42 --
  ...-space-graphics-driver-binary-license-emgd-1.14 | 559 
 -
  ...-space-graphics-driver-binary-license-emgd-1.16 | 559 
 -
  ...-space-graphics-driver-binary-license-emgd-1.18 | 559 
 -
  .../xorg-driver/emgd-driver-bin/egl.pc |  12 -
  .../xorg-driver/emgd-driver-bin/glchar.patch   |  17 -
  .../xorg-driver/emgd-driver-bin/gles_cm.pc |  12 -
  .../xorg-driver/emgd-driver-bin/glesv2.pc  |  12 -
  .../xorg-driver/emgd-driver-bin_1.16.bb| 186 ---
  .../xorg-driver/emgd-driver-bin_1.18.bb| 188 ---
  .../xorg-xserver/xserver-xorg-1.9.3.inc|  20 -
  .../xserver-xorg-1.9.3/crosscompile.patch  |  22 -
  .../fix_open_max_preprocessor_error.patch  |  15 -
  .../xserver-xorg-1.9.3/macro_tweak.patch   |  30 --
  .../xorg-xserver/xserver-xorg-1.9.3/nodolt.patch   |  14 -
  .../xserver-xorg-1.9.3/ptr-to-int-cast-fix.patch   |  92 
  .../xserver-xorg-1.9.3/werror-address-fix.patch|  49 --
  .../xorg-xserver/xserver-xorg_1.9.3.bb |   4 -
  .../recipes-multimedia/gstreamer/gst-va-intel.bb   |   9 -
  common/recipes-multimedia/libva/va-intel.bb|   3 -
  conf/machine/include/meta-intel-emgd.inc   |   9 -
  conf/machine/include/meta-intel.inc|   4 -
  meta-crownbay/README   |  51 +-
  meta-crownbay/conf/machine/crownbay.conf   |  32 --
  .../formfactor/formfactor/crownbay/machconfig  |   3 -
  .../xserver-xf86-config/crownbay/xorg.conf |  43 --
  .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |   3 -
  .../recipes-kernel/linux/linux-yocto_3.10.bbappend |  12 -
  meta-emenlow/README|  49 +-
  meta-emenlow/conf/machine/emenlow.conf |  32 --
  .../formfactor/formfactor/emenlow/machconfig   |   3 -
  .../xserver-xf86-config/emenlow/xorg.conf  |  43 --
  .../recipes-kernel/linux/linux-yocto_3.10.bbappend |  13 -
  meta-fri2/README   |  51 +-
  meta-fri2/conf/machine/fri2.conf   |  47 --
  .../alsa-state/alsa-state/fri2/asound.state| 411 ---
  .../formfactor/formfactor/fri2/machconfig  |   3 -
  .../init-ifupdown/files/fri2/interfaces|   9 -
  .../xserver-xf86-config/fri2/xorg.conf |  60 ---
  .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |   1 -
  .../linux/linux-yocto-rt_3.10.bbappend |   7 -
  .../linux/linux-yocto-tiny_3.10.bbappend   |   8 -
  .../recipes-kernel/linux/linux-yocto_3.10.bbappend |  11 -
  46 files changed, 18 insertions(+), 3386 deletions(-)
  delete mode 100644 classes/emgd-gl.bbclass
  delete mode 100644 common/custom-licenses/Intel-software-license-emgd-1.14
  delete mode 100644 common/custom-licenses/Intel-software-license-emgd-1.16
  delete mode 100644 common/custom-licenses/Intel-software-license-emgd-1.18
  delete mode 100644 
 common/custom-licenses/Intel-user-space-graphics-driver-binary-license-emgd-1.14
  delete mode 100644 
 common/custom-licenses/Intel-user-space-graphics-driver-binary-license-emgd-1.16
  delete mode 100644 
 common/custom-licenses/Intel-user-space-graphics-driver-binary-license-emgd-1.18
  delete mode 100644 common/recipes-graphics/xorg-driver/emgd-driver-bin/egl.pc
  delete mode 100644 
 common/recipes-graphics/xorg-driver/emgd-driver-bin/glchar.patch
  delete mode 100644 
 common/recipes-graphics/xorg-driver/emgd-driver-bin/gles_cm.pc
  delete mode 100644 
 common/recipes-graphics/xorg-driver/emgd-driver-bin/glesv2.pc
  delete mode 100644 
 common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb
  delete mode 100644 
 common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb
  delete mode 100644

[meta-intel] [PATCH 1/2] intel-corei7-64.conf: include the AMT daemon in the images

2014-09-17 Thread nitin . a . kamble 
From: Nitin A Kamble nitin.a.kam...@intel.com

Some of the platforms supported by the intel-corei7-64 BSP have AMT feature
on the platform. Enable it so that it can get utilized with this BSP.

Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com
---
 conf/machine/intel-corei7-64.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/intel-corei7-64.conf 
b/conf/machine/intel-corei7-64.conf
index c3b08bc..97d57b3 100644
--- a/conf/machine/intel-corei7-64.conf
+++ b/conf/machine/intel-corei7-64.conf
@@ -16,7 +16,7 @@ MACHINE_FEATURES += wifi 3g
 
 MACHINE_HWCODECS ?= va-intel gst-va-intel
 
-MACHINE_EXTRA_RRECOMMENDS += linux-firmware
+MACHINE_EXTRA_RRECOMMENDS += linux-firmware lms8
 
 XSERVER ?= ${XSERVER_X86_BASE} \
 ${XSERVER_X86_EXT} \
-- 
1.8.1.4

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 2/2] meta-intel.inc: allow disabling of Intel microcode

2014-09-17 Thread Burton, Ross 
On 17 September 2014 20:44,  nitin.a.kam...@intel.com wrote:
 As per request from Tom, allow disabling of the Intel microcode
 feature for meta-intel BSPs.

 If one adds this line to local.conf while build a meta-intel BSP,
 the microcode feature will be disabled for the build target.

 DISABLE_INTEL_MICROCODE = 1

I agree with Tom here - microcode should be opt-in at the machine level.

Ross
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 2/2] meta-intel.inc: allow disabling of Intel microcode

2014-09-17 Thread Kamble, Nitin A 
Tom,
  There is an issue with this commit. I will send another commit for this
purpose.

Thanks,
Nitin


On 9/17/14, 12:44 PM, Kamble, Nitin A nitin.a.kam...@intel.com wrote:

From: Nitin A Kamble nitin.a.kam...@intel.com

As per request from Tom, allow disabling of the Intel microcode
feature for meta-intel BSPs.

If one adds this line to local.conf while build a meta-intel BSP,
the microcode feature will be disabled for the build target.

DISABLE_INTEL_MICROCODE = 1

Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com
---
 conf/machine/include/meta-intel.inc | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/conf/machine/include/meta-intel.inc
b/conf/machine/include/meta-intel.inc
index f43903e..e8134a7 100644
--- a/conf/machine/include/meta-intel.inc
+++ b/conf/machine/include/meta-intel.inc
@@ -20,10 +20,11 @@ XSERVER_X86_MATROX_MGA = xf86-video-mga \
 
 XSERVER_X86_ASPEED_AST = xf86-video-ast \

-
+# if not disabled,
 # include the user space intel microcode loading support in the
generated images.
-MACHINE_ESSENTIAL_EXTRA_RDEPENDS_append =  intel-microcode iucode-tool
+MACHINE_ESSENTIAL_EXTRA_RDEPENDS_append = ${@[' intel-microcode
iucode-tool', ''][d.getVar('DISABLE_INTEL_MICROCODE', True) != '1']}
 
-# For the early boot time kernel microcode loading support,
+# if not disabled,
+# for the early boot time kernel microcode loading support,
 # merge the microcode data in the final initrd image.
-INITRD_prepend = ${DEPLOY_DIR_IMAGE}/microcode.cpio 
+INITRD_prepend = ${@['${DEPLOY_DIR_IMAGE}/microcode.cpio ',
''][d.getVar('DISABLE_INTEL_MICROCODE', True) != '1']}
-- 
1.8.1.4


-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 2/2] meta-intel.inc: allow disabling of Intel microcode

2014-09-17 Thread Kamble, Nitin A 


I agree with Tom here - microcode should be opt-in at the machine level.

Ross

Then it can be implemented as a MACHINE_FEATURE. Tom¹s need is bit
different though. He want it kind of a distro feature, so that poky-tiny
will not pick it up.

Nitin



-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] (no subject)

2014-09-17 Thread Burton, Ross 
On 16 September 2014 12:35, Stuart Weaver stuart.wea...@datapath.co.uk wrote:
 I've just made a fresh Yocto/meta-intel repository and created an image based
 on core-image-sato for valleyisland-32.

What release or git revision of poky/yocto/oe-core are you using?  The
microcode support in git master of meta-intel needs some changes that
were made to oe-core master, so if you're using a release of Poky (or
oe-core) but git master of meta-intel then this is the sort of failure
I'd expect to see.

If you're stuck with a release of oe-core/poky then use the
corresponding branch in meta-intel, and cherry-pick anything that you
need from master.

Ross
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 2/2] meta-intel.inc: allow disabling of Intel microcode

2014-09-17 Thread Hart, Darren 
On 9/17/14, 13:23, Kamble, Nitin A nitin.a.kam...@intel.com wrote:



No, we had this discussion. These BSPs need to build out of the box
without special flags to disable feature that would otherwise break it on
supported systems. If Microcode can't be enabled generically and safely,
then it needs to be opt-in, not opt-out.

--
Darren
We discussed this a bit on jabber. The new proposal is to make it a
MACHINE_FEATURE and add it to all the machine .conf files from meta-intel.

The problem with this of course is we can't use it easily with the common
BSPs and ultimately we want to eliminate as many of the other BSPs as
possible.

What is the exact issue with microcode? How does it break certain systems
when enabled on the intel common BSPs?


-- 
Darren Hart Open Source Technology Center
darren.h...@intel.com   Intel Corporation


-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 2/2] meta-intel.inc: allow disabling of Intel microcode

2014-09-17 Thread Kamble, Nitin A 



The problem with this of course is we can't use it easily with the common
BSPs and ultimately we want to eliminate as many of the other BSPs as
possible.

What is the exact issue with microcode? How does it break certain systems
when enabled on the intel common BSPs?

1st there is no boot issue related to microcode. What was reported is a
build issue. His initrd file was not built correctly. And we believe that
it happened because he used older version of poky/oecore. So that is
turning out to be a build setup issue.

Here are the updates on the bug:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6730


Nitin

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] (no subject)

2014-09-17 Thread Tom Zanussi 
On Tue, 2014-09-16 at 09:27 -0500, Tom Zanussi wrote:
 On Tue, 2014-09-16 at 11:35 +, Stuart Weaver wrote:
  Hi all,
  
  I've just made a fresh Yocto/meta-intel repository and created an
  image based on core-image-sato for valleyisland-32. However when
  booting, the kernel was panicking as it could not load /initrd.
  Looking at the image created I found that initrd was not being
  included. After comparing with an older version of the repositories I
  had, I found that commenting out the following lines in
  meta-intel/conf/machine/include/meta-intel.inc solved the issue:
  
  # include the user space intel microcode loading support in the
  generated images.
  # MACHINE_ESSENTIAL_EXTRA_RDEPENDS_append =  intel-microcode
  iucode-tool
  
  # For the early boot time kernel microcode loading support,
  # merge the microcode data in the final initrd image.
  # INITRD_prepend = ${DEPLOY_DIR_IMAGE}/microcode.cpio 
  
  I don't know anything bout intel microcode, and hence would it be
  possible to explain/point me to some place that has more information
  about the microcode and how to configure it to create the initrd
  correctly?
  
 Hi,
 
 This shouldn't be your problem - the recent microcode commits are to
 blame.  I pulled them in on the condition that there would be an opt-out

Sorry, my bad, the microcode commits probably aren't to blame, looks
like it was just a case of using a stale poky, as noticed by Ross and
mentioned by Nitin in the bug.  Please try the suggestions in the bug.

Tom

 mechanism available asap.  If this can happen on a per-machine basis, it
 should actually be an opt-in only feature.
 
 I've just filed a bug for this:
 
 https://bugzilla.yoctoproject.org/show_bug.cgi?id=6730
 
 If this isn't just a case of a simple bug, I'll revert the patchset.
 
 
 Thanks,
 
 Tom
 
  Best Regards,
  Stuart
  
  
  __
  This email has been scanned by the Symantec Email Security.cloud
  service.
  For more information please visit http://www.symanteccloud.com
  __
 
 


-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 1/2] intel-corei7-64.conf: include the AMT daemon in the images

2014-09-17 Thread Kamble, Nitin A 


On 9/17/14, 12:58 PM, Hart, Darren darren.h...@intel.com wrote:

On 9/17/14, 12:44, Kamble, Nitin A nitin.a.kam...@intel.com wrote:

From: Nitin A Kamble nitin.a.kam...@intel.com

Some of the platforms supported by the intel-corei7-64 BSP have AMT
feature
on the platform. Enable it so that it can get utilized with this BSP.

How does this impact boot of systems without AMT support? 32 and 64 bit?

This change just adds the AMT module to the images. It would not affect
booting unless a system has broken AMT firmware. In that case the
machine-setup-tool configuration can be used to blacklist the mei kernel
driver.

Nitin



Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com
---
 conf/machine/intel-corei7-64.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/intel-corei7-64.conf
b/conf/machine/intel-corei7-64.conf
index c3b08bc..97d57b3 100644
--- a/conf/machine/intel-corei7-64.conf
+++ b/conf/machine/intel-corei7-64.conf
@@ -16,7 +16,7 @@ MACHINE_FEATURES += wifi 3g
 
 MACHINE_HWCODECS ?= va-intel gst-va-intel
 
-MACHINE_EXTRA_RRECOMMENDS += linux-firmware
+MACHINE_EXTRA_RRECOMMENDS += linux-firmware lms8
 
 XSERVER ?= ${XSERVER_X86_BASE} \
 ${XSERVER_X86_EXT} \
-- 
1.8.1.4




-- 
Darren HartOpen Source Technology Center
darren.h...@intel.com  Intel Corporation



-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH V2 3/3] meta-romley: DPDK v1.7.0 support for Romley machine config

2014-09-17 Thread Selvaraj, Sreeju ArmughanX 
Hi Nitin,

Yes, it can be utilized in  crystalforest, highlandforest and mohonpeak.

Thanks and Regards,
-Sreeju

-Original Message-
From: Kamble, Nitin A 
Sent: Thursday, September 18, 2014 12:04 AM
To: Selvaraj, Sreeju ArmughanX; meta-intel@yoctoproject.org
Subject: Re: [meta-intel] [PATCH V2 3/3] meta-romley: DPDK v1.7.0 support for 
Romley machine config

Hi Sreeju,

Aren¹t there other BSPs such as crystalforest which can utilize the DPDK 
feature?

Nitin


On 9/17/14, 7:20 AM, sreeju.armughanx.selva...@intel.com
sreeju.armughanx.selva...@intel.com wrote:

From: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com

Added MACHINE_EXTRA_RRECOMMENDS to include dpdk v1.7.0 support for 
romley machiine, so that dpdk will be enabled by default for Romley. 
Also included the dpdk example package, so that user can use example 
apps to exercise the DPDK libraries.

Signed-off-by: Sreeju Selvaraj sreeju.armughanx.selva...@intel.com
---
 meta-romley/conf/machine/romley-ivb.conf | 4 
 meta-romley/conf/machine/romley.conf | 5 +
 2 files changed, 9 insertions(+)

diff --git a/meta-romley/conf/machine/romley-ivb.conf
b/meta-romley/conf/machine/romley-ivb.conf
index af52897..e130068 100644
--- a/meta-romley/conf/machine/romley-ivb.conf
+++ b/meta-romley/conf/machine/romley-ivb.conf
@@ -18,3 +18,7 @@ XSERVER ?= ${XSERVER_X86_BASE} \
${XSERVER_X86_EXT} \
  ${XSERVER_X86_MATROX_MGA} \

+PREFERRED_VERSION_dpdk ?= 1.7.0%
+MACHINE_EXTRA_RRECOMMENDS += dpdk \
+dpdk-examples \
+
diff --git a/meta-romley/conf/machine/romley.conf
b/meta-romley/conf/machine/romley.conf
index ed52a1e..a814fc3 100644
--- a/meta-romley/conf/machine/romley.conf
+++ b/meta-romley/conf/machine/romley.conf
@@ -18,3 +18,8 @@ XSERVER ?= ${XSERVER_X86_BASE} \
${XSERVER_X86_EXT} \
  ${XSERVER_X86_MATROX_MGA} \

+PREFERRED_VERSION_dpdk ?= 1.7.0%
+MACHINE_EXTRA_RRECOMMENDS += dpdk \
+dpdk-examples \
+
+
--
1.9.1

--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH V2 3/3] meta-romley: DPDK v1.7.0 support for Romley machine config

2014-09-17 Thread Ong, Boon Leong 
 On their own, the DPDK packages are useless as the user needs to compile
 their application with them.  What you're basically doing is forcing a 
 library onto
 *every* image for that machine, even ones that don't want to use DPDK.
 Please don't do that.

So, reading from your feedback, I think that you are suggesting to create 
bbappend file for each of the target image type
(core-image-sato  core-image-sato-sdk) with IMAGE_INSTALL += dpdk 
dpdk-examples ... 
Just want to be sure we get your idea correctly.

These are the two images that CID customers are using from Yocto Project. 

Thanks


 
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel