Date   

[PATCHv4 4/8] fishriver BSP retirement

nitin.a.kamble@...
 

From: Nitin A Kamble <nitin.a.kamble@...>

This commit removes fishriver bsp from meta-intel layer.

Fish-River-Island-2 hardware and BSP has made this
Fish-River-Island hardware and BSP obsolete.
Also we discussed this on the Yocto Execution Tracking Meeting,
and to our knowledge no customer is using (cares about) this BSP now.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@...>
---
MAINTAINERS | 4 -
meta-fishriver/COPYING.MIT | 17 ---
meta-fishriver/README | 114 --------------------
meta-fishriver/README.sources | 17 ---
meta-fishriver/conf/layer.conf | 12 --
meta-fishriver/conf/machine/fishriver.conf | 17 ---
.../formfactor/formfactor/fishriver/machconfig | 3 -
.../recipes-bsp/formfactor/formfactor_0.0.bbappend | 3 -
.../xserver-xf86-config/fishriver/xorg.conf | 26 -----
.../xorg-xserver/xserver-xf86-config_0.1.bbappend | 1 -
.../linux/linux-yocto-rt_3.0.bbappend | 8 --
.../linux/linux-yocto-rt_3.2.bbappend | 8 --
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 9 --
.../recipes-kernel/linux/linux-yocto_3.2.bbappend | 8 --
.../recipes-kernel/linux/linux-yocto_3.4.bbappend | 8 --
15 files changed, 0 insertions(+), 255 deletions(-)
delete mode 100644 meta-fishriver/COPYING.MIT
delete mode 100644 meta-fishriver/README
delete mode 100644 meta-fishriver/README.sources
delete mode 100644 meta-fishriver/binary/.gitignore
delete mode 100644 meta-fishriver/conf/layer.conf
delete mode 100644 meta-fishriver/conf/machine/fishriver.conf
delete mode 100644 meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig
delete mode 100644 meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
delete mode 100644 meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf
delete mode 100644 meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend

diff --git a/MAINTAINERS b/MAINTAINERS
index 5bcf470..3bf0add 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -56,10 +56,6 @@ EMENLOW
M: Tom Zanussi <tom.zanussi@...>
F: meta-emenlow/

