Date   

[PATCH 4/7] add enable-dga to the xserver to get rid of DGAInit startup error

kishore.k.bodke@...
 

From: Tom Zanussi <tom.zanussi@...>

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
.../xorg-xserver/xserver-xorg_1.11.1.bbappend | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
create mode 100644 meta-romley/recipes-graphics/xorg-xserver/xserver-xorg_1.11.1.bbappend

diff --git a/meta-romley/recipes-graphics/xorg-xserver/xserver-xorg_1.11.1.bbappend b/meta-romley/recipes-graphics/xorg-xserver/xserver-xorg_1.11.1.bbappend
new file mode 100644
index 0000000..b2808ef
--- /dev/null
+++ b/meta-romley/recipes-graphics/xorg-xserver/xserver-xorg_1.11.1.bbappend
@@ -0,0 +1 @@
+EXTRA_OECONF += "--enable-dga"
--
1.7.5.4


[PATCH 3/7] meta-romley: xserver-xorg renaming updates

kishore.k.bodke@...
 

From: Tom Zanussi <tom.zanussi@...>

Update romley to reflect the new xserver-xorg naming.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-romley/conf/machine/romley.conf | 12 +++++++++---
.../xorg-driver/xf86-video-mga_1.4.13.bb | 2 +-
meta-sugarbay/conf/machine/sugarbay.conf | 4 +---
3 files changed, 11 insertions(+), 7 deletions(-)

diff --git a/meta-romley/conf/machine/romley.conf b/meta-romley/conf/machine/romley.conf
index 3fae18d..625fa60 100644
--- a/meta-romley/conf/machine/romley.conf
+++ b/meta-romley/conf/machine/romley.conf
@@ -17,9 +17,15 @@ PREFERRED_VERSION_linux-yocto = "3.0%"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"
PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
PREFERRED_PROVIDER_virtual/libgl ?= "mesa-dri"
-PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xf86-dri-lite"
-PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xf86-dri-lite"
-XSERVER ?= "xserver-xf86-dri-lite \
+PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
+PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xorg"
+XSERVER ?= "xserver-xorg \
+ xserver-xorg-extension-dri \
+ xserver-xorg-extension-dri2 \
+ xserver-xorg-extension-glx \
+ xserver-xorg-extension-extmod \
+ xserver-xorg-extension-dbe \
+ xserver-xorg-module-libint10 \
xf86-input-mouse \
xf86-input-keyboard \
xf86-input-evdev \
diff --git a/meta-romley/recipes-graphics/xorg-driver/xf86-video-mga_1.4.13.bb b/meta-romley/recipes-graphics/xorg-driver/xf86-video-mga_1.4.13.bb
index 9905a28..b48e56d 100755
--- a/meta-romley/recipes-graphics/xorg-driver/xf86-video-mga_1.4.13.bb
+++ b/meta-romley/recipes-graphics/xorg-driver/xf86-video-mga_1.4.13.bb
@@ -1,4 +1,4 @@
-require recipes-graphics/xorg-driver/xf86-video-common.inc
+require recipes-graphics/xorg-driver/xorg-driver-video.inc

SUMMARY = "X.Org X server -- Matrox MGA display driver"

diff --git a/meta-sugarbay/conf/machine/sugarbay.conf b/meta-sugarbay/conf/machine/sugarbay.conf
index 3ea9ca3..c606cf4 100644
--- a/meta-sugarbay/conf/machine/sugarbay.conf
+++ b/meta-sugarbay/conf/machine/sugarbay.conf
@@ -30,9 +30,7 @@ XSERVER ?= "xserver-xorg \
xf86-input-keyboard \
xf86-input-evdev \
xf86-input-synaptics \
- xf86-video-intel \
- mesa-dri \
- mesa-dri-driver-i965"
+ mesa-dri"

SERIAL_CONSOLE = "115200 ttyS0"

--
1.7.5.4


[PATCH 2/7] meta-romley: remove meta-intel/common from BBFILES

kishore.k.bodke@...
 

From: Tom Zanussi <tom.zanussi@...>

There's nothing in meta-intel/common used by romley, and is too broad
anyway, so remove it from BBFILES.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-romley/conf/layer.conf | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)

diff --git a/meta-romley/conf/layer.conf b/meta-romley/conf/layer.conf
index f9dd569..c5eeaab 100644
--- a/meta-romley/conf/layer.conf
+++ b/meta-romley/conf/layer.conf
@@ -3,9 +3,7 @@ BBPATH := "${BBPATH}:${LAYERDIR}"

