KVM, paravirtualization and virtio drivers are now activated
in runqemu using the kvm option flag for qemux86.
Host CPU features are also exported to guest OS (Yocto Linux).
Usage example: runqemu qemux86 core-image-x11 kvm
Implements [YOCTO #2550].
(From OE-Core rev: a35d03e2eb905de4eadc9c7df5b50bff1fb7f897)
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
uprobes depends on functionality provided by perf events. After
uprobes was enabled in the standard kernel the mpc8315 board showed
link errors due to missing perf event functions.
This problem isn't isolated to the board or powerpc arch, but all
other boards have PERF_EVENTS enabled. To fix this, we make UPROBE_EVENT
select PERF_EVENTS, and any new boards will be protected from the
same failure.
We also update the configuration fragments since CONFIG_UPROBES depends on
CONFIG_PERF_EVENTS being set, so PERF_EVENTS needs to be added whenever
uprobes are enabled.
[YOCTO #3111]
(From OE-Core rev: b681b74624d1c8c4c98b2a121828e010fc5c3a25)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta branch SRCREV to pick up virtio and kvm guest
configuration fragments.
79947f1 meta: add paravirtualized KVM guest config fragment
3ed86ed meta: add MMIO support in virtio config fragment
(From OE-Core rev: b6b5b501fbe7158f190e887c3edc1214bb3671ed)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It was reported that the kernel configuration checks for custom yocto
kernels had the following output:
NOTE: validating kernel configuration
grep: /meta-series: No such file or directory
grep: /meta-series: No such file or directory
WARNING: Can't find any BSP hardware or required configuration fragments.
WARNING: Looked at //cfg///hdw_frags.txt and //cfg///required_frags.txt in directory: //cfg//
NOTE: Tasks Summary: Attempted 375 tasks of which 367 didn't need to be rerun and all succeeded.
which is not inspire confidence in the output of the process.
Completely inhibiting the check is one option to remove the messages,
but that removes the ability see output, which can help move users to
a better or more fully configured linux-yocto based kernel.
To fix this, we have to ensure that the path to the meta-series is
always valid, and that the tools can deal with not all files existing
in the audit directory.
Since custom yocto kernels do not set KMETA (they don't have a meta branch),
we ensure that a default of 'meta' is passed to the audit ('meta' is always
valid), and that kconf_check itself can deal with an incomplete set of
input audit files.
The net result is output like this (using a defconfig with invalid options
for the kernel being built):
NOTE: validating kernel configuration
This BSP sets 19 invalid/obsolete kernel options.
These config options are not offered anywhere within this kernel.
The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/invalid.cfg
There were 1 instances of config fragment errors.
The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/fragment_errors.txt
The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/missing_required.cfg
(From OE-Core rev: 4d1b7dae063ee4c35c426306d0e22f11ce112c72)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was noticed by the following warnings of files that should have been removed!
WARNING: QA Issue: kernelshark: Files/directories were installed but not shipped
/usr/share
/usr/share/trace-cmd
/usr/share/trace-cmd/plugins
/usr/share/trace-cmd/plugins/plugin_blk.so
/usr/share/trace-cmd/plugins/plugin_sched_switch.so
/usr/share/trace-cmd/plugins/plugin_kmem.so
/usr/share/trace-cmd/plugins/plugin_kvm.so
/usr/share/trace-cmd/plugins/plugin_function.so
/usr/share/trace-cmd/plugins/plugin_jbd2.so
/usr/share/trace-cmd/plugins/plugin_hrtimer.so
/usr/share/trace-cmd/plugins/plugin_mac80211.so
/usr/share/trace-cmd/plugins/.debug
/usr/share/trace-cmd/plugins/.debug/plugin_blk.so
/usr/share/trace-cmd/plugins/.debug/plugin_sched_switch.so
/usr/share/trace-cmd/plugins/.debug/plugin_kmem.so
/usr/share/trace-cmd/plugins/.debug/plugin_kvm.so
/usr/share/trace-cmd/plugins/.debug/plugin_function.so
/usr/share/trace-cmd/plugins/.debug/plugin_jbd2.so
/usr/share/trace-cmd/plugins/.debug/plugin_hrtimer.so
/usr/share/trace-cmd/plugins/.debug/plugin_mac80211.so
(From OE-Core rev: c3cff64708cb078405f5ecd9bca6801031786bc4)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When x32 is the tuning for a x86 MACHINE, the kernel should also have
CONFIG_X86_X32=y. This adds a x32 fragment that can be used to trigger
the right ABI.
The commit also contains a check for mx32 in TUNE_FEATURES, and if
present, the new fragment will be appended to KERNEL_FEATURES and
trigger the support in the kernel.
cc: Saul Wold <sgw@linux.intel.com>
(From OE-Core rev: bf689c60caa905eb8866101b9e99dd4ae246a2ca)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is sometimes useful for KERNEL_FEATURES to be set in a machine
or other configuration file. The linux-yocto recipes currently
initialize the variable, which clobbers any values set by .conf
files.
Appending to the variables allows these settings to propagate to
the kernel configuration, while maintaining the existing set of
added kernel features.
(From OE-Core rev: 7121fe8d836fc178e9ab8f0e6f8eb34a99325c81)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to 3.4.10 which has been soaking for a bit now, as well
as picking up the following meta commits from Tom Z:
a82db2f meta: have systemtap use kprobes and uprobes feature
d5d5b80 meta: add kprobes support to ktypes/standard
b32d373 meta: add kprobes feature
d40ed99 meta: have uprobe feature use uprobe.cfg
a69d1db meta: add uprobe.cfg
(From OE-Core rev: fb71d8c3ab735739baedcb5c8c44b028890d8a5e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The first import of 3.4.9-rt17 only picked up part of the import due
to a merge conflict with the modified files, and then SRCREVs being
generated from the pre-merge commit.
This SRCREV update picks up the rest of the modified files for full
-rt support.
(From OE-Core rev: d1ec0b64018dafaa6e47233b3465fbe4189e6280)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the 3.4 kernel to -rt17.
As well as picking up the normal set of bug fixes, this update fixes
a boot issue that was introduced during merging of kernel.org -stable
updates into the -rt branches (in the timekeeping code).
(From OE-Core rev: 0c060a81ade685aee5492e0273f199850dffaf76)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.2/3.4 linux-yocto SRCREVs to pickup the following fix:
arm: Fix linking errors with binutils 2.23
We end up with linking errors on arm using latest binutils
because we are linking asm generated objects which use -march=all
generating different attributes into object and use some c objects
e.g. misc.o which use different march therefore generating a
different set of attributes into object. When linking is done
the ld complains since it finds incompatible attributes and ends
up with errors like
error: DIV usage mismatch between arch/arm/boot/compressed/head.o and
output
error: DIV usage mismatch between arch/arm/boot/compressed/misc.o and
output
error: DIV usage mismatch between arch/arm/boot/compressed/decompress.o
and output
error: DIV usage mismatch between arch/arm/boot/compressed/lib1funcs.o
and output
This patch fixes it by providing correct march to assembly routines
which than matches with output of ld.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(From OE-Core rev: e67ffb708522a622d149641ea09b249259ed3fb4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Importing the following tools SRCREV:
kgit-meta: exclude explicit branches from name calculations
kernel branches are constructed during patching of the tree by
constructing a '/' based hierarchy of names as each branch
directive is encountered.
But if a "branch $name $branchpoint" is used, the entire branch
name is supplied so no additions to the hierarchy should
happen. As such, that type of branch command should not be part
of branch name calculation and preparation.
(From OE-Core rev: a3884938233c8a2d6861b1d4e6be5b9824d3b131)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When patches fail to apply, the status of all pending patches should
be exported to the logs and to the user. Currently, a missing export
of GUILT_BASE makes it look more like an internal error, than a 'normal'
patch failure:
| [ERROR] unable to complete push
| pending patches are:
| Patches directory doesn't exist, try guilt-init
With this variable exported, we have this:
| [INFO] validating against known patches (qemux86-standard-meta)
| error: patch failed: Makefile:2
| error: Makefile: patch does not apply
| To force apply this patch, use 'guilt push -f'
| [ERROR] unable to complete push
| pending patches are:
| links/files/0002-makefile-patch.patch
(From OE-Core rev: b2b2512cbc4196fa0f814be3677517dab30e5b52)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
commit 7a79f7412 [linux-yocto: make KBRANCH the exception and not the rule]
ensures that a request branch is always built. The implementation of this
guarantee is a branch switch before the build starts. But that switch may
be before all patches are applied. If the proper routines are not called,
no patches can be applied to the tree.
Updating the SRCREV to pickup this fix:
updateme: use branch command when forcing branch switches
When forcing a branch switch to the desired branch we should be
using the proper 'branch' command. Since without this call, the
proper variables will not be set, and patches can't be applied
to the tree.
(From OE-Core rev: bede3086cb9ab0f79fb7775528b646817b2b9af0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The qemu-config initscript was only starting oprofile-server, so move it
to the oprofileui-server recipe.
(From OE-Core rev: 3063126e2c8ec72e900a48f7048aaf9662606792)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Increase SRCREV to include an upstream patch that fixes the configure
script so that the server can be built separately without gtk+ and
avahi-ui, and create a separate recipe for the server.
Also fix the RDEPENDS so that oprofile actually gets pulled in by the
client and the server.
Part of the fix for [YOCTO #1690].
(From OE-Core rev: 971fbbd50ae147805fc7498b72a046be5bffc3c7)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since kernelshark depends on trace-cmd, there is no reason to
install and package the plugins that are part of trace-cmd.
[YOCTO #238]
(From OE-Core rev: d6614b0ac7c83b2e17e68903a85fc8374e936c1a)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As discussed on the mailing lists, using a suffix to package names is
hard and has lead to many recipes having to do PKGSUFFIX games. Its
looking extremely hard to scale nativesdk much further without hacking
many recipes.
By comparison, using a prefix like multilib does works much better and
doesn't involve "hacking" as many recipes. This change converts nativesdk
to use a prefix using the existing multilib infrastructure.
(From OE-Core rev: 81813c0e322dc04ce4b069117188d8a54dfddb8c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
perf depends on bison and flex for event parsing - add them as
dependencies.
(From OE-Core rev: f04b0ddb7a392425ba5890026564bc3521a32c67)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To support custom repositories that set a SRCREV and that only have
a single master branch, do_validate_branches needs a special case
for 'master'. We can't delete and recreate the branch, since you
cannot delete the current branch, instead we must reset the branch
to the proper SRCREV.
(From OE-Core rev: de5bb5879fa3282c46dc1ede36af34eaab8f647f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the kernel's tools/perf/Makefile CFLAGS was previously hard coded to
contain "-I/usr/include/slang" to work with hosts that have
"/usr/include/slang/slang.h" as well as hosts that have
"/usr/include/slang.h". This path can cause compile warnings like:
cc1: warning: '/usr/include/slang' doesn't exists.
or
cc1: warning: include location "/usr/include/slang" is unsafe for
cross-compilation [-Wpoison-system-directories]
Then in some cases warnings become errors if WERROR is enabled hence
build errors.
In coordination with a kernel fix, we can fix this error for all
kernels by modifying the perf Makefile within the staged kernel
source.
(From OE-Core rev: 4e0daf05ed04e9fb4343032c6290a379f53b89f3)
Signed-off-by: Liang Li <liang.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
kmod will fail to build with the following error because O_CLOEXEC is
not defined:
| libkmod/libkmod-module.c: In function 'kmod_module_get_initstate':
| libkmod/libkmod-module.c:1640: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-module.c:1640: error: (Each undeclared identifier is reported only once
| libkmod/libkmod-module.c:1640: error: for each function it appears in.)
| libkmod/libkmod-module.c: In function 'kmod_module_get_refcnt':
| libkmod/libkmod-module.c:1754: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-module.c: In function 'kmod_module_get_sections':
| libkmod/libkmod-module.c:1913: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-file.c: In function 'kmod_file_open':
| libkmod/libkmod-file.c:282: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-file.c:282: error: (Each undeclared identifier is reported only once
| libkmod/libkmod-file.c:282: error: for each function it appears in.)
Since we are only using kmod-native for depmod, and it's a non-threaded
user of this libary being built this should be safe to override O_CLOEXEC.
Keep in mind this is ONLY effecting the native builds and not what is
being shipped in the root file system.
(From OE-Core rev: edcb57fe308979cc5b92359d064e32bb70d4ad76)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This helps in appending to this regexp from bbappends
coming from other layers who want to leverage linux-yocto
with minimum tweaks by using a standard prefefined machine
from linux-yocto
(From OE-Core rev: 32ba716e71fb7a16f13c83ab6c8cc51de56b3be2)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the meta SRCREV to pickup this fix:
meta: rename virto.scc to virtio.scc
The virtio configuration block is misnamed. BSPs that include it with
the proper name, now throw an error (as they should). So fixing the
name of the fragment fixes the build.
(From OE-Core rev: c6b335099224d590109a8bcda22bf54c597c7eee)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To streamline the creation of build time branches (branches that are
not always present in the upstream kernel repository), linux-yocto-tiny
should specify a default kernel branch. By setting the default branch
(KBRANCH_DEFAULT) and also setting the build branch (KBRANCH) to that
default, the tools will allow the board description to be processed
and no branching forced.
(From OE-Core rev: 07e422138b89e4f4a0cc911db70e2ce953b7623b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removes a make install-python_ext when not present since
older versions of perf lack this install rule
This also fixes a library issue on older kernels building with
a newer toolchain where libaries that would previously be pulled
in are no longer. So we add them manually.
(From OE-Core rev: 70b17a893bd2e1bbba8ea16619b02a60e7c4b8d8)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kern-tools scripts can support a meta branch and directory of a name that
isn't "meta", but they need the name passed through the environment variable
KMETA. ensuring that KMETA is exported in the shell environment sets the stage
to support flexible meta branch name.
(From OE-Core rev: 9b90c8ace04c88ac6105f0bf686f9abc70fe8074)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A BSP specific KBRANCH assignment is no longer a required
element to locate and build a yocto kernel. As such we can
set the default kbranch, and remove all other explicit
assignments.
KBRANCH is still used, and if it is changed from the
default, that branch will be built.
(From OE-Core rev: 7984a9f6ccd00bf282c9eedab7ab933add68448c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel branch is no longer required by the yocto-kern-tools
to locate BSP feature descriptions (it is the MACHINE:KTYPE
descriptor), so we no longer require that the BSP branch be
explicitly set.
If a kernel branch is explicitly set, it is now used to trigger
a checks to ensure that the branch really is being built.
Otherwise the branch that the machine description creates will
be built (just as it always was).
This further simplies the use and configuration of a linux-yocto
based kernel recipe.
(From OE-Core rev: 3cac3ce65abae9dc253641a2004440a2b38fd44d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the linux-yocto 3.4 recipe with consolidated fixes, BSPs
and cleanups.
From the kernel meta branch:
28bcd46 meta: move emgd features to staging
6c01949 meta: Crystal Forest Machine Created.
3c19c4d meta/qemuppc: remove redundant profiling options
a5da4d5 meta: kgdb: update configuration for out of box functionality
1d13e00 meta: update status/series and patches for v3.4
b96c408 fsl-mpc8315e-rdb: replace leading dot with hash in cfg file
7c9a3b0 usb: fix scc and cfg filename collision with ktypes/base/
aa0e1f6 kconfig: make CONFIG_BLOCK=y part of base config
3d1a2f2 kconfig: add tty/serial file to hardware listing
60b600f routerstationpro: specify chosen filesystems in audit input.
8b5c8c7 routerstationpro: add config data for audit purposes
d7ae8fa meta: add ath79 Kconfig to hardware listing.
And from the standard branch:
c77666c powerpc: uprobes: removed external declaration of uprobe_get_swbp_addr.
c262f3e powerpc: Uprobes port to powerpc
d40e73d powerpc: Add trap_nr to thread_struct
6a64190 Revert "This is the port of uprobes to powerpc. Usage is similar to x86."
e422119 Revert "powerpc: uprobes: removed external declaration of uprobe_get_swbp_addr."
d4ef82f keys: kill task_struct->replacement_session_keyring
1cc141e keys: kill the dummy key_replace_session_keyring()
090ca45 keys: change keyctl_session_to_parent() to use task_work_add()
61bc7a8 genirq: reimplement exit_irq_thread() hook via task_work_add()
5ee34dd task_work_add: generic process-context callbacks
70754de move key_repace_session_keyring() into tracehook_notify_resume()
6f70bc1 powerpc: uprobes: removed external declaration of uprobe_get_swbp_addr.
e5f6a4c This is the port of uprobes to powerpc. Usage is similar to x86.
2bc4597 On RISC architectures like powerpc, instructions are fixed size. Instruction analysis on such pl
8893371 perf probe: Detect probe target when m/x options are absent
544d531a perf probe: Provide perf interface for uprobes
103b503 tracing: Fix kconfig warning due to a typo
9bb012e tracing: Provide trace events interface for uprobes
b9b7281 tracing: Extract out common code for kprobes/uprobes trace events
91f0360 tracing: Modify is_delete, is_return from int to bool
a8600f2 uprobes/core: Decrement uprobe count before the pages are unmapped
a252056 uprobes/core: Make background page replacement logic account for rss_stat counters
3efc15b uprobes/core: Optimize probe hits with the help of a counter
20f3d76 uprobes/core: Allocate XOL slots for uprobes use
77bfad8 uprobes/core: Handle breakpoint and singlestep exceptions
7196d9a uprobes/core: Rename bkpt to swbp
c99bc18 uprobes/core: Make order of function parameters consistent across functions
7e9be99 uprobes/core: Make macro names consistent
c4247f2 uprobes: Update copyright notices
f066ff9 uprobes/core: Move insn to arch specific structure
e91cf65 uprobes/core: Remove uprobe_opcode_sz
942b91c uprobes/core: Make instruction tables volatile
56c1e99 uprobes: Move to kernel/events/
0a7ad1c uprobes/core: Clean up, refactor and improve the code
3760d62 uprobes, mm, x86: Add the ability to install and remove uprobes breakpoints
Two BSP updates:
- Crystal Forest Machine has been added
- routerstationpro configuration updates for 3.4
(From OE-Core rev: bd05dcb634cbb4022b4189985585f73c86f01fae)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The v3.4.7 -stable update has been released, updating all in-tree
BSPs to this new baseline.
(From OE-Core rev: 89a0587d5affe8d8986efce7738b7b3774792154)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add in a workaround to avoid host infection detection build failures
from the slang include directory in perf. I'll defer to Bruce to
fix this properly but we need a workaround now as this is breaking
builds.
(From OE-Core rev: 4fd4b2eafb5f4ff2ef85d7f5ff3238a41c34313b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This change breaks firmware loading on 64 bit platforms. This therefore
reverts commit ce2665b6ae77770d69ffbc4d45c96ce829d16738.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Latest version is 1.0.0 but in rc4 for now.
(From OE-Core rev: 6172f1fed9850180a3a84ca62cc0741d132031e4)
Signed-off-by: Radu Moisan <radu.moisan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is considered good practice to use the build system provided
variables instead of directly specify hardcoded paths.
(From OE-Core rev: ce2665b6ae77770d69ffbc4d45c96ce829d16738)
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is considered good practice to use the build system provided
variables instead of directly specify hardcoded paths.
(From OE-Core rev: 095f9c056373a252c0ba2679d8e6f4ad932a958d)
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add pythonnative to the inherits list
(From OE-Core rev: b3ef5a986e3bc1a29ba2b4a25d063a0267e2f72f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 kernel to the latest -stable release and updating preempt-rt
to 3.4.4-rt14.
Tested on qemu*
(From OE-Core rev: 955fd1408713634d9a96b00ef53ed0a6a188e9fe)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this it can't reautoconf or run configure since it depends on pkg-config.
(From OE-Core rev: 7673cd498a50f59b0e2954341de0e8c6913d374f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 meta SRCREV for the following fixes:
949fddd meta: crownbay.scc change emgd branch name
cd0721a yocto/emgd: emgd 1.14 driver
c2b5ee3 meta: disable CONFIG_MTD_NAND_VERIFY_WRITE
004cadb meta: kmemcheck: 'other' configs turning on CONFIG_FUNCTION_TRACER
(From OE-Core rev: c192b2da74b20f091b6191349ceb1cf195aae8c6)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add pythonnative to the inherits list
(From OE-Core rev: d27cd814162fde3362278435a6842928310c2704)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The bb and os modules are always imported so having these extra import calls
are a waste of space/execution time. They also set a bad example for people
copy and pasting code so clean them up.
(From OE-Core rev: 7d674820958be3a7051ea619effe1a6061d9cbe2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.0 SRCREVs to pickup the recent perf scripting fixes.
cef17a1 perf: add sgidefs.h to for mips builds
3258da3 perf: change --root to --prefix for python install
1f9c25b perf: add 'libperl not found' warning
f2b1bf1 perf: use pkg-config instead of python-config
568e05f perf tools: Add support to install perf python extension
7e47f81 Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON"
(From OE-Core rev: 20405bdab18b7a2b101f818e72863d289d5945e4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
On 64bit systems dtc will still install libaries in /usr/lib
unless we havet this override
(From OE-Core rev: b60579e66601ba60669a9e1194409fcd8b80530e)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a new feature named 'perf-tui'. Adding this into the
PERF_FEATURES variable in perf.inc will enable the perf TUI (Text-base
UI) user interface on a target, which adds libnewt and turns on the
perf text UI options in perf, if perf is included in an image.
If 'perf-tui' isn't named as a feature (the default), the perf TUI
will be disabled and unavailable.
(From OE-Core rev: 4fd8a550886f02189e4ed127d0a2f16e92f8474c)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a new feature named 'perf-scripting'. Adding this into the
PERF_FEATURES variable in perf.inc will enable perf scripting on a
target, which will turn on all the language bindings currently
available in perf (Perl and Python), if perf is included in an image.
If 'perf-scripting' isn't named as a feature (the default), all perf
language bindings will be disabled and unavailable.
(From OE-Core rev: fc0661041436013b9099dbd659994a2b8b292c19)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a perf.inc to contain utility functions and definitions and to
avoid cluttering up the main recipe.
(From OE-Core rev: 414d00be5b350ea84fc7e1ff690f78b3396cfcd0)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 SRCREVs to pickup the following changes:
6297e4c perf: add sgidefs.h to for mips builds
69b7817 yaffs: add leading underscore to mtd_info function names
160f1ac yaffs: change type for mode to umode_t
2d875e8 Unionfs: use mode_t
(From OE-Core rev: 9d75c34948f5d961cff9d72fbaa628ff58821cc7)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating SRCREVs for the following fix:
Author: Tom Zanussi <tom.zanussi@intel.com>
Date: Tue Jul 10 09:38:40 2012 -0500
perf: add sgidefs.h to for mips builds
Allow Python.h to find the definitions it needs on mips i.e. get rid
of the error: "_ABIN32" is not defined.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
(From OE-Core rev: 04396899dc7973261404d5fbec3f85aa03a32e03)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This shouldn't be unconditional - a later patch made it so, but that's
not yet pulled in. In the meantime, to fix build failures remove the
unconditional install.
(From OE-Core rev: dcc43c34bfa9304233ecfd3f518a84ddfdc2fd90)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libexec/perf-core contains all the pre-canned scripts and modules
needed by both the Perl and Python bindigs. Add libexec/perf-core
along with all the pre-defined perf scripts underneath it.
(From OE-Core rev: 00f9e8aed9f111d351c2dc71cd8605ccbd11f68f)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add support to enable the perf Perl binding.
The build depends on perl-native to retrieve the configuration
settings needed for the binding. cpan-base adds some useful functions
like is_target() and get_perl_version() that we need for
PERLCONFIGTARGET and related settings, which allow us to use the
target's Config_heavy.pl settings for ExtUtils:Embed when building for
the target.
Also adds the perl-modules dependency to give the target the perl
modules that scripts using the binding need.
(From OE-Core rev: 73a8eed010a821fc4f5c0e71ef749938ed780b44)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add support to enable the perf python bindings. The combination of
these changes and the changes in the python-config sections in the
kernel Makefile enable all the python bindings currently available in
perf.
(From OE-Core rev: 487c3a72f0ac7121b79d2f78b81f1d4732bc258a)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #1614]
Add the kernel headers to the kernel-dev package. This packages what was
already built and kept in sysroots for building modules with bitbake.
Making this available on the target requires removing some additional
host binaries.
Move the location to /usr/src/kernel
Before use on the target, the user will need to:
# cd /usr/src/kernel
# make scripts
This renders the kernel-misc recipe empty, so remove it.
As we use /usr/src/kernel in several places (and I missed one in the
previous version), add a KERNEL_SRC_DIR variable and use that throughout
the class to avoid update errors in the future.
Now that we package the kernel headers, drop the
kernel_package_preprocess function which removed them from PKGD.
All *-sdk image recipes include dev-pkgs, so the kernel-dev package will
be installed by default on all such images.
(From OE-Core rev: 6125ea40d4483965f793bd847b3ce14b668a5b1e)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With recent kern tools changes, having a meta branch is opt-in. The
other linux-yocto recipes were updated, but linux-yocto-tiny was
missed.
Without specifying a meta branch, the kernel configuration audit
won't return any useful results, and throws a warning message.
WARNING: Can't find any BSP hardware or required configuration fragments.
WARNING: Looked at //cfg///hdw_frags.txt and //cfg///required_frags.txt in directory: //cfg//
NOTE: package linux-yocto-tiny-3.2.18+git1+ee78519365bdb25287703bbc31c06b193263c654_1+27b68a93eb791e830da8d3a2c0fc99780897ad89-r3.0: task do_kernel
(From OE-Core rev: 29dbe7d7ba66c66e9e5c8dc438f89d9b46c509a0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating preempt-rt in the 3.4 kernel to the latest upstream version
3.4.4-rt13.
(From OE-Core rev: f5ed8bc876fd24e4f08d29da06454037eec818e6)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the kernel version to v3.4.4 and importing the following
meta branch commits:
9b7c74b meta: bump kver to v3.4.4
8231dec ck: relocate config post patches
26b965e net_sched: remove dupicate configuration option
df8bf19 meta: remove non applying routerstationpro patch
292d8ea arm: import upstream versatile io.h fix
f4824b1 net_sched: select ACT as a dependency of INGRESS
30ae722 cgroups: delete obsolete namespace option
51f94f0 meta: add qemumipsel mapping
Built and boot tested on qemu*
(From OE-Core rev: 3d33b8c8b3be5dcdac30c115b9fec427269db2b4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta branch with a board description and configuration
that can be found from the linux-yocto recipes without doing a
MACHINE -> KMACHINE mapping.
From the meta branch commit:
The mti malta board description for a little endian config can't
be found by default unless it has a matching KMACHINE, or the
KMACHINE is set in a kernel recipe. In this case, it is easier to
just add qemumipsel in the KMACHINE list, so the recipe doesn't
need to do the mapping.
The little endian mips support reuses everything but the endianess
settings from the big endian mti malta board emulation.
This change adds the required mappings and SRCREVs, but does not
update the machine compatibilty, since official support is still
pending. The compatibility can be set in addon layers until that
time.
(From OE-Core rev: de2535b2bb47b80bdaeb3053b0ac0d1bbb9c5d53)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When making changes to kernel.bbclass, it would be nice not to have to
manually change the PR of every linux-yocto*.bb file that requires it.
Move the "require kernel" line to linux-yocto.inc and update the
linux-yocto recipes to use INC_PR.
(From OE-Core rev: 7a41d96c946029aeec03cd26f326bc6ca26e74fd)
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: Richard Purdie <richard.purdie@linuxfoundation.org>
In tree linux-yocto 3.0 boards indicate that they are BSPs via
the older/obsolete syntax "scc_leaf". This line in their board
description is detected by the build process and is used to find
the BSP description and the kernel type they use as their base.
To work with the latest kern tools, the BSP descriptions should
be updated to "include <ktype> branch <machine>" to acheive the
same result.
All trees newer than 3.0 already have this change and do not need
to be updated.
(From OE-Core rev: e32c993859337964033a285922dac3971e5add2d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
including following enhancement:
* support multi-dtb build
* skip dtb build and install when KERNEL_DEVICETREE is empty
* print a warning message when specified dts file is not available
(From OE-Core rev: 66f7921f34dfa8b3c7f8f7184715214164f3f8b0)
Signed-off-by: Zhenhua Luo <b19537@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the systemtap recipes to the recently released 1.8. Remove a
couple patches whose changes are already present in the new version.
(From OE-Core rev: 1c5a127d075ebf78b70d14e3ca1d0ff640a80cb8)
Signed-off-by: Wade Farnsworth <wade_farnsworth@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 SRCREVs to pickup build fixes for -rt, feature backports,
and a second set of 3.4 configuration audit results.
d65afd9 profiling: delete reference of obsolete CONFIG_X86_UP_APIC
9431490 meta: fix net_sched.cfg include
242149d meta: add CONFIG_VIRTIO_CONSOLE to virtio configuration
671a822 meta: resync series -> branches
e044ee1 rt: integrate patch to fix compile fail on certain configs
edac822 ktest: update with v3.5 content
182b8da net_sched: Add CODEL queue management algorithm.
c6adcd9 net_sched: move content out of cgroups dir
c8edb3e sys940x: branch before merge
6d06257 ext3: delete duplicate enablement settings.
6a5a2f8 ipv6: build in the core support vs. it being modular
e106230 ipv6: make standard and RT share a common config block
42996fb netfilter: coalesce bridge settings for standard and RT into a common file.
2b62fea netfilter: coalesce IPv6 settings for standard and RT into a common file.
d1c38c8 netfilter: coalesce IPv4 settings for standard and RT into a common file.
b5f9c7c preempt-rt: align with standard kernel type for basic cfg
ea33e01 cfg: move devtmpfs cfg/scc to cfg/fs dir
517eda4 preempt-rt: combine two config fragments into one
171a30a cgroups: re-enable net_traffic config fragment
86a599d cgroups: delete old blkio patches
8be6e5b netfilter: add comment documenting external bb use case
90e06bf x86[_64]: align with korg on HOTPLUG_PCI, HOTPLUG_PCI_PCIE and PCI_MSI
e103f7c seccomp: backport of BPF syscall filtering from v3.5
[YOCTO #1694]
(From OE-Core rev: 0c522dfabbf6b25488865a7653ea30f994d8177f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 3.4 kernel adopted the qemu machine name for the kernel branches, so
the 3.4-rt recipe needs to be updated to reflect that.
(From OE-Core rev: 9cec3f55cd2381c5d69c6f0911bd985311e2baf9)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the linux-yocto 3.4 SRCREV to import the -stable update
to v3.4.3.
(From OE-Core rev: 529d07cf663e671140ea99877e73db091d5a9734)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 kernel tree with some initial results of the 3.4
kernel configuration audit and refresh. This is the start of the
3.4 kernel configuration policy update and includes a refresh / update
with respect to kernel.org defaults and new categorization of
configuration fragments.
0f6975b Sched: Import base BFS-423 for v3.4
c517c5c cfg: strip off redundant path prefixes
689fd20 cfg: create timer subdir for HZ and HPET related settings
5367b46 cfg: add a fs dir for filesystem related configs
67a784b x86/x86_64: disable MTRR sanitizer
5da51ea x86/x86_64: consolidate ACPI and EFI settings
7627402 x86/x86_64: enable CONFIG_NO_HZ=y by default.
9ca6026 mips: select HZ=100 by default.
149efc6 arm: select HZ=100 by default.
29c9fc7 x86/x86_64: use HZ=1000
700b8b5 x86/x86_64: enable boot mem corruption checks; align with korg defaults
bbd054d x86: enable CONFIG_HIGHPTE=y by default.
2569871 x86: align to korg defconfig on IRQ fixups and microcode
ec5cdc2 x86/x86_64: enable SMP by default
b9932fa cfg: relocate/add a frag for HPET / RTC enablement
f9645f5 8250: separate out the 8250 configuration from feature dir
5e8fea0 bsp: tie cfg/x86.scc into all "KARCH i386" boards
4020ade cfg: make a common landing ground for ARCH=x86
e126316 cfg: add basic HZ fragments
4a8627b cfg: delete instances of any reference to dmesg buf size.
0794c16 routerstationpro: lib/kobject_uevent: switch to uevent_sock_mutex
[YOCTO #1694]
(From OE-Core rev: 92ff386b950879255802d3a74590fef36d160ba4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the kern-tools SRCREV to pickup the following functionality:
- buildall: provides the ability to build all kernel branches
without a build system, only a cross compiler and configme
are required.
- robustness/cleanups: obselete/unused code removal and general robustness
fixes from Paul Gortmaker and Bruce Ashfield
The following kern-tools commits are part of this series:
b8dfd3d buildall: add whitelist/blacklist support
0ef039c configme: catch errors found during fragment sanitization
5b6498c buildall: remove all instances of it using/reading scc files
2e57550 buildall: support semi seamless restarts
4b5dd4d kconf_check: simplify cmdline args, dont store data per branch
58fbb6e configme: relieve it of all knowledge of scc files
a03e291 configme: strip out alternative meta series logic.
96d2bcf kgit-init: check for valid branchpoint
5598db6 buildall: allow a max cap on the number of builds done
b46abec buildall: add support for randomizing build order
68a04e9 buildall: dont copy failed build logs into main build dir
5575d85 buildall: script to independently build all board kernels
86d6200 configme: delete unused variable
8d4e29d configme: delete unused KPROFILE setting
7e15436 configme: ensure we have a valid machine type set
152b9cb scc: remove depreciated/unused commands
bb4e96a scc: allow includes within conditional statements
7da7951 configme: derive path to tools from $0
152dc45 configme: test for BUILD_DIR != ""
129f7b0 kgit-scc: add warnings about bad input args.
e977662 kgit-scc: add text for no arg and invalid arg case.
[YOCTO #843]
(From OE-Core rev: be3cff86d55db6255e036d68e943e527802b4f4c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is now the authoratative repository, taking updates.
The latest has a couple updated license files, vs. the previous
srcrev that was used.
(From OE-Core rev: b9d42ec94dfcbe92ce2a857045a0e3678c05c26c)
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-libc-headers no longer needs its own ARCH mapping code,
since the mapping done in kernel-arch works and we can
consolidate all arch mapping code in a single place.
(From OE-Core rev: 7d73cfb2ae24ad2b694244c56dd4648ba7e2df11)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
perf has been moved to a standalone package, making linux-tools.inc
unecessary. It can now be removed and recipes that included it
updated.
(From OE-Core rev: b485f3e0e55ad62079ed0913970ff0620f4808ea)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
perf has been coupled to the kernel packages via kernel.bbclass.
While maintaining the build of perf out of the kernel source tree
is desired the package coupling has proved to be awkward in
several situations such as:
- when a kernel recipe doesn't want to build/provide perf
- when licensing of dependencies would prohibit perf and hence
the kernel from being built.
To solve some of these problems, this recipe is the extraction of
the linux-tools.inc provided perf compilation into a standalone
perf recipe that builds out of the kernel source, but is otherwise
independent.
No new functionality is provided above what the linux-tools.inc
variant provided, but the separate recipe provides baseline for
adding new functionality.
(From OE-Core rev: ab883d0c1a05bd99e97e5d71bc7bed05cb1ae8c8)
Signed-off-by: Liang Li <liang.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adding the 3.4 variant of the linux-yocto-rt recipe. This updates
to 3.4.1-rt9, and builds and boots on the supported targets.
(From OE-Core rev: 7f007994cbc5f188439ad2b26f60dbcc1c2763bd)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 SRCREVs to pickup a yaffs2 update and the removal
of a feature that was required in the 3.2 kernel tree.
1/2 [
meta: rc6: remove rc6 patches for snb
The sandybridge rc6 patches are part of the released v3.4 kernel.
Hence there is no need to keep these patches in the 3.4 linux
yocto kernel repository.
(From OE-Core rev: 7822565a3a3ae906112c88f7e59f396c7fdabd4c)
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
]
2/2 [
yaffs2: update core support
Uprev yaffs2 to latest version as of 2012-05-29
To include the following commits:
662466a yaffs2 checkpointing: Add further checkpoint data sanity checking
d9cae0a yaffs2: Make checkpoint block scanning skip bad blocks.
eb12d56 Remove trace that should not be in mounting.
9ee5d06 yaffs for u-boot: Cleanups to make patches acceptable for u-boot
83d9993 Merge remote branch 'origin/master'
07353dd Clean up checkin. Do not use
00ebf30 Update timothy test Makefile
1658295 yaffsfs: Allocate directory searches from a table rather than via malloc.
8dae7f1 Fix compilation of python tests.
14ff4e1 yaffs u-boot: Fix problem if an illegal nand chip number is entered.
8b34846 Set up u-boot glue code and patching scripts.
1a17e3a Add more descriptive comment for using the yaffs commands.
80f8530 Add files to hook up yaffs direct to u-boot
95ff7ef Merge branch 'master' of ssh://www.aleph1.co.uk/home/aleph1/git/yaffs2
e49491a Put both the summary and checkpoint version stamps together, update checkpoint version
468d72b Fix compilation of mkyaffsimage and mkyaffs2image
87166df Fix resizing of large files.
eeb0f17 Fix summary header validation
d308180 Add a summary header
7862c13 Remove extra line from banner.
d14c6a6 Add script to handle common Linux and direct files
6518138 Change Makefiles to support new way to structure yaffs_strxxx renaming for yaffs direct
8429784 Update README about linux patching
6ee2533 Update Makefiles for new sed-based way case-insensitive handling
2369fad Set up new version of case insensitive code using sed
4d8ae2f Add large file support changes to yaffs_vfs_single.c
ce0a5fb Merge branch 'big-files': Merge in large file support
80d031a Add Waldemar's patches for Linux 3.2
a7ae50c yaffs large file support: Fix max file size issue that prevented the scanning working.
a7cb3a3 WIP Changes to tests
2360446 yaffs large file support: Add more tests
0ed6086 yaffs large file support: Saves and restores large files fine under yaffs direct.
fc4028b large file storage WIP. Can save and verify a large file under yaffs direct.
20de150 WIP large file support
b4d93e2 First cut of changes to support large files.
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 3.4 kernel is released, and is the default for qemu* builds, so
we can safely update the default libc-headers version to 3.4.
Built and booted for qemu*
(From OE-Core rev: 3e57510bb11b350fbe15cae2fb5bf851956061ac)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove a stray character at the end of the meta SRCREV.
(From OE-Core rev: 009f7734e880084a5b01d8377cb006dc82f1d278)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the kern-tools SRCREV to pick up the following fix:
Out of tree feature descriptions (.scc files) take two forms: normal
features and BSP descriptions.
A normal feature is detected and added to the end of the current machine
being processed. During tree processing, it's configuration and patches
will be applied.
A BSP description on the other hand must be matched based on three
critera (which are in the .scc file via "define <foo>"):
- machine
- kernel type
- architecture
Since features that define machines are only explicitly added, they
are removed from the list of features that should be automatically
added.
The criteria for removing them from the auto-add list is the
definitions found in the .scc file. The existing check was simply
for KMACHINE anywhere in the file. This meant that a conditional
or even a comment containing that phrase would exclude a file.
Properly anchoring the KMACHINE test to "^define.*KMACHINE" fixes the
problem of overly agreesive exclusions.
(From OE-Core rev: 75a973328d50ef3c007edb7a471ea77fb97911ea)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating meta to move Kernel Features out of the BSP and add to
the Cedartrail Machine branch.
(From OE-Core rev: e44b616309dd8e442c7cd13c4c0b1a4ee41ac40f)
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the 3.2 SRCREVs to pickup the following configuration changes for
the new chiefriver BSP and the existing fri2 machines:
5b4c9dc fri2: update base config
cdfbb50 fri2: add usb-mass-storage to standard and preempt-rt
3c1af06 fri2 update: drop NETDEVICE, e1xxx, usb-mass-storage, add iwlwifi feature
26a4d79 iwlagn: Correct a comment typo
ade9c57 iwlwifi: Add a feature for iwlwifi
571b6cb fri2: Configuration update (usb, wifi, i2c)
b257485 meta: add tmp/rc6 feature
24c6494 chiefriver: create initial BSP infrastructure
All branches are also updated with the following fix:
1ce6700 efi: Add patch to fix 32bit EFI service mapping (rhbz 726701)
(From OE-Core rev: 0bef6360305c7d8cfa48e8132b3eeb2ac1b4236e)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Introducing the 3.4 kernel recipe. At this point there are three
supported kernel 3.4, 3.2 and 3.0.
Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and
qemuppc
(From OE-Core rev: f85c3f727fd326fe6dd2f2c2b68c692515867737)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>