-FISHRIVER
-M: Tom Zanussi <tom.zanussi@...>
-F: meta-fishriver/
-
FRI2
M: Darren Hart <dvhart@...>
F: meta-fri2/
diff --git a/meta-fishriver/COPYING.MIT b/meta-fishriver/COPYING.MIT
deleted file mode 100644
index fb950dc..0000000
--- a/meta-fishriver/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
diff --git a/meta-fishriver/README b/meta-fishriver/README
deleted file mode 100644
index 1dd0a4c..0000000
--- a/meta-fishriver/README
+++ /dev/null
@@ -1,114 +0,0 @@
-This README file contains information on building the meta-fishriver
-BSP layer, and booting the images contained in the /binary directory.
-Please see the corresponding sections below for details.
-
-
-Dependencies
-============
-
-This layer depends on:
-
- URI: git://git.openembedded.org/bitbake
- branch: master
-
- URI: git://git.openembedded.org/openembedded-core
- layers: meta
- branch: master
-
- URI: git://git.yoctoproject.org/meta-intel
- layers: intel
- branch: master
-
-
-Patches
-=======
-
-Please submit any patches against this BSP to the Yocto mailing list
-(yocto@...) and cc: the maintainer:
-
-Maintainer: Tom Zanussi <tom.zanussi@...>
-
-Please see the meta-intel/MAINTAINERS file for more details.
-
-
-Table of Contents
-=================
-
- I. Building the meta-fishriver BSP layer
- II. Booting the images in /binary
-
-
-I. Building the meta-fishriver BSP layer
-========================================
-
-In order to build an image with BSP support for a given release, you
-need to download the corresponding BSP tarball from the 'Board Support
-Package (BSP) Downloads' page of the Yocto Project website.
-
-Having done that, and assuming you extracted the BSP tarball contents
-at the top-level of your yocto build tree, you can build a fishriver
-image by adding the location of the meta-fishriver layer to
-bblayers.conf, along with the meta-intel layer itself (to access
-common metadata shared between BSPs) e.g.:
-
- yocto/meta-intel \
- yocto/meta-intel/meta-fishriver \
-
-To enable the fishriver layer, add the fishriver MACHINE to local.conf:
-
- MACHINE ?= "fishriver"
-
-You should then be able to build a fishriver image as such:
-
- $ source oe-init-build-env
- $ bitbake core-image-sato
-
-At the end of a successful build, you should have a live image that
-you can boot from a USB flash drive (see instructions on how to do
-that below, in the section 'Booting the images from /binary').
-
-As an alternative to downloading the BSP tarball, you can also work
-directly from the meta-intel git repository. For each BSP in the
-'meta-intel' repository, there are multiple branches, one
-corresponding to each major release starting with 'laverne' (0.90), in
-addition to the latest code which tracks the current master (note that
-not all BSPs are present in every release). Instead of extracting a
-BSP tarball at the top level of your yocto build tree, you can
-equivalently check out the appropriate branch from the meta-intel
-repository at the same location.
-
-
-II. Booting the images in /binary
-=================================
-
-This BSP contains bootable live images, which can be used to directly
-boot Yocto off of a USB flash drive.
-
-Under Linux, insert a USB flash drive. Assuming the USB flash drive
-takes device /dev/sdf, use dd to copy the live image to it. For
-example:
-
-# dd if=core-image-sato-fishriver-20101207053738.hddimg of=/dev/sdf
-# sync
-# eject /dev/sdf
-
-This should give you a bootable USB flash device. Insert the device
-into a bootable USB socket on the target, and power on. This should
-result in a system booted to the Sato graphical desktop.
-
-If you want a terminal, use the arrows at the top of the UI to move to
-different pages of available applications, one of which is named
-'Terminal'. Clicking that should give you a root terminal.
-
-If you want to ssh into the system, you can use the root terminal to
-ifconfig the IP address and use that to ssh in. The root password is
-empty, so to log in type 'root' for the user name and hit 'Enter' at
-the Password prompt: and you should be in.
-
-----
-
-If you find you're getting corrupt images on the USB (it doesn't show
-the syslinux boot: prompt, or the boot: prompt contains strange
-characters), try doing this first:
-
-# dd if=/dev/zero of=/dev/sdf bs=1M count=512
diff --git a/meta-fishriver/README.sources b/meta-fishriver/README.sources
deleted file mode 100644
index 76180f1..0000000
--- a/meta-fishriver/README.sources
+++ /dev/null
@@ -1,17 +0,0 @@
-The sources for the packages comprising the images shipped with this
-BSP can be found at the following location:
-
-http://downloads.yoctoproject.org/mirror/sources/
-
-The metadata used to generate the images shipped with this BSP, in
-addition to the code contained in this BSP, can be found at the
-following location:
-
-http://www.yoctoproject.org/downloads/yocto-1.2/poky-denzil-7.0.tar.bz2
-
-The metadata used to generate the images shipped with this BSP, in
-addition to the code contained in this BSP, can also be found at the
-following locations:
-
-git://git.yoctoproject.org/poky.git
-git://git.yoctoproject.org/meta-intel
diff --git a/meta-fishriver/binary/.gitignore b/meta-fishriver/binary/.gitignore
deleted file mode 100644
index e69de29..0000000
diff --git a/meta-fishriver/conf/layer.conf b/meta-fishriver/conf/layer.conf
deleted file mode 100644
index 61e292b..0000000
--- a/meta-fishriver/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
-# We have a conf and classes directory, add to BBPATH
-BBPATH := "${BBPATH}:${LAYERDIR}"
-
-# We have a recipes directory, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
- ${LAYERDIR}/recipes-*/*/*.bbappend"
-
-BBFILE_COLLECTIONS += "fishriver"
-BBFILE_PATTERN_fishriver := "^${LAYERDIR}/"
-BBFILE_PRIORITY_fishriver = "6"
-
-LAYERDEPENDS_fishriver = "intel"
diff --git a/meta-fishriver/conf/machine/fishriver.conf b/meta-fishriver/conf/machine/fishriver.conf
deleted file mode 100644
index ec2e87f..0000000
--- a/meta-fishriver/conf/machine/fishriver.conf
+++ /dev/null
@@ -1,17 +0,0 @@
-#@TYPE: Machine
-#@NAME: fishriver
-
-#@DESCRIPTION: Machine configuration for Fish River Island systems
-# i.e. Z530/E660 + EG20T
-
-PREFERRED_VERSION_linux-yocto ?= "3.4%"
-
-require conf/machine/include/tune-atom.inc
-require conf/machine/include/ia32-base.inc
-
-XSERVER ?= "${XSERVER_IA32_BASE} \
- ${XSERVER_IA32_EXT} \
- ${XSERVER_IA32_VESA} \
- "
-
-APPEND += "video=vesafb vga=0x318"
diff --git a/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig b/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig
deleted file mode 100644
index ffce012..0000000
--- a/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig
+++ /dev/null
@@ -1,3 +0,0 @@
-# Assume a USB mouse and keyboard are connected
-HAVE_TOUCHSCREEN=0
-HAVE_KEYBOARD=1
diff --git a/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 6644a84..0000000
--- a/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1,3 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-PRINC := "${@int(PRINC) + 2}"
diff --git a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf b/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf
deleted file mode 100644
index da4fc3c..0000000
--- a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf
+++ /dev/null
@@ -1,26 +0,0 @@
-Section "Device"
- Identifier "Generic VESA"
- Driver "vesa"
-EndSection
-
-Section "Monitor"
- Identifier "Generic Monitor"
- Option "DPMS"
-EndSection
-
-Section "Screen"
- Identifier "Default Screen"
- Device "Generic VESA"
- Monitor "Generic Monitor"
- DefaultDepth 24
-EndSection
-
-Section "ServerLayout"
- Identifier "Default Layout"
- Screen "Default Screen"
-EndSection
-
-Section "ServerFlags"
- Option "DontZap" "0"
- Option "AutoAddDevices" "False"
-EndSection
diff --git a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend b/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
deleted file mode 100644
index 72d991c..0000000
--- a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend b/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
deleted file mode 100644
index 7a502bd..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-
-# Update the following to use a different BSP branch or meta SRCREV
-#KBRANCH_fishriver = "yocto/standard/preempt-rt/base"
-#SRCREV_machine_pn-linux-yocto-rt_fishriver ?= XXXX
-#SRCREV_meta_pn-linux-yocto-rt_fishriver ?= XXXX
diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend b/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
deleted file mode 100644
index a91a425..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-
-# Update the following to use a different BSP branch or meta SRCREV
-#KBRANCH_fishriver = "standard/preempt-rt/base"
-#SRCREV_machine_pn-linux-yocto-rt_fishriver ?= XXXX
-#SRCREV_meta_pn-linux-yocto-rt_fishriver ?= XXXX
diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
deleted file mode 100644
index 6ac6ef5..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
+++ /dev/null
@@ -1,9 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-KBRANCH_fishriver = "yocto/standard/fishriver"
-KERNEL_FEATURES_append_fishriver += " cfg/smp.scc"
-
-SRCREV_machine_pn-linux-yocto_fishriver ?= "c139592c96722727a9f074515a4061c3820da1a6"
-SRCREV_meta_pn-linux-yocto_fishriver ?= "59314a3523e360796419d76d78c6f7d8c5ef2593"
diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
deleted file mode 100644
index 9a2f678..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-KBRANCH_fishriver = "standard/default/fishriver"
-
-SRCREV_machine_pn-linux-yocto_fishriver ?= "969edd015a46eed77d6c3daeffdc299dd06e3397"
-SRCREV_meta_pn-linux-yocto_fishriver ?= "5b4c9dc78b5ae607173cc3ddab9bce1b5f78129b"
diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
deleted file mode 100644
index c0d04dc..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-KBRANCH_fishriver = "standard/fishriver"
-
-SRCREV_machine_pn-linux-yocto_fishriver ?= "3fa06aa29078fdb2af431de2d3fdae7d281ba85f"
-SRCREV_meta_pn-linux-yocto_fishriver ?= "5bdc655034a58a7147176a8a882d81e2fd51e4b9"
--
1.7.3.4


[PATCHv4 3/8] emgd-driver_bin_1.10: Remove in favor of 1.14

nitin.a.kamble@...
 

From: Nitin A Kamble <nitin.a.kamble@...>

All BSPs have been migrated to 1.14, we can now safely retire 1.10

Signed-off-by: Nitin A Kamble <nitin.a.kamble@...>
---
.../xorg-driver/emgd-driver-bin_1.10.bb | 93 --------------------
1 files changed, 0 insertions(+), 93 deletions(-)
delete mode 100644 common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb

diff --git a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb
deleted file mode 100644
index 6d80bee..0000000
--- a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb
+++ /dev/null
@@ -1,93 +0,0 @@
-SUMMARY = "EMGD 1.10 xserver binaries"
-DESCRIPTION = "EMGD 1.10 includes some userspace binaries that use non-free \
-licensing, which are now available via a non-click-through downloadable \
-tarball, and is what this recipe now uses. Since it is a non-free license, \
-this recipe is marked as 'License_emgd-driver-bin_1.10' and you need to add \
-to LICENSE_FLAGS_WHITELIST += \"License_emgd-driver-bin_1.10\" to your \
-local.conf in order to enable it in a build."
-LICENSE = "Intel-binary-only"
-LICENSE_FLAGS = "license_${PN}_${PV}"
-PR = "r1"
-
-EMGD_LIC_DIR = "IEMGD_HEAD_Linux/License"
-EMGD_RPM_DIR = "IEMGD_HEAD_Linux/MeeGo1.2"
-EMGD_VIDEO_PLUGIN_DIR = "../common/video_plugin"
-
-LIC_FILES_CHKSUM = "file://${WORKDIR}/${EMGD_LIC_DIR}/License.txt;md5=b54f01caaf8483b3cb60c0c40f2bf22d"
-
-DEPENDS = "rpm-native xz-native"
-
-SRC_URI = "https://edc.intel.com/App_Shared/Downloads/LIN_EMGD_1_10_RC_2209.tgz"
-
-SRC_URI[md5sum] = "e4a38d9efa0b086ae21b68145c4db4e9"
-SRC_URI[sha256sum] = "acea5f0f93a31553553428623c007d7ed0c604cf715fd87dfe075751da4be548"
-
-# These are closed binaries generated elsewhere so don't check ldflags
-INSANE_SKIP_${PN} = "ldflags"
-# Inhibit warnings about files being stripped, we can't do anything about it.
-INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
-
-FILES_${PN} += "${libdir}/dri ${libdir}/gstreamer-0.10 ${libdir}/xorg/modules/drivers"
-FILES_${PN}-dbg += "${libdir}/xorg/modules/drivers/.debug ${libdir}/dri/.debug"
-
-S = "${WORKDIR}/${EMGD_RPM_DIR}"
-
-do_install () {
- # A gstreamer VA buffer library
- rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-vabuffer*.rpm | cpio -id
-
- # MIX Common contains common classes, datatype, header files used by other MIX components
- rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixcommon*.rpm | cpio -id
-
- # MIX Video Bitstream Parser is an user library interface for various video format bitstream parsing
- rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixvbp*.rpm | cpio -id
-
- # MIX Video is an user library interface for various video codecs available on the platform.
- rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixvideo*.rpm | cpio -id
-
- install -d -m 0755 ${D}${libdir}/gstreamer-0.10
- install -m 0755 ${S}/usr/lib/* ${D}${libdir}/
-
- # A gstreamer plugin that uses MIX Video for hardware accelerated video decoding and rendering.
- rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-plugins-mixvideo*.rpm | cpio -id
-
- # A collection of gstreamer plugins that uses VA libraries for hardware accelerated video rendering and text overlay.
- rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-plugins-va*.rpm | cpio -id
-
- install -m 0755 ${S}/usr/lib/gstreamer-0.10/* ${D}${libdir}/gstreamer-0.10/
-
- # EMGD runtime graphics libraries
- rpm2cpio ${S}/emgd-bin*.rpm | xz -d | cpio -id
-
- install -d -m 0755 ${D}${libdir}/dri
- install -d -m 0755 ${D}${libdir}/xorg/modules/drivers
- install -d -m 0755 ${D}${sysconfdir}
- install -d -m 0755 ${D}${mandir}/man4
- install -m 0755 ${S}/usr/lib/*.so.* ${D}${libdir}/
- install -m 0755 ${S}/usr/lib/dri/* ${D}${libdir}/dri/
- install -m 0755 ${S}/usr/lib/xorg/modules/drivers/* ${D}${libdir}/xorg/modules/drivers/
- install -m 0755 ${S}/etc/* ${D}${sysconfdir}/
- install -m 0755 ${S}/usr/share/man/man4/* ${D}${mandir}/man4/
-
- # Khronos development headers needed for EGL, OpenGL-ES, and OpenVG development
- rpm2cpio ${S}/emgd-devel*.rpm | xz -d | cpio -id
-
- install -d -m 0755 ${D}${includedir}/EGL
- install -m 0755 ${S}/usr/include/EGL/*.h ${D}${includedir}/EGL/
- install -d -m 0755 ${D}${includedir}/GLES
- install -m 0755 ${S}/usr/include/GLES/*.h ${D}${includedir}/GLES/
- install -d -m 0755 ${D}${includedir}/GLES2
- install -m 0755 ${S}/usr/include/GLES2/*.h ${D}${includedir}/GLES2/
- install -d -m 0755 ${D}${includedir}/KHR
- install -m 0755 ${S}/usr/include/KHR/*.h ${D}${includedir}/KHR/
- install -d -m 0755 ${D}${includedir}/VG
- install -m 0755 ${S}/usr/include/VG/*.h ${D}${includedir}/VG/
-
- ln -sf libEGL.so.1 ${D}${libdir}/libEGL.so
- ln -sf libGLES_CM.so.1 ${D}${libdir}/libGLES_CM.so
- ln -sf libGLESv2.so.2 ${D}${libdir}/libGLESv2.so
- ln -sf libOpenVG.so.1 ${D}${libdir}/libOpenVG.so
- ln -sf libOpenVGU.so.1 ${D}${libdir}/libOpenVGU.so
-}
-
-LEAD_SONAME = "libEGL.so"
--
1.7.3.4


[PATCHv4 2/8] crownbay.conf: specify the 8.0.4 version as preferred version of mesa-dri

nitin.a.kamble@...
 

From: Nitin A Kamble <nitin.a.kamble@...>

Avoid following warnings while building crownbay BSPs:

NOTE: preferred version 7.11 of mesa-dri not available (for item virtual/libgl)
NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7

This commit addresses one of the issue reported on the bug:
[YOCTO #3238]

Signed-off-by: Nitin A Kamble <nitin.a.kamble@...>
---
meta-crownbay/conf/machine/crownbay.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf
index c18fa1d..72431de 100644
--- a/meta-crownbay/conf/machine/crownbay.conf
+++ b/meta-crownbay/conf/machine/crownbay.conf
@@ -18,7 +18,7 @@ XSERVER ?= "${XSERVER_IA32_BASE} \
"

PREFERRED_VERSION_xserver-xorg ?= "1.9.3"
-PREFERRED_VERSION_mesa-dri ?= "7.11"
+PREFERRED_VERSION_mesa-dri ?= "8.0.4"
PREFERRED_VERSION_xf86-input-evdev ?= "2.6.0"

APPEND += "video=vesafb vga=0x318 vmalloc=256MB"
--
1.7.3.4


[PATCHv4 0/8] Misc meta-intel commits

nitin.a.kamble@...
 

From: Nitin A Kamble <nitin.a.kamble@...>

This v4 pull request add these extra commits compared to v3
mesa-dri.bbappend: avoid conflict with emgd-driver-bin
emgd-driver-bin: note all the EMGD licenses
custom-licenses dir for emgd recipe Licenses

Thanks,
Nitin

The following changes since commit 5d8a05811101f7d69994f4028ec620c4480f6da4:

Fix use of PRINC in meta-intel BSPs (2012-10-09 16:04:30 -0700)

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 (8):
xf86-video-intel: Bring 2.20.0 version to match released graphics
stack
crownbay.conf: specify the 8.0.4 version as preferred version of
mesa-dri
emgd-driver_bin_1.10: Remove in favor of 1.14
fishriver BSP retirement
update maintainers of various BSPs
mesa-dri.bbappend: avoid conflict with emgd-driver-bin
emgd-driver-bin: note all the EMGD licenses
custom-licenses dir for emgd recipe Licenses

MAINTAINERS | 16 +-
.../Intel-software-license-emgd-1.14 | 42 ++
...-space-graphics-driver-binary-license-emgd-1.14 | 559 ++++++++++++++++++++
.../recipes-graphics/mesa/mesa-dri_8.0.4.bbappend | 24 +
.../xorg-driver/emgd-driver-bin_1.10.bb | 93 ----
.../xorg-driver/emgd-driver-bin_1.14.bb | 5 +-
.../xorg-driver/xf86-video-intel_2.20.0.bb | 27 +
.../xorg-driver/xorg-driver-common.inc | 33 ++
.../xorg-driver/xorg-driver-video.inc | 4 +
conf/layer.conf | 3 +
meta-chiefriver/README | 11 +
meta-crownbay/README | 2 +-
meta-crownbay/conf/machine/crownbay.conf | 2 +-
meta-emenlow/README | 2 +-
meta-fishriver/COPYING.MIT | 17 -
meta-fishriver/README | 114 ----
meta-fishriver/README.sources | 17 -
meta-fishriver/conf/layer.conf | 12 -
meta-fishriver/conf/machine/fishriver.conf | 17 -
.../formfactor/formfactor/fishriver/machconfig | 3 -
.../recipes-bsp/formfactor/formfactor_0.0.bbappend | 3 -
.../xserver-xf86-config/fishriver/xorg.conf | 26 -
.../xorg-xserver/xserver-xf86-config_0.1.bbappend | 1 -
.../linux/linux-yocto-rt_3.0.bbappend | 8 -
.../linux/linux-yocto-rt_3.2.bbappend | 8 -
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 9 -
.../recipes-kernel/linux/linux-yocto_3.2.bbappend | 8 -
.../recipes-kernel/linux/linux-yocto_3.4.bbappend | 8 -
meta-jasperforest/README | 2 +-
meta-sugarbay/README | 2 +-
30 files changed, 717 insertions(+), 361 deletions(-)
create mode 100644 common/custom-licenses/Intel-software-license-emgd-1.14
create mode 100644 common/custom-licenses/Intel-user-space-graphics-driver-binary-license-emgd-1.14
create mode 100644 common/recipes-graphics/mesa/mesa-dri_8.0.4.bbappend
delete mode 100644 common/recipes-graphics/xorg-driver/emgd-driver-bin_1.10.bb
create mode 100644 common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb
create mode 100644 common/recipes-graphics/xorg-driver/xorg-driver-common.inc
create mode 100644 common/recipes-graphics/xorg-driver/xorg-driver-video.inc
delete mode 100644 meta-fishriver/COPYING.MIT
delete mode 100644 meta-fishriver/README
delete mode 100644 meta-fishriver/README.sources
delete mode 100644 meta-fishriver/binary/.gitignore
delete mode 100644 meta-fishriver/conf/layer.conf
delete mode 100644 meta-fishriver/conf/machine/fishriver.conf
delete mode 100644 meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig
delete mode 100644 meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
delete mode 100644 meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf
delete mode 100644 meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend

--
1.7.3.4


[PATCHv4 1/8] xf86-video-intel: Bring 2.20.0 version to match released graphics stack

nitin.a.kamble@...
 

From: Nitin A Kamble <nitin.a.kamble@...>

The Intel Linux graphics stack version 12.07 released on 2012-07-24
requires version 2.20.0 as seen here:
http://intellinuxgraphics.org/2012.07.html

Currently oecore has 2.19.0 version. So get this 2.20.0 version in
meta-intel layer to be used by sugarbay and other BSPs using the
Intel graphics stack.

Also took changes from version 2.20.8 recipe from Ross Burton's branch.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@...>
---
.../xorg-driver/xf86-video-intel_2.20.0.bb | 27 ++++++++++++++++
.../xorg-driver/xorg-driver-common.inc | 33 ++++++++++++++++++++
.../xorg-driver/xorg-driver-video.inc | 4 ++
3 files changed, 64 insertions(+), 0 deletions(-)
create mode 100644 common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb
create mode 100644 common/recipes-graphics/xorg-driver/xorg-driver-common.inc
create mode 100644 common/recipes-graphics/xorg-driver/xorg-driver-video.inc

diff --git a/common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb b/common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb
new file mode 100644
index 0000000..6cfca03
--- /dev/null
+++ b/common/recipes-graphics/xorg-driver/xf86-video-intel_2.20.0.bb
@@ -0,0 +1,27 @@
+require xorg-driver-video.inc
+
+SUMMARY = "X.Org X server -- Intel integrated graphics chipsets driver"
+
+DESCRIPTION = "intel is an Xorg driver for Intel integrated graphics \
+chipsets. The driver supports depths 8, 15, 16 and 24. On some chipsets, \
+the driver supports hardware accelerated 3D via the Direct Rendering \
+Infrastructure (DRI)."
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=8730ad58d11c7bbad9a7066d69f7808e"
+
+PR = "${INC_PR}.0"
+
+DEPENDS += "virtual/libx11 drm xf86driproto glproto \
+ virtual/libgl xineramaproto xf86driproto libpciaccess"
+
+PACKAGECONFIG ??= ""
+PACKAGECONFIG[sna] = "--enable-sna,--disable-sna"
+PACKAGECONFIG[xvmc] = "--enable-xvmc,--disable-xvmc,libxvmc"
+
+# --enable-kms-only option is required by ROOTLESS_X
+EXTRA_OECONF += '${@base_conditional( "ROOTLESS_X", "1", " --enable-kms-only", "", d )}'
+
+COMPATIBLE_HOST = '(i.86|x86_64).*-linux'
+
+SRC_URI[md5sum] = "070bb866b05a16366bd9bb844c9b91aa"
+SRC_URI[sha256sum] = "21949297220ceda32bba430f778c6409002079dc717c7190dbd1062ab4a56783"
diff --git a/common/recipes-graphics/xorg-driver/xorg-driver-common.inc b/common/recipes-graphics/xorg-driver/xorg-driver-common.inc
new file mode 100644
index 0000000..1ed2742
--- /dev/null
+++ b/common/recipes-graphics/xorg-driver/xorg-driver-common.inc
@@ -0,0 +1,33 @@
+DESCRIPTION = "X driver"
+HOMEPAGE = "http://www.x.org"
+BUGTRACKER = "https://bugs.freedesktop.org"
+SECTION = "x11/drivers"
+LICENSE = "MIT-X"
+
+PE = "2"
+INC_PR = "r0"
+
+DEPENDS = "virtual/xserver xproto randrproto util-macros"
+
+SRC_URI = "${XORG_MIRROR}/individual/driver/${BPN}-${PV}.tar.bz2"
+
+S = "${WORKDIR}/${BPN}-${PV}"
+
+FILES_${PN} += " ${libdir}/xorg/modules/drivers/*.so"
+FILES_${PN}-dbg += " ${libdir}/xorg/modules/drivers/.debug"
+
+inherit autotools pkgconfig
+
+# AC_CHECK_FILE doesn't work when cross compiling, so we create a replacement
+# macro that simply assumes the test succeeds.
+do_configure_prepend () {
+ echo 'AC_DEFUN(CC_AC_CHECK_FILE, $2)' > configure.ac.new
+ sed 's/AC_CHECK_FILE/CC_AC_CHECK_FILE/g' configure.ac >> configure.ac.new
+ mv configure.ac.new configure.ac
+}
+
+# FIXME: We don't want to include the libtool archives (*.la) from modules
+# directory, as they serve no useful purpose. Upstream should fix Makefile.am
+do_install_append() {
+ find ${D}${libdir}/xorg/modules -regex ".*\.la$" | xargs rm -f --
+}
diff --git a/common/recipes-graphics/xorg-driver/xorg-driver-video.inc b/common/recipes-graphics/xorg-driver/xorg-driver-video.inc
new file mode 100644
index 0000000..57c80d1
--- /dev/null
+++ b/common/recipes-graphics/xorg-driver/xorg-driver-video.inc
@@ -0,0 +1,4 @@
+include xorg-driver-common.inc
+
+DEPENDS =+ "renderproto videoproto xextproto fontsproto"
+
--
1.7.3.4


Re: The BitBake equivalent of "Hello, World!"

Patrick Turley <PatrickTurley@...>
 

On Oct 9, 2012, at 5:56 PM, McClintock Matthew-B29882 <B29882@...> wrote:

On Tue, Oct 9, 2012 at 5:31 PM, Patrick Turley
<PatrickTurley@...> wrote:
Success. The file tree depicted at the bottom of this mail is nearly the
smallest, valid BitBake project that prints "Hello, World!" Here's the
output:
Perhaps you could push this to github somewhere as an example?

-M


Getting gcc-4.7 and eglibc-2.16 to work with PowerPC440

Elvis Dowson
 

Hi Khem,
After I finished getting gcc-4.5.4 and eglibc-2.13 to build for the PowerPC440 target, using soft-float, I tried the following combinations

1. gcc-4.7.2 with eglibc-2.13 - result, no prompt on the login screen, able to ping the target board, but no root login prompt. It doesn't crash during the boot process either.

2. gcc-4.5.4 with eglibc-2.16: init crash with a kernel panic, immediately after boot, just before the login prompt.

I vaguely recall somewhere in one of the patches, or browsing some discussions threads on the internet, that before gcc-4.5, support would be dropped for specific powerpc variants. Perhaps is that why I'm running into these issues?

Best regards,

Elvis Dowson


Re: [PATCH 2/5] crownbay.conf: specify the 8.0.4 version as preferred version of mesa-dri

Burton, Ross <ross.burton@...>
 

On 11 October 2012 00:10, Kamble, Nitin A <nitin.a.kamble@...> wrote:
So far I have tested with glxgears and glxinfo with the 8.0.4 version of mesa-dri. And I did not find any issues. And Tom has been testing the same way so far without any complaints. If there is something which can help things test further, it would be nice to add it to the poky tree; so that it can become part of standard tests, and QA also can use it.
A slightly better test than glxgears that is in oe-core is in
libclutter-glx-1.0-examples. Run "test-interactive
test_cairo_flowers" in a terminal, you should get flowers falling down
the screen.

(on cdt, this results in a PVR driver error - #3280)

Ross


Build failure using Master branch for Crownbay

Jim Abernathy
 

I just did a pull today and tried to rebuild Crownbay BSP which I successfully built yesterday. I'm looking for a case where the rebuild fails on a previously successful build with just running bitbake core-image-sato without deleting any files or cleaning anything, as I've been instructed previously.

I got such a failure today and the console log is below. I'll hold off deleting the build directory and rebuilding as I usually do when this happens, until I hear from the experts on how to proceed.

JIm A

Build Configuration:
BB_VERSION = "1.16.0"
TARGET_ARCH = "i586"
TARGET_OS = "linux"
MACHINE = "crownbay"
DISTRO = "poky"
DISTRO_VERSION = "1.3+snapshot-20121011"
TUNE_FEATURES = "m32 core2"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "master:df127c9cef334955e72420724fa6e1f6a6d44662"
meta-intel
meta-crownbay = "master:5d8a05811101f7d69994f4028ec620c4480f6da4"
meta-jfa = "<unknown>:<unknown>"

NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 7.11 of mesa-dri not available (for item virtual/libgl)
NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7
NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri)
NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7
NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri-dev)
NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7
NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri)
NOTE: versions of mesa-dri available: 2:8.0.4 2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_install (see /build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/temp/log.do_install.28628 for further information)
ERROR: Logfile of failure stored in: /build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/temp/log.do_install.28628
Log data follows:
| DEBUG: Executing shell function do_install
| cpio: ./usr/lib/libgstvabuffer.so.0 not created: newer or same age version exists
| cpio: ./usr/lib/libgstvabuffer.so.0.10.8 not created: newer or same age version exists
| 19 blocks
| cpio: ./usr/lib/libmixcommon.so.0 not created: newer or same age version exists
| cpio: ./usr/lib/libmixcommon.so.0.10.8 not created: newer or same age version exists
| 28 blocks
| cpio: ./usr/lib/libmixvbp.so.0 not created: newer or same age version exists
| cpio: ./usr/lib/libmixvbp.so.0.10.8 not created: newer or same age version exists
| cpio: ./usr/lib/libmixvbp_h264.so.0 not created: newer or same age version exists
| cpio: ./usr/lib/libmixvbp_h264.so.0.10.8 not created: newer or same age version exists
| cpio: ./usr/lib/libmixvbp_mpeg4.so.0 not created: newer or same age version exists
| cpio: ./usr/lib/libmixvbp_mpeg4.so.0.10.8 not created: newer or same age version exists
| cpio: ./usr/lib/libmixvbp_vc1.so.0 not created: newer or same age version exists
| cpio: ./usr/lib/libmixvbp_vc1.so.0.10.8 not created: newer or same age version exists
| 358 blocks
| cpio: ./usr/lib/libmixvideo.so.0 not created: newer or same age version exists
| cpio: ./usr/lib/libmixvideo.so.0.10.9 not created: newer or same age version exists
| 465 blocks
| install: omitting directory `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/dri'
| install: omitting directory `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/gstreamer-0.10'
| install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libEGL.so': No such file or directory
| install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libGLES_CM.so': No such file or directory
| install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libGLESv2.so': No such file or directory
| install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libOpenVG.so': No such file or directory
| install: cannot stat `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/libOpenVGU.so': No such file or directory
| install: omitting directory `/build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/IEMGD_HEAD_Linux/MeeGo1.2/usr/lib/xorg'
| ERROR: Function failed: do_install (see /build/crownbay-master/tmp/work/core2-poky-linux/emgd-driver-bin-1.14-r2/temp/log.do_install.28628 for further information)
ERROR: Task 3814 (/home/jim/poky/meta-intel/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.14.bb, do_install) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4452 tasks of which 2802 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
/home/jim/poky/meta-intel/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.14.bb, do_install
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
jim@jim-ubuntu-x64:/build/crownbay-master$


Re: Changelog for 1.3

Burton, Ross <ross.burton@...>
 

On 11 October 2012 12:22, Paul Eggleton <paul.eggleton@...> wrote:
- Mesa can now provide GLES accelerated graphics without X11
Explicitly saying "through EGL" might be a good idea here.

Ross


Changelog for 1.3

Paul Eggleton
 

Hi folks,

I've put together a list of medium to high-level changes based on
browsing through the commits for the release:

- Improved terminal UI which makes it easy to see the tasks that are currently executing, and avoids burying any warnings that are printed
- Eliminated intermediate step when building cross compiler toolchain
- SDK is now relocatable
- Large number of usability improvements in the Hob image building UI
- Upgraded eglibc to version 2.16
- Upgraded gcc to version 4.7
- Added yocto-bsp script for automating the initial parts of creating a new BSP
- Python functions now consistently use four spaces for indentation - no more having to try to match the mix of tabs and spaces in your recipes
- Disabled sharing shared state between machines using different distros by default to avoid glibc version problems
- Fixes to allow qemu-native to be built on host systems without X11 (i.e. for console use only)
- Enabled python and perl scripting for perf as well as text-mode UI
- Added ability to produce a companion SDK together with an image
- Allow forcing the rebuilding of a recipe (new -C and improved -f options)
- Enabled EFI in grub installer
- Mesa can now provide GLES accelerated graphics without X11
- Added script for producing "bootcharts" from buildstats so you can see the timeline of the build
- Checksums for local files referred to in SRC_URI are now included in task signatures so that changing their contents causes the relevant tasks to be re-executed
- Extended bitbake-diffsigs to look up signature files from task and recipe name, and trace back recursively through dependent task changes
- Moved from module-init-tools to kmod
- Added create-recipe script to automate some of the parts of creating a brand new recipe
- Buildhistory improvements: better performance, track postinst/postrm scripts
- Added bin_package bbclass for recipes that package pre-built binaries
- Added doc-pkgs IMAGE_FEATURES feature to install all documentation
- Added class-* overrides - particularly useful for target/cross/crosssdk but works with all classes
- Reference hardware BSPs are now separate from Poky reference distro configuration
- nativesdk is now a prefix rather than a suffix, simplifying packaging in nativesdk recipes greatly
- Detect and warn if files in the sysroot are potentially written to by multiple recipes
- Automatic launching of "screen" within terminal for devshell/patch resolution
- task-* recipes renamed to packagegroup-* and tidied up significantly
- Improved mirror handling - allow mirrors of mirrors; handle errors more gracefully
- Reduced dependencies between debugging symbol packages
- Significant cleanup of X server recipes
- Start to add regression tests for BitBake

Is there anything that belongs here that I have missed? I know we've done a
lot of other bugfixes and package upgrades, we're really after the
highlights.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: [PATCHv2 2/5] crownbay.conf: specify the 8.0.4 version as preferred version of mesa-dri

Burton, Ross <ross.burton@...>
 

On 11 October 2012 00:14, Kamble, Nitin A <nitin.a.kamble@...> wrote:
The reason is we want to know if the version of mesa in oecore has changed or not. EMGD has specific needs of mesa, and in the testing we are not finding any issues with v8.0.4 of mesa. But that may not hold true for future versions of mesa, so we would like to pin the version here so we know that this version works as expected.
That's an excellent reason.

Ross


Minutes: Yocto Project Technical Team Meeting - Tuesday, October 09, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

Liu, Song <song.liu@...>
 

Sorry for the late.

Attendees:
ScottR, Jessica, Beth, DaveST, PaulE, Richard, Sea, Fahad, DavidW, Denys, AlexG, Ross, Song
 
Amit: MontaVista, based in India, Bangalore. Replacing Mark in this meeting for MontaVista Dave, Michael,
 
Minutes:
 
* Opens collection - 5 min (Song)
* Yocto 1.3 status - 10 min (Song/team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status
- RC4 is due out tomorrow. Larger, invasive less possibility going in. 3.4.10 kernel caused segfault on arm. We are going to move to 3.4.11. Master is still in bug fixing mode. At the moment we will take everything into the release branch. Hoping to release RC4.
- If you expect anything in the release, please get them in today. If you.
- Medium+ bugs review: https://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&list_id=16013&priority=Medium%2B&query_format=advanced&target_milestone=1.3&target_milestone=1.3%20M1&target_milestone=1.3%20M2&target_milestone=1.3%20M3&target_milestone=1.3%20M4&target_milestone=1.3%20M5&target_milestone=1.3.1&target_milestone=1.3.2&order=assigned_to%20DESC%2Cpriority%2Cbug_status%20DESC%2Cbug_id&query_based_on=
 
3176: delay to 1.4. not doable, easy to workaround, release note this one.
1640: How to document, it will be wiki for 1.3 release 3080, release note.
3231, release note.
- Non-bug issues: Paul to send song email.
 
* SWAT team rotation: Saul
* Opens - 10 min
* Team sharing - 20 min
- Paul: documentation and bug fixes recently. Got some time to release the build history tool. This is a little web app allows you to go through warning, mark each one needing attention. Will send email today with more details. Publish the meta-webserver layer. Apache, modphp, php myadmin. It's functional, but there are some bugs. Still working on it. RP: QA can use this.
- Michael: last week SSD upgrade on servers. worked with Beth on release prep. Working on some of the internal servers, space issues, etc.
- Beth: Last week worked with Michael on external ABs. should speed up build time a little bit. Working on 2 release script. 1.main YP release script. It does major release. Related to the eclipse bug. Single push button. 2. release script for people using YP to build and release with GPL compliance. Bring together all the source code, release, etc. together.
- David Wolf: if you submit a patch, how do we know if it is applied. Saul: we review the patches on the mailing list. Saul pull into Master under test, then send to Richard. Richard pull them into master. There are times Richard see something to be directly pulled in without MUT. You should see a email if it's merged. If you don't see any response, ping it.
. RP: for managing the balance of updating to the latest master and maintaining a queue of un-merged patches, recommend looking at Git, probably maintaining a branch in git with master update/rebase and local fixes. If the master does merge those patches, rebase.
. Some fixes on master will be back ported to stable releases. The patches need to be based on master generally, then back ported. Read only http pull (Michael has been working on) will help.


Minutes: Yocto Project Technical Team Meeting - Tuesday, October 09, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

Liu, Song <song.liu@...>
 

Sorry for the late.

Attendees:
ScottR, Jessica, Beth, DaveST, PaulE, Richard, Sea, Fahad, DavidW, Denys, AlexG, Ross, Song
 
Amit: MontaVista, based in India, Bangalore. Replacing Mark in this meeting for MontaVista
Dave, Michael,
 
Minutes:
 
* Opens collection - 5 min (Song)
* Yocto 1.3 status - 10 min (Song/team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status
- RC4 is due out tomorrow. Larger, invasive less possibility going in. 3.4.10 kernel caused segfault on arm. We are going to move to 3.4.11. Master is still in bug fixing mode. At the moment we will take everything into the release branch. Hoping to release RC4.
- If you expect anything in the release, please get them in today. If you.
- Medium+ bugs review: https://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&list_id=16013&priority=Medium%2B&query_format=advanced&target_milestone=1.3&target_milestone=1.3%20M1&target_milestone=1.3%20M2&target_milestone=1.3%20M3&target_milestone=1.3%20M4&target_milestone=1.3%20M5&target_milestone=1.3.1&target_milestone=1.3.2&order=assigned_to%20DESC%2Cpriority%2Cbug_status%20DESC%2Cbug_id&query_based_on=
 
3176: delay to 1.4. not doable, easy to workaround, release note this one.
1640: How to document, it will be wiki for 1.3 release
3080, release note.
3231, release note.
- Non-bug issues: Paul to send song email.
 
* SWAT team rotation: Saul
* Opens - 10 min
* Team sharing - 20 min
- Paul: documentation and bug fixes recently. Got some time to release the build history tool. This is a little web app allows you to go through warning, mark each one needing attention. Will send email today with more details. Publish the meta-webserver layer. Apache, modphp, php myadmin. It's functional, but there are some bugs. Still working on it. RP: QA can use this.
- Michael: last week SSD upgrade on servers. worked with Beth on release prep. Working on some of the internal servers, space issues, etc.
- Beth: Last week worked with Michael on external ABs. should speed up build time a little bit. Working on 2 release script. 1.main YP release script. It does major release. Related to the eclipse bug. Single push button. 2. release script for people using YP to build and release with GPL compliance. Bring together all the source code, release, etc. together.
- David Wolf: if you submit a patch, how do we know if it is applied. Saul: we review the patches on the mailing list. Saul pull into Master under test, then send to Richard. Richard pull them into master. There are times Richard see something to be directly pulled in without MUT. You should see a email if it's merged. If you don't see any response, ping it.
. RP: for managing the balance of updating to the latest master and maintaining a queue of un-merged patches, recommend looking at Git, probably maintaining a branch in git with master update/rebase and local fixes. If the master does merge those patches, rebase.
. Some fixes on master will be back ported to stable releases. The patches need to be based on master generally, then back ported. Read only http pull (Michael has been working on) will help.


Re: 1.3 RC3 full pass test reports

Liu, Song <song.liu@...>
 

Hi Laurentiu,

 

Thanks a lot for the full test report. Great work!

 

Here’s a quick summary of the bugs in this report:

 

·         Resolved:  3142, 3186, 3201 ,3203

·         Release note candidate: 3080, 3100, 2694

·         Patch Review: 3199

·         3233: might be a QA machine setup issue. Tom/Jessica cannot recreate. Needs QA verification/feedback

·         3007: it's an enhancement, not a bug.

·         3116: patch merged, needs to be marked as resolved and QA verification.

·         All others (2878 2918 3125 and others) are still being worked on. 2878 seems widespread, I’ll check with Mark Hatle. Others don't seem to indicate any special concern, especially for the release at this point.

 

Please make sure we verify all the resolved bugs here in M4 build and work with Tom/Jessica to clarify 3233.

 

Thanks!

Song

 

From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Serban, Laurentiu
Sent: Wednesday, October 10, 2012 1:12 PM
To: yocto@...
Subject: [yocto] 1.3 RC3 full pass test reports

 

Hello guys,

 

Here are the test results for the 1.3 RC3 full pass.

The commit id is: 86c9aa8081f107420cd3763d0566d779daddc2b1

 

For the performance tests: the build for sato x86 took 88 minutes (a slight decrease in perfomance)

 

The following issue are encountered. I also updated with comments from Jessica and Saul:

-          For the BSPs:

o   For qemu x86_64 images – the zypper refresh fails (2694),

o   For all the boards there is commos n issue with the Sudoku-savant application (2878)

o   Dmesg errors on e-menlow sato image (2866)

o   An old problem shutting down and arm qemu machine (684)

-          For core build system:

o   There are still errors with the do_rootfs fails for lib64-core-image-sato-sdk (2918), there is a small issue with the sstate-cache-management.sh (3116) and there is a problem related to meta-intel BSP creation using yocto-bsp (3142).

o   Also there is an issue with dash vs. x32 on Ubuntu (3080) [SW] bash vs dash issue on Ubuntu

-          For ADT

o   There are issues with the lttng (3203) and meta-toolchain-support (3100). [JZ] This one is the only one that remains as an issue

o   There is an issue using the standalone toolchain for ARM and x86 (3201) [JZ] resolved

o   An error occurs when selecting kernel 3.4 in Yocto-bsp tool (3233) [JZ] need confirmation for AlexG, maybe a sighting? since both Tom and I can’t reproduce from commandline and eclipse plugin

o   iptables 1.4.15 compile failed on qemux86,qemuarm i686 gmae-toolchain (3125)

-          For HOB:

o   Choosing another toolchain host than x86_64 produces an hob-toolchain error (3199)

o   Improve bblayers-hob.conf (3007)

 

Test Result Summary

Component

Target

Status

Comments

Boards

p1022ds

GOOD

Sudoku-savant issue (2878)

Beagleboard

GOOD

Sudoku-savant issue (2878, 3186)

Routerstationpro

GOOD

Sudoku-savant issue (2878)

Mpc8315e-rdb

GOOD

Sudoku-savant issue (2878)

eMenlow-sato-sdk

BUGGY

Sudoku-savant issue (2878)

dmesg errors on emenlow sato image (2866)

Blacksand-sato-sdk

GOOD

Sudoku-savant issue (2878)

Sugarbay sato-sdk

GOOD

Sudoku-savant issue (2878)

Crownbay-emgd-sato-sdk

GOOD

Sudoku-savant issue (2878)

FRI2-sato

GOOD

Sudoku-savant build issue (2878)

HuronRiver-sato

GOOD

Sudoku-savant issue (2878)

Jasperforest-lsb

GOOD

Sudoku-savant issue (2878), zypper is not installed in core-image-lsb-sdk (3098)

QEMU

 

 

 

Qemuarm

GOOD

Everything runs well

Qemuppc

GOOD

Everything runs well

Qemumips

GOOD

Everything runs well

qemux86

GOOD

Everything runs well

qemux86-64

BUGGY

Zypper issue (2694)

Core build system

 

BUGGY

incremental RPM generation (3047),

lib64-core-image-sato-sdk fails due to do_rootfs issue (2918)

sstate-cache-management.sh prints some error message when running (3116)

[meta-x32] x32 image fails to build due to no recipes available for eglib_2.15 (3080)

HOB

 

GOOD

[HOB]toolchain arch in settings is not saved (3199)

Improve bblayers-hob.conf (3007)

ADT

 

BUGGY

autoreconf run failed on x86-64 gmae-toolchain (3100)

cannot build Hello World Ansi C project using standalone Toolchain for ARM and X86 (3201)

kernel trace type not available in the lttng project (3203)

error when selecting kernel version 3.4 in yocto bsp tool (3233)

iptables 1.4.15 compile failed on qemux86,qemuarm i686 gmae-toolchain (3125)

Stress Testing

GOOD

Both Crashme and Helltest on Jasperforest could pass 24 hours stress testing

Distribution Support

GOOD

Everything runs well for Ubuntu 12.04, Ubuntu 12.10 – nightly, OpenSuse 12.1, OpenSuse 12.2 RC2, Fedora 17, CentOs 6.3, Fedora 16

Power and Performance

GOOD

one qemux86 sato build on a Core i7 machine costs 88 minutes with the packages previously fetched.

Compliance

GOOD

Tests on Huron River and BlackSand passed

Build Appliance

GOOD

Everything runs well on VMWare Player (on Ubuntu). The relevant tests were performed also for qemu-kvm on Fedora 17 libvirt and

VMWare Workstation.(Ubuntu)

 

 

Detailed Test Result for each component

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

Beagleboard Sato-SDK

42

0

37

5(2878, 3186)

0

Routerstationpro Sato-SDK

35

0

34

1(2878)

0

p1022ds-sato-sdk

37

0

36

1(2878)

0

Mpc8315e-rdb Sato-SDK

37

0

36

1(2878)

0

eMenlow Sato-sdk

67

0

64

3 (bug 2878,3091)

0

n450 Sato-sdk

67

0

66

1 (bug 2878)

0

Crownbay-Sato-sdk

65

0

62

3 (2878, 2792, 2386, 1258)

0

FRI2 Sato-sdk

85

0

84

1 (2878)

0

HuronRiver Sato-sdk

68

0

67

1 (2878)

0

Sugarbay sato-sdk

68

0

67

1 (2878)

0

Jasperforest lsb-sdk

34

0

26

8 (2878,3098)

0

Qemuarm Sato

31

0

31

0

0

Qemuarm Sato-SDK

36

0

36

0

0

Qemumips Sato

31

0

31

0

0

Qemumips Sato-SDK

36

0

36

0

0

Qemuppc Sato

31

0

31

0

0

Qemuppc Sato-SDK

36

0

36

0

0

Qemux86-64 Sato

30

0

27

3 (bug 2694)

0

Qemux86-64 Sato-SDK

36

0

32

4 (bug 2694)

0

Qemux86 Sato

30

0

30

0

0

Qemux86 Sato-SDK

36

0

36

0

0

Core build system

64

0

57

7 (3142, 2918, 3116,3080)

0

HOB

39

0

37

2(3199,3007 )

0

ADT

53

0

40

13(3201, 3203, 3100)

0

Build Appliance

14

0

13

1 (3243)

0

Total

1108

0

1052

56

0

 

 

Component

Bug Number

Target Milestone

System & Core OS

System Usage

Bug 2878 pkgconfig is missing from sato-sdk image - installing and then trying to removing it leads to rpm crashes/assertions

Bug 2694 [QEMU-X86_64]zypper refresh fail

Bug 3186 BeagleBoard: rpm query package failed due to glibc realloc() error

Core build system

Bug 3142 [yocto-bsp] kernel panic message for yocto-bsp based images.

Bug  3116 sstate-cache-management.sh prints some error message when running

Bug 3080 [meta-x32] x32 image fails to build due to no recipes available for eglib_2.15

Bug 2918  lib64-core-image-sato-sdk fails due to do_rootfs issue.

ADT

Bug 3100 autoreconf run failed on x86-64 gmae-toolchain

Bug 3201 cannot build Hello World Ansi C project using standalone Toolchain for ARM and X86

Bug 3203  kernel trace type not available in the lttng project

Bug 3233 error when selecting kernel version 3.4 in yocto bsp tool

Bug 3125 iptable 1.4.15 compile failed on qemux86,qemuarm i686 gmae-toolchain

HOB

Bug 3199 Choosing another toolchain host than x86_64 produces an hob-toolchain error

Bug 3007 Improve bblayers-hob.conf

 

 

 

Best regards,

Laurentiu Serban

QA Engineer

Open Source Technology Center

System Software Division Romania

Desk: +40 31 8604742

iNET: 88451042

 


Re: [PATCHv2 4/5] fishriver BSP retirement

Bruce Ashfield <bruce.ashfield@...>
 

On 12-10-10 7:18 PM, Kamble, Nitin A wrote:


-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@...]
Sent: Wednesday, October 10, 2012 2:07 PM
To: Kamble, Nitin A
Cc: Zanussi, Tom; Hart, Darren; yocto@...
Subject: Re: [yocto] [PATCHv2 4/5] fishriver BSP retirement

On 12-10-09 09:16 PM, nitin.a.kamble@... wrote:
From: Nitin A Kamble<nitin.a.kamble@...>

This commit removes fishriver bsp from meta-intel layer.

Fish-River-Islnad-2 hardware and BSP has made this
Fish-River-Island hardware and BSP absolute.
Also we discussed this on the Yocto Execution Tracking Meeting, and
to our knowledge no customer is using (cares about) this BSP now.
Just so I don't forget, can you send a patch that also removes the kernel
meta data for the BSP ? That way I won't recreate the branch for future
releases :)
Removing the FRI-1 contents from meta branch of v3.4 kernel tree should be ok because it preserves the old commits.
But I think we will have to leave the topic branch for fishriver machine as it is.
ok, works for me. We still do have the yocto-kernel-cache repository
to track the history, but for historical purposes, I agree that keeping
it in all the 3.x trees is ok, without the meta-intel support .. you can't
build it and it doesn't do any harm.


I assume it is ok that the kernel branches stay in the 3.x kernels for the yocto
1.3 release ?
I also think that is the right way to handle it.
Fine with me as well, I'll just ensure that it doesn't appear in new
repos, a kernel meta commit patch against the 3.4 tree that says 3.6+
will make sure that happens.

Bruce


Regards,
Nitin


Cheers,

Bruce


Signed-off-by: Nitin A Kamble<nitin.a.kamble@...>
---
MAINTAINERS | 4 -
meta-fishriver/COPYING.MIT | 17 ---
meta-fishriver/README | 114 --------------------
meta-fishriver/README.sources | 17 ---
meta-fishriver/conf/layer.conf | 12 --
meta-fishriver/conf/machine/fishriver.conf | 17 ---
.../formfactor/formfactor/fishriver/machconfig | 3 -
.../recipes-bsp/formfactor/formfactor_0.0.bbappend | 3 -
.../xserver-xf86-config/fishriver/xorg.conf | 26 -----
.../xorg-xserver/xserver-xf86-config_0.1.bbappend | 1 -
.../linux/linux-yocto-rt_3.0.bbappend | 8 --
.../linux/linux-yocto-rt_3.2.bbappend | 8 --
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 9 --
.../recipes-kernel/linux/linux-yocto_3.2.bbappend | 8 --
.../recipes-kernel/linux/linux-yocto_3.4.bbappend | 8 --
15 files changed, 0 insertions(+), 255 deletions(-)
delete mode 100644 meta-fishriver/COPYING.MIT
delete mode 100644 meta-fishriver/README
delete mode 100644 meta-fishriver/README.sources
delete mode 100644 meta-fishriver/binary/.gitignore
delete mode 100644 meta-fishriver/conf/layer.conf
delete mode 100644 meta-fishriver/conf/machine/fishriver.conf
delete mode 100644 meta-fishriver/recipes-
bsp/formfactor/formfactor/fishriver/machconfig
delete mode 100644 meta-fishriver/recipes-
bsp/formfactor/formfactor_0.0.bbappend
delete mode 100644 meta-fishriver/recipes-graphics/xorg-
xserver/xserver-xf86-config/fishriver/xorg.conf
delete mode 100644 meta-fishriver/recipes-graphics/xorg-
xserver/xserver-xf86-config_0.1.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-
rt_3.0.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-
rt_3.2.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-
yocto_3.0.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-
yocto_3.2.bbappend
delete mode 100644
meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend

diff --git a/MAINTAINERS b/MAINTAINERS index 5bcf470..3bf0add 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -56,10 +56,6 @@ EMENLOW
M: Tom Zanussi<tom.zanussi@...>
F: meta-emenlow/

-FISHRIVER
-M: Tom Zanussi<tom.zanussi@...>
-F: meta-fishriver/
-
FRI2
M: Darren Hart<dvhart@...>
F: meta-fri2/
diff --git a/meta-fishriver/COPYING.MIT b/meta-fishriver/COPYING.MIT
deleted file mode 100644 index fb950dc..0000000
--- a/meta-fishriver/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
-Permission is hereby granted, free of charge, to any person obtaining
a copy -of this software and associated documentation files (the
"Software"), to deal -in the Software without restriction, including
without limitation the rights -to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell -copies of the Software, and to
permit persons to whom the Software is -furnished to do so, subject to the
following conditions:
-
-The above copyright notice and this permission notice shall be
included in -all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF
MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT
HOLDERS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN
AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR
IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN -
THE SOFTWARE.
diff --git a/meta-fishriver/README b/meta-fishriver/README deleted
file mode 100644 index 1dd0a4c..0000000
--- a/meta-fishriver/README
+++ /dev/null
@@ -1,114 +0,0 @@
-This README file contains information on building the meta-fishriver
-BSP layer, and booting the images contained in the /binary directory.
-Please see the corresponding sections below for details.
-
-
-Dependencies
-============
-
-This layer depends on:
-
- URI: git://git.openembedded.org/bitbake
- branch: master
-
- URI: git://git.openembedded.org/openembedded-core
- layers: meta
- branch: master
-
- URI: git://git.yoctoproject.org/meta-intel
- layers: intel
- branch: master
-
-
-Patches
-=======
-
-Please submit any patches against this BSP to the Yocto mailing list
-(yocto@...) and cc: the maintainer:
-
-Maintainer: Tom Zanussi<tom.zanussi@...>
-
-Please see the meta-intel/MAINTAINERS file for more details.
-
-
-Table of Contents
-=================
-
- I. Building the meta-fishriver BSP layer
- II. Booting the images in /binary
-
-
-I. Building the meta-fishriver BSP layer
-========================================
-
-In order to build an image with BSP support for a given release, you
-need to download the corresponding BSP tarball from the 'Board
Support -Package (BSP) Downloads' page of the Yocto Project website.
-
-Having done that, and assuming you extracted the BSP tarball contents
-at the top-level of your yocto build tree, you can build a fishriver
-image by adding the location of the meta-fishriver layer to
-bblayers.conf, along with the meta-intel layer itself (to access
-common metadata shared between BSPs) e.g.:
-
- yocto/meta-intel \
- yocto/meta-intel/meta-fishriver \
-
-To enable the fishriver layer, add the fishriver MACHINE to local.conf:
-
- MACHINE ?= "fishriver"
-
-You should then be able to build a fishriver image as such:
-
- $ source oe-init-build-env
- $ bitbake core-image-sato
-
-At the end of a successful build, you should have a live image that
-you can boot from a USB flash drive (see instructions on how to do
-that below, in the section 'Booting the images from /binary').
-
-As an alternative to downloading the BSP tarball, you can also work
-directly from the meta-intel git repository. For each BSP in the
-'meta-intel' repository, there are multiple branches, one
-corresponding to each major release starting with 'laverne' (0.90),
in -addition to the latest code which tracks the current master (note
that -not all BSPs are present in every release). Instead of
extracting a -BSP tarball at the top level of your yocto build tree,
you can -equivalently check out the appropriate branch from the
meta-intel -repository at the same location.
-
-
-II. Booting the images in /binary
-=================================
-
-This BSP contains bootable live images, which can be used to directly
-boot Yocto off of a USB flash drive.
-
-Under Linux, insert a USB flash drive. Assuming the USB flash drive
-takes device /dev/sdf, use dd to copy the live image to it. For
-example:
-
-# dd if=core-image-sato-fishriver-20101207053738.hddimg of=/dev/sdf
-# sync -# eject /dev/sdf
-
-This should give you a bootable USB flash device. Insert the device
-into a bootable USB socket on the target, and power on. This should
-result in a system booted to the Sato graphical desktop.
-
-If you want a terminal, use the arrows at the top of the UI to move
to -different pages of available applications, one of which is named
-'Terminal'. Clicking that should give you a root terminal.
-
-If you want to ssh into the system, you can use the root terminal to
-ifconfig the IP address and use that to ssh in. The root password is
-empty, so to log in type 'root' for the user name and hit 'Enter' at
-the Password prompt: and you should be in.
-
-----
-
-If you find you're getting corrupt images on the USB (it doesn't show
-the syslinux boot: prompt, or the boot: prompt contains strange
-characters), try doing this first:
-
-# dd if=/dev/zero of=/dev/sdf bs=1M count=512 diff --git
a/meta-fishriver/README.sources b/meta-fishriver/README.sources
deleted file mode 100644 index 76180f1..0000000
--- a/meta-fishriver/README.sources
+++ /dev/null
@@ -1,17 +0,0 @@
-The sources for the packages comprising the images shipped with this
-BSP can be found at the following location:
-
-http://downloads.yoctoproject.org/mirror/sources/
-
-The metadata used to generate the images shipped with this BSP, in
-addition to the code contained in this BSP, can be found at the
-following location:
-
-http://www.yoctoproject.org/downloads/yocto-1.2/poky-denzil-7.0.tar.b
z2
-
-The metadata used to generate the images shipped with this BSP, in
-addition to the code contained in this BSP, can also be found at the
-following locations:
-
-git://git.yoctoproject.org/poky.git
-git://git.yoctoproject.org/meta-intel
diff --git a/meta-fishriver/binary/.gitignore
b/meta-fishriver/binary/.gitignore
deleted file mode 100644
index e69de29..0000000
diff --git a/meta-fishriver/conf/layer.conf
b/meta-fishriver/conf/layer.conf deleted file mode 100644 index
61e292b..0000000
--- a/meta-fishriver/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
-# We have a conf and classes directory, add to BBPATH -BBPATH :=
"${BBPATH}:${LAYERDIR}"
-
-# We have a recipes directory, add to BBFILES -BBFILES := "${BBFILES}
${LAYERDIR}/recipes-*/*/*.bb \
- ${LAYERDIR}/recipes-*/*/*.bbappend"
-
-BBFILE_COLLECTIONS += "fishriver"
-BBFILE_PATTERN_fishriver := "^${LAYERDIR}/"
-BBFILE_PRIORITY_fishriver = "6"
-
-LAYERDEPENDS_fishriver = "intel"
diff --git a/meta-fishriver/conf/machine/fishriver.conf
b/meta-fishriver/conf/machine/fishriver.conf
deleted file mode 100644
index ec2e87f..0000000
--- a/meta-fishriver/conf/machine/fishriver.conf
+++ /dev/null
@@ -1,17 +0,0 @@
-#@TYPE: Machine
-#@NAME: fishriver
-
-#@DESCRIPTION: Machine configuration for Fish River Island systems -#
i.e. Z530/E660 + EG20T
-
-PREFERRED_VERSION_linux-yocto ?= "3.4%"
-
-require conf/machine/include/tune-atom.inc
-require conf/machine/include/ia32-base.inc
-
-XSERVER ?= "${XSERVER_IA32_BASE} \
- ${XSERVER_IA32_EXT} \
- ${XSERVER_IA32_VESA} \
- "
-
-APPEND += "video=vesafb vga=0x318"
diff --git
a/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfi
g
b/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfi
g
deleted file mode 100644
index ffce012..0000000
---
a/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfi
g
+++ /dev/null
@@ -1,3 +0,0 @@
-# Assume a USB mouse and keyboard are connected
-HAVE_TOUCHSCREEN=0
-HAVE_KEYBOARD=1
diff --git
a/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
b/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 54da0ff..0000000
--- a/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1,3 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-PRINC = "1"
diff --git
a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fis
hriver/xorg.conf
b/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fis
hriver/xorg.conf
deleted file mode 100644
index da4fc3c..0000000
---
a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fis
hriver/xorg.conf
+++ /dev/null
@@ -1,26 +0,0 @@
-Section "Device"
- Identifier "Generic VESA"
- Driver "vesa"
-EndSection
-
-Section "Monitor"
- Identifier "Generic Monitor"
- Option "DPMS"
-EndSection
-
-Section "Screen"
- Identifier "Default Screen"
- Device "Generic VESA"
- Monitor "Generic Monitor"
- DefaultDepth 24
-EndSection
-
-Section "ServerLayout"
- Identifier "Default Layout"
- Screen "Default Screen"
-EndSection
-
-Section "ServerFlags"
- Option "DontZap" "0"
- Option "AutoAddDevices" "False"
-EndSection
diff --git
a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1
.bbappend
b/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1
.bbappend
deleted file mode 100644
index 72d991c..0000000
---
a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1
.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git
a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
b/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
deleted file mode 100644
index 7a502bd..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-
-# Update the following to use a different BSP branch or meta SRCREV
-#KBRANCH_fishriver = "yocto/standard/preempt-rt/base"
-#SRCREV_machine_pn-linux-yocto-rt_fishriver ?= XXXX
-#SRCREV_meta_pn-linux-yocto-rt_fishriver ?= XXXX diff --git
a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
b/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
deleted file mode 100644
index a91a425..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-
-# Update the following to use a different BSP branch or meta SRCREV
-#KBRANCH_fishriver = "standard/preempt-rt/base"
-#SRCREV_machine_pn-linux-yocto-rt_fishriver ?= XXXX
-#SRCREV_meta_pn-linux-yocto-rt_fishriver ?= XXXX diff --git
a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
deleted file mode 100644
index 6ac6ef5..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
+++ /dev/null
@@ -1,9 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-KBRANCH_fishriver = "yocto/standard/fishriver"
-KERNEL_FEATURES_append_fishriver += " cfg/smp.scc"
-
-SRCREV_machine_pn-linux-yocto_fishriver ?=
"c139592c96722727a9f074515a4061c3820da1a6"
-SRCREV_meta_pn-linux-yocto_fishriver ?=
"59314a3523e360796419d76d78c6f7d8c5ef2593"
diff --git
a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
deleted file mode 100644
index 9a2f678..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-KBRANCH_fishriver = "standard/default/fishriver"
-
-SRCREV_machine_pn-linux-yocto_fishriver ?=
"969edd015a46eed77d6c3daeffdc299dd06e3397"
-SRCREV_meta_pn-linux-yocto_fishriver ?=
"5b4c9dc78b5ae607173cc3ddab9bce1b5f78129b"
diff --git
a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
deleted file mode 100644
index c0d04dc..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-KBRANCH_fishriver = "standard/fishriver"
-
-SRCREV_machine_pn-linux-yocto_fishriver ?=
"3fa06aa29078fdb2af431de2d3fdae7d281ba85f"
-SRCREV_meta_pn-linux-yocto_fishriver ?=
"5bdc655034a58a7147176a8a882d81e2fd51e4b9"


Re: [PATCHv2 4/5] fishriver BSP retirement

Kamble, Nitin A <nitin.a.kamble@...>
 

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@...]
Sent: Wednesday, October 10, 2012 2:07 PM
To: Kamble, Nitin A
Cc: Zanussi, Tom; Hart, Darren; yocto@...
Subject: Re: [yocto] [PATCHv2 4/5] fishriver BSP retirement

On 12-10-09 09:16 PM, nitin.a.kamble@... wrote:
From: Nitin A Kamble<nitin.a.kamble@...>

This commit removes fishriver bsp from meta-intel layer.

Fish-River-Islnad-2 hardware and BSP has made this
Fish-River-Island hardware and BSP absolute.
Also we discussed this on the Yocto Execution Tracking Meeting, and
to our knowledge no customer is using (cares about) this BSP now.
Just so I don't forget, can you send a patch that also removes the kernel
meta data for the BSP ? That way I won't recreate the branch for future
releases :)
Removing the FRI-1 contents from meta branch of v3.4 kernel tree should be ok because it preserves the old commits.
But I think we will have to leave the topic branch for fishriver machine as it is.

I assume it is ok that the kernel branches stay in the 3.x kernels for the yocto
1.3 release ?
I also think that is the right way to handle it.

Regards,
Nitin


Cheers,

Bruce


Signed-off-by: Nitin A Kamble<nitin.a.kamble@...>
---
MAINTAINERS | 4 -
meta-fishriver/COPYING.MIT | 17 ---
meta-fishriver/README | 114 --------------------
meta-fishriver/README.sources | 17 ---
meta-fishriver/conf/layer.conf | 12 --
meta-fishriver/conf/machine/fishriver.conf | 17 ---
.../formfactor/formfactor/fishriver/machconfig | 3 -
.../recipes-bsp/formfactor/formfactor_0.0.bbappend | 3 -
.../xserver-xf86-config/fishriver/xorg.conf | 26 -----
.../xorg-xserver/xserver-xf86-config_0.1.bbappend | 1 -
.../linux/linux-yocto-rt_3.0.bbappend | 8 --
.../linux/linux-yocto-rt_3.2.bbappend | 8 --
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 9 --
.../recipes-kernel/linux/linux-yocto_3.2.bbappend | 8 --
.../recipes-kernel/linux/linux-yocto_3.4.bbappend | 8 --
15 files changed, 0 insertions(+), 255 deletions(-)
delete mode 100644 meta-fishriver/COPYING.MIT
delete mode 100644 meta-fishriver/README
delete mode 100644 meta-fishriver/README.sources
delete mode 100644 meta-fishriver/binary/.gitignore
delete mode 100644 meta-fishriver/conf/layer.conf
delete mode 100644 meta-fishriver/conf/machine/fishriver.conf
delete mode 100644 meta-fishriver/recipes-
bsp/formfactor/formfactor/fishriver/machconfig
delete mode 100644 meta-fishriver/recipes-
bsp/formfactor/formfactor_0.0.bbappend
delete mode 100644 meta-fishriver/recipes-graphics/xorg-
xserver/xserver-xf86-config/fishriver/xorg.conf
delete mode 100644 meta-fishriver/recipes-graphics/xorg-
xserver/xserver-xf86-config_0.1.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-
rt_3.0.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto-
rt_3.2.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-
yocto_3.0.bbappend
delete mode 100644 meta-fishriver/recipes-kernel/linux/linux-
yocto_3.2.bbappend
delete mode 100644
meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend

diff --git a/MAINTAINERS b/MAINTAINERS index 5bcf470..3bf0add 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -56,10 +56,6 @@ EMENLOW
M: Tom Zanussi<tom.zanussi@...>
F: meta-emenlow/

-FISHRIVER
-M: Tom Zanussi<tom.zanussi@...>
-F: meta-fishriver/
-
FRI2
M: Darren Hart<dvhart@...>
F: meta-fri2/
diff --git a/meta-fishriver/COPYING.MIT b/meta-fishriver/COPYING.MIT
deleted file mode 100644 index fb950dc..0000000
--- a/meta-fishriver/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
-Permission is hereby granted, free of charge, to any person obtaining
a copy -of this software and associated documentation files (the
"Software"), to deal -in the Software without restriction, including
without limitation the rights -to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell -copies of the Software, and to
permit persons to whom the Software is -furnished to do so, subject to the
following conditions:
-
-The above copyright notice and this permission notice shall be
included in -all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF
MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT
HOLDERS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN
AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR
IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN -
THE SOFTWARE.
diff --git a/meta-fishriver/README b/meta-fishriver/README deleted
file mode 100644 index 1dd0a4c..0000000
--- a/meta-fishriver/README
+++ /dev/null
@@ -1,114 +0,0 @@
-This README file contains information on building the meta-fishriver
-BSP layer, and booting the images contained in the /binary directory.
-Please see the corresponding sections below for details.
-
-
-Dependencies
-============
-
-This layer depends on:
-
- URI: git://git.openembedded.org/bitbake
- branch: master
-
- URI: git://git.openembedded.org/openembedded-core
- layers: meta
- branch: master
-
- URI: git://git.yoctoproject.org/meta-intel
- layers: intel
- branch: master
-
-
-Patches
-=======
-
-Please submit any patches against this BSP to the Yocto mailing list
-(yocto@...) and cc: the maintainer:
-
-Maintainer: Tom Zanussi<tom.zanussi@...>
-
-Please see the meta-intel/MAINTAINERS file for more details.
-
-
-Table of Contents
-=================
-
- I. Building the meta-fishriver BSP layer
- II. Booting the images in /binary
-
-
-I. Building the meta-fishriver BSP layer
-========================================
-
-In order to build an image with BSP support for a given release, you
-need to download the corresponding BSP tarball from the 'Board
Support -Package (BSP) Downloads' page of the Yocto Project website.
-
-Having done that, and assuming you extracted the BSP tarball contents
-at the top-level of your yocto build tree, you can build a fishriver
-image by adding the location of the meta-fishriver layer to
-bblayers.conf, along with the meta-intel layer itself (to access
-common metadata shared between BSPs) e.g.:
-
- yocto/meta-intel \
- yocto/meta-intel/meta-fishriver \
-
-To enable the fishriver layer, add the fishriver MACHINE to local.conf:
-
- MACHINE ?= "fishriver"
-
-You should then be able to build a fishriver image as such:
-
- $ source oe-init-build-env
- $ bitbake core-image-sato
-
-At the end of a successful build, you should have a live image that
-you can boot from a USB flash drive (see instructions on how to do
-that below, in the section 'Booting the images from /binary').
-
-As an alternative to downloading the BSP tarball, you can also work
-directly from the meta-intel git repository. For each BSP in the
-'meta-intel' repository, there are multiple branches, one
-corresponding to each major release starting with 'laverne' (0.90),
in -addition to the latest code which tracks the current master (note
that -not all BSPs are present in every release). Instead of
extracting a -BSP tarball at the top level of your yocto build tree,
you can -equivalently check out the appropriate branch from the
meta-intel -repository at the same location.
-
-
-II. Booting the images in /binary
-=================================
-
-This BSP contains bootable live images, which can be used to directly
-boot Yocto off of a USB flash drive.
-
-Under Linux, insert a USB flash drive. Assuming the USB flash drive
-takes device /dev/sdf, use dd to copy the live image to it. For
-example:
-
-# dd if=core-image-sato-fishriver-20101207053738.hddimg of=/dev/sdf
-# sync -# eject /dev/sdf
-
-This should give you a bootable USB flash device. Insert the device
-into a bootable USB socket on the target, and power on. This should
-result in a system booted to the Sato graphical desktop.
-
-If you want a terminal, use the arrows at the top of the UI to move
to -different pages of available applications, one of which is named
-'Terminal'. Clicking that should give you a root terminal.
-
-If you want to ssh into the system, you can use the root terminal to
-ifconfig the IP address and use that to ssh in. The root password is
-empty, so to log in type 'root' for the user name and hit 'Enter' at
-the Password prompt: and you should be in.
-
-----
-
-If you find you're getting corrupt images on the USB (it doesn't show
-the syslinux boot: prompt, or the boot: prompt contains strange
-characters), try doing this first:
-
-# dd if=/dev/zero of=/dev/sdf bs=1M count=512 diff --git
a/meta-fishriver/README.sources b/meta-fishriver/README.sources
deleted file mode 100644 index 76180f1..0000000
--- a/meta-fishriver/README.sources
+++ /dev/null
@@ -1,17 +0,0 @@
-The sources for the packages comprising the images shipped with this
-BSP can be found at the following location:
-
-http://downloads.yoctoproject.org/mirror/sources/
-
-The metadata used to generate the images shipped with this BSP, in
-addition to the code contained in this BSP, can be found at the
-following location:
-
-http://www.yoctoproject.org/downloads/yocto-1.2/poky-denzil-7.0.tar.b
z2
-
-The metadata used to generate the images shipped with this BSP, in
-addition to the code contained in this BSP, can also be found at the
-following locations:
-
-git://git.yoctoproject.org/poky.git
-git://git.yoctoproject.org/meta-intel
diff --git a/meta-fishriver/binary/.gitignore
b/meta-fishriver/binary/.gitignore
deleted file mode 100644
index e69de29..0000000
diff --git a/meta-fishriver/conf/layer.conf
b/meta-fishriver/conf/layer.conf deleted file mode 100644 index
61e292b..0000000
--- a/meta-fishriver/conf/layer.conf
+++ /dev/null
@@ -1,12 +0,0 @@
-# We have a conf and classes directory, add to BBPATH -BBPATH :=
"${BBPATH}:${LAYERDIR}"
-
-# We have a recipes directory, add to BBFILES -BBFILES := "${BBFILES}
${LAYERDIR}/recipes-*/*/*.bb \
- ${LAYERDIR}/recipes-*/*/*.bbappend"
-
-BBFILE_COLLECTIONS += "fishriver"
-BBFILE_PATTERN_fishriver := "^${LAYERDIR}/"
-BBFILE_PRIORITY_fishriver = "6"
-
-LAYERDEPENDS_fishriver = "intel"
diff --git a/meta-fishriver/conf/machine/fishriver.conf
b/meta-fishriver/conf/machine/fishriver.conf
deleted file mode 100644
index ec2e87f..0000000
--- a/meta-fishriver/conf/machine/fishriver.conf
+++ /dev/null
@@ -1,17 +0,0 @@
-#@TYPE: Machine
-#@NAME: fishriver
-
-#@DESCRIPTION: Machine configuration for Fish River Island systems -#
i.e. Z530/E660 + EG20T
-
-PREFERRED_VERSION_linux-yocto ?= "3.4%"
-
-require conf/machine/include/tune-atom.inc
-require conf/machine/include/ia32-base.inc
-
-XSERVER ?= "${XSERVER_IA32_BASE} \
- ${XSERVER_IA32_EXT} \
- ${XSERVER_IA32_VESA} \
- "
-
-APPEND += "video=vesafb vga=0x318"
diff --git
a/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfi
g
b/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfi
g
deleted file mode 100644
index ffce012..0000000
---
a/meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfi
g
+++ /dev/null
@@ -1,3 +0,0 @@
-# Assume a USB mouse and keyboard are connected
-HAVE_TOUCHSCREEN=0
-HAVE_KEYBOARD=1
diff --git
a/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
b/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
deleted file mode 100644
index 54da0ff..0000000
--- a/meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
+++ /dev/null
@@ -1,3 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-PRINC = "1"
diff --git
a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fis
hriver/xorg.conf
b/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fis
hriver/xorg.conf
deleted file mode 100644
index da4fc3c..0000000
---
a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fis
hriver/xorg.conf
+++ /dev/null
@@ -1,26 +0,0 @@
-Section "Device"
- Identifier "Generic VESA"
- Driver "vesa"
-EndSection
-
-Section "Monitor"
- Identifier "Generic Monitor"
- Option "DPMS"
-EndSection
-
-Section "Screen"
- Identifier "Default Screen"
- Device "Generic VESA"
- Monitor "Generic Monitor"
- DefaultDepth 24
-EndSection
-
-Section "ServerLayout"
- Identifier "Default Layout"
- Screen "Default Screen"
-EndSection
-
-Section "ServerFlags"
- Option "DontZap" "0"
- Option "AutoAddDevices" "False"
-EndSection
diff --git
a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1
.bbappend
b/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1
.bbappend
deleted file mode 100644
index 72d991c..0000000
---
a/meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1
.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
diff --git
a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
b/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
deleted file mode 100644
index 7a502bd..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-
-# Update the following to use a different BSP branch or meta SRCREV
-#KBRANCH_fishriver = "yocto/standard/preempt-rt/base"
-#SRCREV_machine_pn-linux-yocto-rt_fishriver ?= XXXX
-#SRCREV_meta_pn-linux-yocto-rt_fishriver ?= XXXX diff --git
a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
b/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
deleted file mode 100644
index a91a425..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-
-# Update the following to use a different BSP branch or meta SRCREV
-#KBRANCH_fishriver = "standard/preempt-rt/base"
-#SRCREV_machine_pn-linux-yocto-rt_fishriver ?= XXXX
-#SRCREV_meta_pn-linux-yocto-rt_fishriver ?= XXXX diff --git
a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
deleted file mode 100644
index 6ac6ef5..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.0.bbappend
+++ /dev/null
@@ -1,9 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-KBRANCH_fishriver = "yocto/standard/fishriver"
-KERNEL_FEATURES_append_fishriver += " cfg/smp.scc"
-
-SRCREV_machine_pn-linux-yocto_fishriver ?=
"c139592c96722727a9f074515a4061c3820da1a6"
-SRCREV_meta_pn-linux-yocto_fishriver ?=
"59314a3523e360796419d76d78c6f7d8c5ef2593"
diff --git
a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
deleted file mode 100644
index 9a2f678..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-KBRANCH_fishriver = "standard/default/fishriver"
-
-SRCREV_machine_pn-linux-yocto_fishriver ?=
"969edd015a46eed77d6c3daeffdc299dd06e3397"
-SRCREV_meta_pn-linux-yocto_fishriver ?=
"5b4c9dc78b5ae607173cc3ddab9bce1b5f78129b"
diff --git
a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
deleted file mode 100644
index c0d04dc..0000000
--- a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-COMPATIBLE_MACHINE_fishriver = "fishriver"
-KMACHINE_fishriver = "fishriver"
-KBRANCH_fishriver = "standard/fishriver"
-
-SRCREV_machine_pn-linux-yocto_fishriver ?=
"3fa06aa29078fdb2af431de2d3fdae7d281ba85f"
-SRCREV_meta_pn-linux-yocto_fishriver ?=
"5bdc655034a58a7147176a8a882d81e2fd51e4b9"


Re: [PATCHv2 2/5] crownbay.conf: specify the 8.0.4 version as preferred version of mesa-dri

Kamble, Nitin A <nitin.a.kamble@...>
 

-----Original Message-----
From: Burton, Ross [mailto:ross.burton@...]
Sent: Wednesday, October 10, 2012 2:25 AM
To: Kamble, Nitin A
Cc: Zanussi, Tom; Hart, Darren; yocto@...
Subject: Re: [yocto] [PATCHv2 2/5] crownbay.conf: specify the 8.0.4 version
as preferred version of mesa-dri

On 10 October 2012 02:16, <nitin.a.kamble@...> wrote:
Avoid following warnings while building crownbay BSPs:

NOTE: preferred version 7.11 of mesa-dri not available (for item
virtual/libgl)
NOTE: versions of mesa-dri available: 2:8.0.4
2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7
This is the preferred version in oe-core, so wouldn't it be easier to just drop
this preferred version line and avoid this repeating itself in the future?

Ross
Hi Ross,
The reason is we want to know if the version of mesa in oecore has changed or not. EMGD has specific needs of mesa, and in the testing we are not finding any issues with v8.0.4 of mesa. But that may not hold true for future versions of mesa, so we would like to pin the version here so we know that this version works as expected.

Nitin


Re: [PATCH 2/5] crownbay.conf: specify the 8.0.4 version as preferred version of mesa-dri

Kamble, Nitin A <nitin.a.kamble@...>
 

-----Original Message-----
From: Burton, Ross [mailto:ross.burton@...]
Sent: Wednesday, October 10, 2012 2:24 AM
To: Kamble, Nitin A
Cc: yocto@...; Zanussi, Tom; Hart, Darren
Subject: Re: [yocto] [PATCH 2/5] crownbay.conf: specify the 8.0.4 version as
preferred version of mesa-dri

Hi Nitin,

From what I understand, EMGD's Mesa driver will only work correctly with a
Mesa that matches exactly the configuration that was used to build EMGD, as
the driver interface isn't stable. Have you tested the GL support with more
than glxinfo?

Ross
Hi Ross,
I find that emgd driver itself is providing some of the mesa libraries & headers. And I could not find a match for those in any of the released mesa sources as well as mesa git repository. So I don't see a way to match mesa code exactly. If such mesa is available in closed source, I am not aware of it either.
So far I have tested with glxgears and glxinfo with the 8.0.4 version of mesa-dri. And I did not find any issues. And Tom has been testing the same way so far without any complaints. If there is something which can help things test further, it would be nice to add it to the poky tree; so that it can become part of standard tests, and QA also can use it.

Nitin


Re: Finding root cause of "host include and/or library paths were used"

Bodke, Kishore K <kishore.k.bodke@...>
 

-----Original Message-----
From: Chris Tapp [mailto:opensource@...]
Sent: Wednesday, October 10, 2012 2:34 PM
To: Bodke, Kishore K
Cc: yocto@... Project
Subject: Re: [yocto] Finding root cause of "host include and/or library paths
were used"


On 10 Oct 2012, at 20:51, Chris Tapp wrote:

On 10 Oct 2012, at 18:26, Bodke, Kishore K wrote:



-----Original Message-----
From: yocto-bounces@... [mailto:yocto-
bounces@...] On Behalf Of Chris Tapp
Sent: Wednesday, October 10, 2012 9:50 AM
To: yocto@... Project
Subject: [yocto] Finding root cause of "host include and/or library paths
were
used"

I'm trying to get libsdl_gfx to build. I've created a .bb file which runs and
installs the relevant headers and libs in tmp/sysroots.

However, I'm getting a QA failure:

NOTE: package libsdl-gfx-2.0.24-r1: task do_populate_sysroot: Succeeded
WARNING: libsdl-gfx: The compile log indicates that host include and/or
library
paths were used.
Please check the log '/media/SSD-RAID/build-denzil-git-sjs-
cedartrail/tmp/work/core2-sjs-linux/libsdl-gfx-2.0.24-
r1/temp/log.do_compile' for more information.

The compile log has instances of:

cc1: warning: include location "/usr/include/SDL" is unsafe for cross-
compilation [-Wpoison-system-directories]

The source uses autotools. I've had a look round the files, but it's not
obvious
to me where the above path is set (I'm definitely not an autotools
expert).
Can anyone give me an idea what I should be looking for? I suspect it may
have something to do with a line from Makefile.am:

libSDL_gfxincludedir = $(includedir)/SDL
Did you inherit autotools in your recipe?
Yes, that's in there.

You may have to patch your makefile not to use host header files.
Or, I think you can use ${STAGING_INCDIR} to override, at the time of your
configure.

Thanks. Are there any examples I can look at to see how to do this? I've not
been able to find which file I need to change after 'unpack'.

I seem to have 'fixed' it, but I'm not sure I understand how! I've added:

EXTRA_OECONF = "--prefix=/any-old-thing"

to the .bb file. No warnings, compile log shows the correct include path:

-I/media/SSD-RAID/build-denzil-git-sjs-cedartrail/tmp/sysroots/cedartrail-
nopvr/usr/include/SDL
Yeah, EXTRA_OECONF with ${STAGING_INCDIR} would do that I guess,
But not exactly sure with the syntax here.

You might want to take a look other recipes in poky using this I guess to find how it is done.

Thanks
Kishore.