# We have a recipes directory, add to BBFILES
BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
- ${LAYERDIR}/recipes-*/*/*.bbappend \
- ${LAYERDIR}/../common/recipes-*/*/*.bb \
- ${LAYERDIR}/../common/recipes-*/*/*.bbappend"
+ ${LAYERDIR}/recipes-*/*/*.bbappend"

BBFILE_COLLECTIONS += "romley"
BBFILE_PATTERN_romley := "^${LAYERDIR}/"
--
1.7.5.4


[PATCH 1/7] New Romley BSP added.

kishore.k.bodke@...
 

From: Kishore Bodke <kishore.k.bodke@...>

---
meta-romley/COPYING.MIT | 17 ++++
meta-romley/README | 86 ++++++++++++++++++++
meta-romley/README.sources | 17 ++++
meta-romley/conf/layer.conf | 12 +++
meta-romley/conf/machine/romley.conf | 41 +++++++++
.../formfactor/formfactor/romley/machconfig | 3 +
.../recipes-bsp/formfactor/formfactor_0.0.bbappend | 3 +
.../recipes-core/tasks/task-core-tools.bbappend | 2 +
.../xorg-driver/xf86-video-mga_1.4.13.bb | 19 +++++
.../xserver-xf86-config/romley/xorg.conf | 26 ++++++
.../xorg-xserver/xserver-xf86-config_0.1.bbappend | 3 +
.../linux/linux-yocto-rt_3.0.bbappend | 8 ++
.../linux/linux-yocto_2.6.37.bbappend | 7 ++
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 7 ++
14 files changed, 251 insertions(+), 0 deletions(-)
create mode 100644 meta-romley/COPYING.MIT
create mode 100644 meta-romley/README
create mode 100644 meta-romley/README.sources
create mode 100644 meta-romley/binary/.gitignore
create mode 100644 meta-romley/conf/layer.conf
create mode 100644 meta-romley/conf/machine/romley.conf
create mode 100644 meta-romley/recipes-bsp/formfactor/formfactor/romley/machconfig
create mode 100644 meta-romley/recipes-bsp/formfactor/formfactor_0.0.bbappend
create mode 100644 meta-romley/recipes-core/tasks/task-core-tools.bbappend
create mode 100755 meta-romley/recipes-graphics/xorg-driver/xf86-video-mga_1.4.13.bb
create mode 100644 meta-romley/recipes-graphics/xorg-xserver/xserver-xf86-config/romley/xorg.conf
create mode 100644 meta-romley/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
create mode 100644 meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
create mode 100644 meta-romley/recipes-kernel/linux/linux-yocto_2.6.37.bbappend
create mode 100644 meta-romley/recipes-kernel/linux/linux-yocto_3.0.bbappend

diff --git a/meta-romley/COPYING.MIT b/meta-romley/COPYING.MIT
new file mode 100644
index 0000000..fb950dc
--- /dev/null
+++ b/meta-romley/COPYING.MIT
@@ -0,0 +1,17 @@
+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-romley/README b/meta-romley/README
new file mode 100644
index 0000000..54776bf
--- /dev/null
+++ b/meta-romley/README
@@ -0,0 +1,86 @@
+This README file contains information on building the meta-romley
+BSP layer, and booting the images contained in the /binary directory.
+Please see the corresponding sections below for details.
+
+The 'romley' platform consists of the Intel Sandy Bridge processor,
+plus the Patsburg chipset. This BSP assumes Matrox graphics is being used.
+
+Table of Contents
+=================
+
+ I. Building the meta-romley BSP layer
+ II. Booting the images in /binary
+
+
+I. Building the meta-romley 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 romley
+image by adding the location of the meta-romley layer to
+bblayers.conf e.g.:
+
+ yocto/meta-intel/meta-romley \
+
+To enable the romley layer, add the romley MACHINE to local.conf:
+
+ MACHINE ?= "romley"
+
+You should then be able to build a romley 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-romley-20111007220323.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-romley/README.sources b/meta-romley/README.sources
new file mode 100644
index 0000000..8e006fb
--- /dev/null
+++ b/meta-romley/README.sources
@@ -0,0 +1,17 @@
+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.1/poky-edison-6.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-romley/binary/.gitignore b/meta-romley/binary/.gitignore
new file mode 100644
index 0000000..e69de29
diff --git a/meta-romley/conf/layer.conf b/meta-romley/conf/layer.conf
new file mode 100644
index 0000000..f9dd569
--- /dev/null
+++ b/meta-romley/conf/layer.conf
@@ -0,0 +1,12 @@
+# 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 \
+ ${LAYERDIR}/../common/recipes-*/*/*.bb \
+ ${LAYERDIR}/../common/recipes-*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "romley"
+BBFILE_PATTERN_romley := "^${LAYERDIR}/"
+BBFILE_PRIORITY_romley = "6"
diff --git a/meta-romley/conf/machine/romley.conf b/meta-romley/conf/machine/romley.conf
new file mode 100644
index 0000000..3fae18d
--- /dev/null
+++ b/meta-romley/conf/machine/romley.conf
@@ -0,0 +1,41 @@
+#@TYPE: Machine
+#@NAME: romley
+
+#@DESCRIPTION: Machine configuration for Sugar Bay systems
+# i.e. Sandy Bridge + Patsburg Chipset
+
+require conf/machine/include/tune-x86_64.inc
+
+MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
+ acpi serial usbgadget"
+
+KERNEL_IMAGETYPE = "bzImage"
+
+PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
+PREFERRED_VERSION_linux-yocto = "3.0%"
+
+PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"
+PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
+PREFERRED_PROVIDER_virtual/libgl ?= "mesa-dri"
+PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xf86-dri-lite"
+PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xf86-dri-lite"
+XSERVER ?= "xserver-xf86-dri-lite \
+ xf86-input-mouse \
+ xf86-input-keyboard \
+ xf86-input-evdev \
+ xf86-input-synaptics \
+ xf86-video-mga \
+ xf86-video-intel \
+ mesa-dri \
+ mesa-dri-driver-i965"
+
+SERIAL_CONSOLE = "115200 ttyS0"
+
+MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts"
+
+IMAGE_FSTYPES ?= "ext3 cpio.gz live"
+
+GLIBC_ADDONS = "nptl"
+GLIBC_EXTRA_OECONF = "--with-tls"
+
+MACHINE_ESSENTIAL_EXTRA_RDEPENDS = "grub"
diff --git a/meta-romley/recipes-bsp/formfactor/formfactor/romley/machconfig b/meta-romley/recipes-bsp/formfactor/formfactor/romley/machconfig
new file mode 100644
index 0000000..ffce012
--- /dev/null
+++ b/meta-romley/recipes-bsp/formfactor/formfactor/romley/machconfig
@@ -0,0 +1,3 @@
+# Assume a USB mouse and keyboard are connected
+HAVE_TOUCHSCREEN=0
+HAVE_KEYBOARD=1
diff --git a/meta-romley/recipes-bsp/formfactor/formfactor_0.0.bbappend b/meta-romley/recipes-bsp/formfactor/formfactor_0.0.bbappend
new file mode 100644
index 0000000..54da0ff
--- /dev/null
+++ b/meta-romley/recipes-bsp/formfactor/formfactor_0.0.bbappend
@@ -0,0 +1,3 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+PRINC = "1"
diff --git a/meta-romley/recipes-core/tasks/task-core-tools.bbappend b/meta-romley/recipes-core/tasks/task-core-tools.bbappend
new file mode 100644
index 0000000..aba487f
--- /dev/null
+++ b/meta-romley/recipes-core/tasks/task-core-tools.bbappend
@@ -0,0 +1,2 @@
+RRECOMMENDS_task-core-tools-profile_append_romley = " systemtap"
+
diff --git a/meta-romley/recipes-graphics/xorg-driver/xf86-video-mga_1.4.13.bb b/meta-romley/recipes-graphics/xorg-driver/xf86-video-mga_1.4.13.bb
new file mode 100755
index 0000000..9905a28
--- /dev/null
+++ b/meta-romley/recipes-graphics/xorg-driver/xf86-video-mga_1.4.13.bb
@@ -0,0 +1,19 @@
+require recipes-graphics/xorg-driver/xf86-video-common.inc
+
+SUMMARY = "X.Org X server -- Matrox MGA display driver"
+
+DESCRIPTION = "mga is an Xorg driver for Matrox video cards"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=bc1395d2cd32dfc5d6c57d2d8f83d3fc"
+
+DEPENDS += "virtual/libx11 libxvmc drm xf86driproto glproto \
+ virtual/libgl xineramaproto libpciaccess"
+
+EXTRA_OECONF += "--enable-dri"
+
+PR = "r0"
+
+COMPATIBLE_HOST = '(i.86.*-linux|x86_64.*-linux)'
+
+SRC_URI[md5sum] = "f967fb3e655f6f68aa3f495eaadcaac2"
+SRC_URI[sha256sum] = "b657bd5fec4aade6396c683886739b7c8ce57924278bee0e36f13a966eeddff6"
diff --git a/meta-romley/recipes-graphics/xorg-xserver/xserver-xf86-config/romley/xorg.conf b/meta-romley/recipes-graphics/xorg-xserver/xserver-xf86-config/romley/xorg.conf
new file mode 100644
index 0000000..28ad0bf
--- /dev/null
+++ b/meta-romley/recipes-graphics/xorg-xserver/xserver-xf86-config/romley/xorg.conf
@@ -0,0 +1,26 @@
+Section "Device"
+ Identifier "Matrox MGA"
+ Driver "mga"
+EndSection
+
+Section "Monitor"
+ Identifier "Generic Monitor"
+ Option "DPMS"
+EndSection
+
+Section "Screen"
+ Identifier "Default Screen"
+ Device "Matrox MGA"
+ 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-romley/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend b/meta-romley/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
new file mode 100644
index 0000000..4b8d0e6
--- /dev/null
+++ b/meta-romley/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
@@ -0,0 +1,3 @@
+THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
+FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}"], d)}:"
+
diff --git a/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend b/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
new file mode 100644
index 0000000..d630dc4
--- /dev/null
+++ b/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
@@ -0,0 +1,8 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+COMPATIBLE_MACHINE_romley = "romley"
+KMACHINE_romley = "romley"
+
+# Update the following to use a different BSP branch or meta SRCREV
+#KBRANCH_sugarbay = "yocto/standard/preempt-rt/base"
+#SRCREV_machine_pn-linux-yocto-rt_sugarbay ?= XXXX
+#SRCREV_meta_pn-linux-yocto-rt_sugarbay ?= XXXX
diff --git a/meta-romley/recipes-kernel/linux/linux-yocto_2.6.37.bbappend b/meta-romley/recipes-kernel/linux/linux-yocto_2.6.37.bbappend
new file mode 100644
index 0000000..e48f8b0
--- /dev/null
+++ b/meta-romley/recipes-kernel/linux/linux-yocto_2.6.37.bbappend
@@ -0,0 +1,7 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_sugarbay = "romley"
+KMACHINE_romley = "yocto/standard/common-pc-64/romley"
+
+SRCREV_machine_pn-linux-yocto_romley ?= "7f495be2ccaa209bf505b8a8899cea64cfd968bb"
+SRCREV_meta_pn-linux-yocto_romley ?= "d5d3c6480d61f83503ccef7fbcd765f7aca8b71b"
diff --git a/meta-romley/recipes-kernel/linux/linux-yocto_3.0.bbappend b/meta-romley/recipes-kernel/linux/linux-yocto_3.0.bbappend
new file mode 100644
index 0000000..9a1d252
--- /dev/null
+++ b/meta-romley/recipes-kernel/linux/linux-yocto_3.0.bbappend
@@ -0,0 +1,7 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_romley = "romley"
+KMACHINE_romley = "yocto/standard/common-pc-64/romley"
+
+SRCREV_machine_pn-linux-yocto_romley ?= "dbe820c277dfa6cbc249d410e8b083286ec484b7"
+SRCREV_meta_pn-linux-yocto_romley ?= "d05450e4aef02c1b7137398ab3a9f8f96da74f52"
--
1.7.5.4


prelink-cross project sync update

Mark Hatle <mark.hatle@...>
 

(I'm going to try to send out these quick blurbs as prelink-cross is synced to
the upstream. Upstream changes are fairly infrequent, so this will be a low
volume set of emails. Most emails in the future will be shorted then this one.)

prelink-cross has been synced up to the latest upstream prelink changes.

The latest changes include:

2011-10-12 Jakub Jelinek <jakub@...>

* src/main.c (layout_page_size): New variable.
(OPT_LAYOUT_PAGE_SIZE): Define.
(options): Add --layout-page-size option.
(set_default_layout_page_size): New function in i?86/x86_64
resp. empty macro on other architectures.
(main): Call it.
* src/arch-i386.c (i386_layout_libs_init): Fail if
l->max_page_size is larger than 2MB and exec_shield is true.
Compute reg0s as REG0S rounded up to l->max_page_size
boundary and use it instead of REG0S.
(i386_layout_libs_pre): Compute reg0s as REG0S rounded up to
l->max_page_size boundary and use it instead of REG0S.
Fix up a pasto in computation of virt parameter for
third i386_find_free_addr call.
* src/prelink.h (layout_page_size): New decl.
* src/layout.c (layout_libs): Set max_page_size and
l.max_page_size to maximum of plarch->max_page_size
and layout_page_size. Fail if mmap_base or mmap_end
aren't max_page_size aligned.
* src/arch-ppc.c (ppc_layout_libs_pre): Give up if
l->max_page_size is larger than 64KB.

In essence what this does is adds a new option "--layout-page-size" that allows
someone to override the "max_page_size" value when necessary. (It's not a true
override as the max_page_size is set to either the existing value or
layout-page-size whichever is larger.)

The upstream change also added dynamic run-time detection for the AMD Bulldozer
platform, setting the default to 32k. Since run-time detection is contrary to
the existing prelink-cross usage, the code has been disabled.

As usual, the upstream version is in the "master" branch, and the cross version
is in the "cross_prelink" branch.

--Mark


Results of the latest documentation audit, October 2011

Scott Garman <scott.a.garman@...>
 

Hello,

Here are the results of the latest documentation audit, using a recent Poky master (72a1e63b67445c65954c21f5cbfab74d617a257f):

587 recipes in total
334 recipes are building documentation
252 recipes are not building documentation

7 recipes did not build, and are counted above as "not building documentation"

For comparison, here were the results from my last audit (September 29):

589 recipes in total
324 recipes are building documentation
265 recipes are not building documentation

6 recipes did not build.

So progress continues to be made.

The lists of recipes are attached to this email. We'd like to improve the percentage of recipes that produce documentation (separated into -doc packages, of course) for our next major release (1.2, in April).

Our userspace recipe maintainers should look into setting aside some time to know which of their recipes are in the "not building documentation" list and work to improve them. A lot of this is likely to be low-hanging fruit, and is easy to do when upgrading your recipes.

Thanks,

Scott

--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center


Re: Eclipse Plugin: ADT Version too old

Zhang, Jessica
 

Jack,

 

I push out a support in Eclipse for post 1.1 (1.1+snapshort*), you can update your eclipse plug-in against latest eclipse-poky master following the steps in the ADT manual.  But it seems you still have some strange thing going on with your Edison build, it shouldn’t contain “1.1+snapshot*” as version for both distro and adt.

 

Cheers,

Jessica

 

From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Jack Mitchell
Sent: Wednesday, October 26, 2011 1:20 AM
Cc: yocto@...
Subject: Re: [yocto] Eclipse Plugin: ADT Version too old

 

On 25/10/2011 22:40, Flanagan, Elizabeth wrote:

On Tue, Oct 25, 2011 at 7:45 AM, Jack Mitchell <ml@...> wrote:
 
Hi Jessica,
 
I posted my environment settings earlier, which are located here:
http://pastebin.com/4vnWPAD2
 
Yes, I did use bitbake meta-ide-support to build my roo
 
Hi Jessica,
 
I just did a full fresh re-build from scratch and now my environment
variables are as follows:
 
http://ix.io/1Wf
 
My current git status is:
 
# On branch edision
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#    ../bitbake/lib/bb/pysh/pyshtables.py
#    ../conf/
#    ./
#    ../qemuarm-toolchain/
nothing added to commit but untracked files present (use "git add" to track)
 
Jack,
 
I just checked out a clean edison and ran bitbake meta-ide-support. My
env is showing export OECORE_DISTRO_VERSION="1.1". My guess is that,
since you are not in master, then you have a TMPDIR from a master
build, or perhaps are using something left over from one, as the only
place DISTRO_VERSION = "1.1+snapshot-${DATE}" would be there. Prior to
c88b991 on edison, DISTRO_VERSION = "1.0+snapshot-${DATE}". So you're
picking that up from some prior master build. It's not an older
version of edison as if it was an older version of edison it would be
1.0+snapshot-${DATE
 
-b
 


Ok, this is some more debug info:

OE Build Configuration:
BB_VERSION        = "1.13.3"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "qemuarm"
DISTRO            = "poky"
DISTRO_VERSION    = "1.1+snapshot-20111026"
TUNE_FEATURES     = "armv5 dsp thumb arm926ejs"
TARGET_FPU        = "soft"
meta             
meta-yocto       
meta-db-generic   = "edision:b4757833c3548b5ee3a1cce58e2f059b3f63cb09"

Could it be that because I have my own layer present it's skewing the git? Should the eclipse plug-in not match 1.1*?

Could you check your file of meta-yocto/conf/distro/poky.conf for the variable DISTRO_VERSION, it should be "1.1'.


It does indeed state 1.1.




Re: [PATCH 0/4][KERNEL] more bsp cleanup and new power/intel feature

Tom Zanussi <tom.zanussi@...>
 

On Wed, 2011-10-26 at 07:39 -0700, Bruce Ashfield wrote:
On 11-10-25 03:17 PM, tom.zanussi@... wrote:
From: Tom Zanussi<tom.zanussi@...>

This patchset adds a new power/intel feature containing power-related
config items for intel bsps and initially makes sugarbay and crownbay
use it.

It also removes the igb feature from common-pc-64, which shouldn't
be there and was responsible for Yocto bug #1188.

Fixes [YOCTO #1188]

Please pull into linux-yocto-3.0 and linux-yocto-dev.
Looks good. Do you agree that this would be part
of any 1.1 point release as well, or is this purely a
1.2/cleanup activity ? If it's the latter, I need to wait
for the 1.1 sustaining kernel to be created.
I think this is all purely 1.2/cleanup. It does fix a bug, but not a
serious enough to make it into a point release, IMHO.

Tom

Bruce


Pull URL: git://git.pokylinux.org/linux-yocto-2.6.37-contrib
Branch: tzanussi/bsp-cleanup2-v0
Browse: http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/bsp-cleanup2-v0

Tom Zanussi (4):
meta: add power feature
meta/sugarbay: use power/intel feature
meta/crownbay: use power/intel feature
meta/common-pc-64: remove igb

.../kernel-cache/bsp/common-pc-64/common-pc-64.scc | 1 -
meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc | 1 +
meta/cfg/kernel-cache/bsp/sugarbay/sugarbay.scc | 1 +
meta/cfg/kernel-cache/features/power/intel.cfg | 28 ++++++++++++++++++++
meta/cfg/kernel-cache/features/power/intel.scc | 1 +
5 files changed, 31 insertions(+), 1 deletions(-)
create mode 100644 meta/cfg/kernel-cache/features/power/intel.cfg
create mode 100644 meta/cfg/kernel-cache/features/power/intel.scc


Re: [PATCH 0/4][KERNEL] more bsp cleanup and new power/intel feature

Bruce Ashfield <bruce.ashfield@...>
 

On 11-10-25 03:17 PM, tom.zanussi@... wrote:
From: Tom Zanussi<tom.zanussi@...>

This patchset adds a new power/intel feature containing power-related
config items for intel bsps and initially makes sugarbay and crownbay
use it.

It also removes the igb feature from common-pc-64, which shouldn't
be there and was responsible for Yocto bug #1188.

Fixes [YOCTO #1188]

Please pull into linux-yocto-3.0 and linux-yocto-dev.
Looks good. Do you agree that this would be part
of any 1.1 point release as well, or is this purely a
1.2/cleanup activity ? If it's the latter, I need to wait
for the 1.1 sustaining kernel to be created.

Bruce


Pull URL: git://git.pokylinux.org/linux-yocto-2.6.37-contrib
Branch: tzanussi/bsp-cleanup2-v0
Browse: http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/bsp-cleanup2-v0

Tom Zanussi (4):
meta: add power feature
meta/sugarbay: use power/intel feature
meta/crownbay: use power/intel feature
meta/common-pc-64: remove igb

.../kernel-cache/bsp/common-pc-64/common-pc-64.scc | 1 -
meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc | 1 +
meta/cfg/kernel-cache/bsp/sugarbay/sugarbay.scc | 1 +
meta/cfg/kernel-cache/features/power/intel.cfg | 28 ++++++++++++++++++++
meta/cfg/kernel-cache/features/power/intel.scc | 1 +
5 files changed, 31 insertions(+), 1 deletions(-)
create mode 100644 meta/cfg/kernel-cache/features/power/intel.cfg
create mode 100644 meta/cfg/kernel-cache/features/power/intel.scc


Re: Eclipse Plugin: ADT Version too old

Jack Mitchell <ml@...>
 

On 25/10/2011 22:40, Flanagan, Elizabeth wrote:
On Tue, Oct 25, 2011 at 7:45 AM, Jack Mitchell <ml@...> wrote:
Hi Jessica,

I posted my environment settings earlier, which are located here:
http://pastebin.com/4vnWPAD2

Yes, I did use bitbake meta-ide-support to build my roo

Hi Jessica,

I just did a full fresh re-build from scratch and now my environment
variables are as follows:

http://ix.io/1Wf

My current git status is:

# On branch edision
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#    ../bitbake/lib/bb/pysh/pyshtables.py
#    ../conf/
#    ./
#    ../qemuarm-toolchain/
nothing added to commit but untracked files present (use "git add" to track)
Jack,

I just checked out a clean edison and ran bitbake meta-ide-support. My
env is showing export OECORE_DISTRO_VERSION="1.1". My guess is that,
since you are not in master, then you have a TMPDIR from a master
build, or perhaps are using something left over from one, as the only
place DISTRO_VERSION = "1.1+snapshot-${DATE}" would be there. Prior to
c88b991 on edison, DISTRO_VERSION = "1.0+snapshot-${DATE}". So you're
picking that up from some prior master build. It's not an older
version of edison as if it was an older version of edison it would be
1.0+snapshot-${DATE

-b


Ok, this is some more debug info:

OE Build Configuration:
BB_VERSION        = "1.13.3"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "qemuarm"
DISTRO            = "poky"
DISTRO_VERSION    = "1.1+snapshot-20111026"
TUNE_FEATURES     = "armv5 dsp thumb arm926ejs"
TARGET_FPU        = "soft"
meta             
meta-yocto       
meta-db-generic   = "edision:b4757833c3548b5ee3a1cce58e2f059b3f63cb09"

Could it be that because I have my own layer present it's skewing the git? Should the eclipse plug-in not match 1.1*?

Could you check your file of meta-yocto/conf/distro/poky.conf for the variable DISTRO_VERSION, it should be "1.1'.


It does indeed state 1.1.





Re: [PATCH 7/7] Add proper deps for nfs-utils, util-linux, and strace

McClintock Matthew-B29882 <B29882@...>
 

On Tue, Oct 25, 2011 at 3:10 AM, Martin Jansa <martin.jansa@...> wrote:
PING

I've fixed nfs_utils, could you please fix util-linux and strace as suggested?
This is still on my list but I'm not sure when I will be able to get to it.

-M


Re: Eclipse Plugin: ADT Version too old

Lu, Lianhao <lianhao.lu@...>
 

Jack Mitchell wrote on 2011-10-25:

Hi Jessica,

I just did a full fresh re-build from scratch and now my environment
variables are as follows:

http://ix.io/1Wf

My current git status is:

# On branch edision # Untracked files: # (use "git add <file>..." to
include in what will be committed) # #
../bitbake/lib/bb/pysh/pyshtables.py # ../conf/ # ./ #
../qemuarm-toolchain/ nothing added to commit but untracked files
present (use "git add" to track)

The environment variables are still wrong, can I manually change them,
I understand this is bad practice but I can't develop until I fix this.
Jack,

You may manually change them, but I doubt this suggesting that there might be some mismatch in your local git branch. The "bitbake meta-ide-support" of Edison branch on my machine could generate the right OECORE_DISTRO_VERSION and OECORE_SDK_VERSION, with the value of "1.1", not "1.1+snapshot".

Could you check your file of meta-yocto/conf/distro/poky.conf for the variable DISTRO_VERSION, it should be "1.1'.

b.t.w. When you "bitbake meta-ide-support", there will be some configuration information on the console which might help you identify the version and configurations, e.g.

OE Build Configuration:
BB_VERSION = "1.13.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "qemuarm"
DISTRO = "poky"
DISTRO_VERSION = "1.1"
TUNE_FEATURES = "armv5 dsp thumb arm926ejs"
TARGET_FPU = "soft"
meta
meta-yocto = "(nobranch):1924f52cc894d4dd6b9d9c1a2248b32fc0a24c8c"

Best Regards,
Lianhao


Re: Eclipse Plugin: ADT Version too old

Flanagan, Elizabeth <elizabeth.flanagan@...>
 

On Tue, Oct 25, 2011 at 7:45 AM, Jack Mitchell <ml@...> wrote:

Hi Jessica,

I posted my environment settings earlier, which are located here:
http://pastebin.com/4vnWPAD2

Yes, I did use bitbake meta-ide-support to build my roo

Hi Jessica,

I just did a full fresh re-build from scratch and now my environment
variables are as follows:

http://ix.io/1Wf

My current git status is:

# On branch edision
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#    ../bitbake/lib/bb/pysh/pyshtables.py
#    ../conf/
#    ./
#    ../qemuarm-toolchain/
nothing added to commit but untracked files present (use "git add" to track)
Jack,

I just checked out a clean edison and ran bitbake meta-ide-support. My
env is showing export OECORE_DISTRO_VERSION="1.1". My guess is that,
since you are not in master, then you have a TMPDIR from a master
build, or perhaps are using something left over from one, as the only
place DISTRO_VERSION = "1.1+snapshot-${DATE}" would be there. Prior to
c88b991 on edison, DISTRO_VERSION = "1.0+snapshot-${DATE}". So you're
picking that up from some prior master build. It's not an older
version of edison as if it was an older version of edison it would be
1.0+snapshot-${DATE

-b

--
Elizabeth Flanagan
Yocto Project
Build and Release


[RFC] BSP Release Process.

Flanagan, Elizabeth <elizabeth.flanagan@...>
 

All,

In order to incorporate the work various individuals are doing on BSPs
into a centralized location, I've spent some time documenting what the
current BSP release process is for meta-intel so that I can help
people get their BSPs included into the yocto downloads
directory/yocto release. Please take a few moments to read/comment.

https://wiki.yoctoproject.org/wiki/Third_Party_BSP_Release_Process

--
Elizabeth Flanagan
Yocto Project
Build and Release


Re: Eclipse Plugin: ADT Version too old

Zhang, Jessica
 

Jack,

 

One other thing to check, did you do git update of your Edison branch before running a fresh build?

 

From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Jack Mitchell
Sent: Tuesday, October 25, 2011 7:45 AM
Cc: yocto@...
Subject: Re: [yocto] Eclipse Plugin: ADT Version too old

 

On 24/10/2011 16:55, Zhang, Jessica wrote:

OK missed your env post. Then this is your problem:
 
16.export OECORE_DISTRO_VERSION="1.1+snapshot-20111021"
17.export OECORE_SDK_VERSION="1.1+snapshot"
 
They need to be 1.1 instead of 1.1+snapshot.  You need to update your Edison branch then do "bitbake meta-ide-support"
 
-----Original Message-----
From: Jack Mitchell [mailto:ml@...]
Sent: Monday, October 24, 2011 8:44 AM
To: Zhang, Jessica
Cc: yocto@...
Subject: Re: [yocto] Eclipse Plugin: ADT Version too old
 
On 24/10/2011 16:42, Zhang, Jessica wrote:
Hi Jack,
 
So you mean you did "bitbake meta-ide-support" to use the build tree?
 
I just tried with my Edison build tree mode on my laptop and it works fine. So can you check under your build/tmp directory, there should be an environment-setup-*-poky-linux file, where * is your target arch.  At the end file do you have several OECORE_* settings ? If not, you need to rerun "bitbake meta-ide-support" and ensure there're OECORE_* settings at the end.
 
Thanks,
Jessica
 
-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Jack Mitchell
Sent: Monday, October 24, 2011 2:24 AM
To: yocto@...
Subject: Re: [yocto] Eclipse Plugin: ADT Version too old
 
On 24/10/2011 10:18, Lu, Lianhao wrote:
Jack Mitchell wrote on 2011-10-24:
I am trying to use the new eclipse plugin, which I have had working
fine for the past couple of weeks until I switched from the master branch to edison.
 
I performed a fresh build using the stable edison branch, installed
the new 1.1 eclipse plugin and now whenever I try to setup the Yocto
eclipse environment I receive the following error:
 
Yocto Preferences Configuration Error!
OECORE related items are not found in envrionement setup files.
The ADT version you're using is too old.
Please upgrade to our latest ADT Version!
 
This pops up in a message box, not the eclipse console. I have
followed the ADT Setup guide to the letter and it's not playing ball -
could someone confirm this as working or point me towards a reason why I may be getting this error?
 
Hi Jack,
 
How did you install your ADT? You can check the ADT version by "cat" the file /opt/poky/${version}/version-xxxx, where xxxx is your target sys architecture.
 
-Lianhao
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
Hi Lianhao,
 
I am using the yocto build tree so I don't have an installed ADT in /opt
but one that has been generated within my build directory, this is
correct yes?
 
Jack.
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
 
Hi Jessica,
 
I posted my environment settings earlier, which are located here:
http://pastebin.com/4vnWPAD2
 
Yes, I did use bitbake meta-ide-support to build my roo


Hi Jessica,

I just did a full fresh re-build from scratch and now my environment variables are as follows:

http://ix.io/1Wf

My current git status is:

# On branch edision
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#    ../bitbake/lib/bb/pysh/pyshtables.py
#    ../conf/
#    ./
#    ../qemuarm-toolchain/
nothing added to commit but untracked files present (use "git add" to track)

The environment variables are still wrong, can I manually change them, I understand this is bad practice but I can't develop until I fix this.

t.

 


[PATCH 2/2] meta-fri2: README correction

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

In the instructions for manually extracting the binaries from the EMGD
Linux tarball, an additional step for removing the emgd_drv_video
shared library is necessary; this adds it for fri2.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-fri2/README | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/meta-fri2/README b/meta-fri2/README
index 29f2618..4dc135b 100644
--- a/meta-fri2/README
+++ b/meta-fri2/README
@@ -124,6 +124,15 @@ You also need to copy the IEMGD License.txt file to the same directory:

$ cp IEMGD_HEAD_Linux/License/License.txt meta-intel/common/recipes/xorg-xserver/emgd-driver-bin-1.8

+Additionally, you should remove the following unused file from the
+emgd binaries in order to avoid a packaging error at build-time:
+
+$ rm meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8/lib/dri/emgd_drv_video.so
+
+Finally, you need to remove the following file:
+
+$ rm meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8/lib/dri/emgd_drv_video.so
+
At this point, you should be able to build meta-fri2 images as usual.


--
1.7.0.4


[PATCH 1/2] meta-crownbay: README correction

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

In the instructions for manually extracting the binaries from the EMGD
Linux tarball, an additional step for removing the emgd_drv_video
shared library is necessary; this adds it for crownbay.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-crownbay/README | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/meta-crownbay/README b/meta-crownbay/README
index 439b8c7..de9f1f1 100644
--- a/meta-crownbay/README
+++ b/meta-crownbay/README
@@ -122,6 +122,11 @@ You also need to copy the IEMGD License.txt file to the same directory:

$ cp IEMGD_HEAD_Linux/License/License.txt meta-intel/common/recipes/xorg-xserver/emgd-driver-bin-1.8

+Additionally, you should remove the following unused file from the
+emgd binaries in order to avoid a packaging error at build-time:
+
+$ rm meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8/lib/dri/emgd_drv_video.so
+
At this point, you should be able to build meta-crownbay images as usual.


--
1.7.0.4


[PATCH 0/2] meta-intel: a couple README fixes

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

This adds a missed step to the READMEs for the manual version of the EMGD
setup for fri2 and crownbay.

The BSP tarballs for these, which would normally be what users would download
and use, don't need these instructions - this is only for users who would
manually extract the binaries from the EGMD tarball/rpm.

These README changes should be pulled into both edison and master.

The following changes since commit d531816b6d986e8a7ff3f827e86e53aba30c6cfb:
Tom Zanussi (1):
meta-jasperforest: add xserver-xorg bbappend

are available in the git repository at:

git://git.yoctoproject.org/meta-intel.git tzanussi/emgd-docfix-v0
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/emgd-docfix-v0

Tom Zanussi (2):
meta-crownbay: README correction
meta-fri2: README correction

meta-crownbay/README | 5 +++++
meta-fri2/README | 9 +++++++++
2 files changed, 14 insertions(+), 0 deletions(-)


[PATCH 4/4][KERNEL] meta/common-pc-64: remove igb

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

igb shouldn't be included by default in the common-pc-64 base, so
remove it.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
.../kernel-cache/bsp/common-pc-64/common-pc-64.scc | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc
index ad01836..2c6b441 100644
--- a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc
+++ b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc
@@ -4,7 +4,6 @@ kconf hardware common-pc-64-graphics.cfg
include cfg/boot-live.scc

include features/hpet/hpet.scc
-include features/igb/igb.scc
include features/intel-e1xxxx/intel-e100.scc
include features/intel-e1xxxx/intel-e1xxxx.scc

--
1.7.0.4


[PATCH 3/4][KERNEL] meta/crownbay: use power/intel feature

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

Have crownbay use more power-friendly settings.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc b/meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc
index 391b955..fb761a0 100644
--- a/meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc
+++ b/meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc
@@ -12,6 +12,7 @@ include features/hpet/hpet.scc
include features/framebuffer/vesafb.scc
include cfg/usb-mass-storage.scc
include cfg/boot-live.scc
+include features/power/intel.scc

include features/logbuf/size-normal.scc

--
1.7.0.4