Updating SRCREVs to reflect:
perf: hard-code NO_LIBPERL/NO_LIBPYTHON
ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and
using it to compile perf, which results in a compilation error that
started appearing just recently.
This turns the code that makes use of ExtUtils::Embed off and simply
hard-codes NO_LIBPERL.
It does the same for LIBPYTHON while we're at it, since it probably
suffers from a similar underlying problem and just by chance hasn't
broken anything yet.
This will be re-enabled after I familiarize myself with the perf
recipe and am able to create a proper fix.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The message cache code in pseudo seems to be causing problems. So we have
finally decided to revert that optimization.
(The revert is in the upstream pseudo.)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
By default the linux-yocto recipes operate on the current branch
and use it as a trigger to locate the description of a board. This
model works well when using the git repo outside of a build system
since the commands can be simply invoked and will do something
useful. However, it does mean that you can't have two BSPs that
differ only by configuration, building out of a single branch
in the repository.
This means that you must have many branches for very similar
BSPs. This model is still preferred, but having the choice of
branching strategies is better.
With this change we can have multiple BSPs using a single branch
with the preferred description being hinted from the build
system by passing the $machine value to updateme/configme.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Updating beagleboard SRCREV to pickup:
commit 8e15b884ecf768fd9f898da5acf24938dfe81a83
Author: Koen Kooi <koen@beagleboard.org>
Date: Tue Jan 11 17:13:35 2011 +0000
omap3: beaglexm: fix EHCI power up GPIO dir
commit a5624323866c06156ca548b8515d9347fdd5188e angstrom-linux
EHCI enable power pin is inverted (active high) in comparison
to vanilla beagle which is active low. Handle this case conditionally.
Without this fix, Beagle XM 4 port EHCI will not function and no
networking will be available
[nm@ti.com: split up, added descriptive changelogs]
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Koen Kooi <koen@beagleboard.org>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Updating the meta branch to contain the latest crownbay
configuration tweaks.
e1f85a4 wrs_meta: turn on OHCI USB config option
8be8e45 wrs_meta (crownbay): turn on AHCI SATA option
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Bumping the SRCREV to pickup some missing functionality:
ebbca89 omap: Beagle: no gpio_wp pin connection on xM
671fd89 omap: Beagle: only Cx boards use pin 23 for write protect
dccdf8a omap: Beagle: revision detection
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
uboot-omap3 appears to be fairly stale (last commit in April 2010) while
the upstream u-boot is making regular tagged releases. Add a new recipe
using the upstream u-boot repository.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
TI is now maintaining an upstream x-loader git repository and
sakoman will no longer be maintained. Current upstream
includes signGP and incorporates it into the Makefile. The new
Makefile ift target builds the universal MLO binary. The armv7-a
patch is included.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
Add systemtap, a general-purpose script-directed dynamic tracing and
performance analysis tool for Linux.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Update pseudo to the latest version to resolve a number of optimization defects.
The problems were present on both 64-bit and 32-bit systems, but generally only
caused issues on 32-bit hosts.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
The switch to KARCH meant that the arch arm settings were not
being applied to all boards. This commit adds the new option
along with the existing one to cover all boards.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Updating the SRCREV to capture this commit to the 2.6.34 kernel:
linux-2.6-windriver: atom-pc-preempt_rt meta-data
The following patch adds support for the preempt_rt kernel type
for the atom-pc machine. It should be applied to the wrs_meta
branch.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Enable the parameters required for systemtap for all BSPs based
off the standard kernel type.
CONFIG_KPROBES=y
CONFIG_RELAY=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_FS=y
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The routerstation pro and mpc8315e-rdb have been validated
on 2.6.37 so we can switch their preference to linux-yocto
and update the machine compatibility to add them to the support
list.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Upgrade to 6c696cec3f264a9399241b6e648f58bc97117d49 which
includes fixes to the Makefile to allow for user override of
CC and AR via the environment as well as python SWIG wrapper
fixes.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
Fixes [BUGID: 620]
Update the SRCREVs to include the full 2.6.37 release plus the
forward port of the alternate RPC port patch. With this fix,
we can complete usermode NFS booting of all the qemu* targets.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Update the SRCREV to pickup changes to update the use of
WRS_* to be K* to provide more generic names for the
platform/board/kernel configuration options.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Updating to reflect the changes from Darren Hart:
[
linux-yocto-2.6.37: Add debugfs and ftrace features to standard ktype meta-data
ftrace provides low impact tracing facilities and should be made
available on the main kernel - as opposed to a debug or tracing
kernel which often add enough overhead to mask subtle bugs.
These features are available on the 2.6.34 yocto kernel.
Boot and trace-cmd tested on qemux86-64.
Signed-off-by: Darren Hart <darren@dvhart.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Fixes [BUGID #581]
The initial routerstation pro BSP went out with with command line
overrides enabled. We'd need to be able to set the command line
from Redbot, so we should disable the forcing of the built in
variant.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
configme used to be able to calculate the output/build directory
when branches were always <machine>-<kernel type>. Branch names
can now be widely different and to avoid embedding complexity
in the scripts it is easier to just pass ${B} from the build system
down to the scripts.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The trace-cmd source includes a graphical trace viewer, but we
don't want to make the trace-cmd recipe depend on gtk+. This
patch adds a second recipe in the meta/recipes-kernel/trace-cmd
directory which uses the trace-cmd SRCREV and RDEPENDS on trace-cmd
to ensure compatibility.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Richard Purdie <richard.purdie@linuxfoundation.org>
CC: Saul Wold <sgw@linux.intel.com>
The _ to - mass change mangled a config file name, which was
dropped from the update. This adds the fixed file back to the
meta branch of the kernel.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Fixes [BUGID #596]
Updating the SRCREVs of the target branches in the linux-yocto
development kernel to point to 2.6.37-rc6 content.
At this point branches have been switched from _ to - and we
are able to remove the old branch names.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
This modifies the meta-emenlow BSP layer to reflect the new BSP
standard layout as defined in the latestYocto BSP Developer's Guide.
There's no change in functionality here - this simply moves things
around, adds a README, and makes the SRCREVs local.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
See the longlinksfix patch for details but symlinks over 100 chars long
were broken in sdk tarballs and its due to problems in the inbuilt tar in
libbb in opkg.
The patch fixes this and switched to svn r590 which already had partial fixes.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
The existing 2.6.34 kernel tree uses _ where poky typically
uses -. This is a historical artifact, since working with
gnu Make and shells means avoiding - is wise. The opposite
is true in Yocto.
To avoid using the _ reserved character wherever possible
we can simply remove it from the branch names in the
new 2.6.37 kernel, but to keep the content stable in the
0.9 2.6.34 kernel, we map _ to - for the purposes of
packaging.
To further faciliate this switch, the branch names no
longer need to be shortened in the KMACHINE mappings, but
can be fully specified and the tools/processing adapt as
required. This gives us the flexibility to map multiple
boards to a single branch for building.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Enable the kernel configuration values required for blktrace
by default. Individual boards can opt out as required.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Fixes [BUGID: 585]
The qemuppc irq handling was only partially updated to 2.6.37,
this completes the job. qemuppc builds and boots with this
change.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
In order to extend and create more kernel recipes based on the
supported yocto kernel common routines need to be placed in
re-usable blocks.
To accomplish this meta/recipes-kernel/linux/linux-yocto_git.bb
is broken into three parts:
- meta/classes/kernel-yocto.bbclass: contains common routines
for checking out and configuring a yocto kernel git repository.
This should be inherited by recipes that need this functionality.
- meta/recipes-kernel/linux/linux-yocto.inc: Contains the machine
mappings, compatibility, build directives and common task
definitions for a yocto kernel based recipe. This inherits
kernel-yocto, and is the typical point of entry for other recipes.
- meta/recipes-kernel/linux/linuux-tools.inc: tasks and function definitions
for kernel recipes that want to build/export perf
It also updates the linux-yocto recipe to default to 2.6.37.
As part of the update to 2.6.37 the branch naming and conventions
have been modified to show inheritance, and be more generic.
For example:
master
meta
yocto/base
yocto/standard/arm_versatile_926ejs
yocto/standard/base
yocto/standard/beagleboard
yocto/standard/common_pc/atom-pc
yocto/standard/common_pc/base
yocto/standard/common_pc_64
yocto/standard/fsl-mpc8315e-rdb
yocto/standard/intel_atom_z530
yocto/standard/intel_core_qm57_pch
yocto/standard/mti_malta32_be
yocto/standard/preempt_rt/base
yocto/standard/preempt_rt/common_pc
yocto/standard/preempt_rt/common_pc_64
yocto/standard/preempt_rt/intel_atom_z530
yocto/standard/preempt_rt/intel_core_qm57_pch
yocto/standard/qemu_ppc32
yocto/standard/routerstationpro
In this structure:
master: tracks the mainline kernel
meta: meta information for the BSPs and kernel features
yocto/base: baseline kernel branch
yocto/standard/base: 'standard' kernel, contains features
and configs for all BSPs
yocto/standard/<machine>: represents a BSP with specific
features or configurations
The tools, tree and libc-headers have all been updated to
deal with this new structure. Also in addition to dealing with
the new structure, they continue to work with the existing
tree and will adapt at runtime to the differences.
The linux-yocto-stable_git.bb recipe continues to build the
2.6.34 based tree,and linux-yocto_git.bb builds 2.6.37. As
boards are enabled for the new kernel they will move from
-stable to the development kernel. As of now, only the
emulated targets have moved to 2.6.37-rcX
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
This reverts commit 4bcba3fb12.
The qemugl is not building so I am reverting this update until
it's resolved.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
qemugl has no update since May 2009. Compared to current SRCREV, there is 3 new commit in upstream. So simply upgrade the SRCREV to the latest commit of May 2009, to include the 3 new commits.
Signed-off-by: Yu Ke <ke.yu@intel.com>
Zhai Edwin
Bruce Ashfield
Mark Hatle
Darren Hart
Qing He
Tom Zanussi
Dongxiao Xu
Saul Wold
Richard Purdie
Alex deVries
Nitin A Kamble
Saul Wold
Yu Ke