Updating the linux-yocto-3.8 SRCREVs to fix a boot issue with ARM boards
when gcc 4.8 is used.
Without the following mainline backports:
f200475 ARM: 7670/1: fix the memset fix
8215b0e ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations
The following trap will be seen on boot:
[<c00fc3b8>] (kmem_cache_alloc_trace+0x54/0x210) from [<c039f074>] (con_insert_unipair+0xcc/0x11c)
[<c039f074>] (con_insert_unipair+0xcc/0x11c) from [<c039fec8>] (con_set_default_unimap+0xfc/0x198)
[<c039fec8>] (con_set_default_unimap+0xfc/0x198) from [<c07ee258>] (console_map_init+0x44/0x58)
[<c07ee258>] (console_map_init+0x44/0x58) from [<c07ee738>] (vty_init+0x16c/0x1b0)
[<c07ee738>] (vty_init+0x16c/0x1b0) from [<c07edb68>] (tty_init+0x108/0x148)
[<c07edb68>] (tty_init+0x108/0x148) from [<c07eead0>] (chr_dev_init+0xb4/0xd8)
[<c07eead0>] (chr_dev_init+0xb4/0xd8) from [<c0008a18>] (do_one_initcall+0x11c/0x18c)
[<c0008a18>] (do_one_initcall+0x11c/0x18c) from [<c07d89d0>] (kernel_init_freeable+0x16c/0x254)
[<c07d89d0>] (kernel_init_freeable+0x16c/0x254) from [<c05a3810>] (kernel_init+0x18/0x160)
[<c05a3810>] (kernel_init+0x18/0x160) from [<c000e530>] (ret_from_fork+0x14/0x20)
Code: e593a000 e35a0000 0a000020 e5943014 (e79a1003)
---[ end trace e6c62de166779f86 ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Moderate stress and board testing shows the fix to hold, and it is good for
broader testing.
[YOCTO #4549]
(From OE-Core rev: 8ef393bc08a20053765ad58c1ebd9ab621cdd704)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Moving forward we plan to support two kernels plus the development
kernel. That leaves 3.2 as the next kernel to be dropped. Support
for this version will be carried in the sustained/old releases.
(From OE-Core rev: b8d53d8f91bd1b165016ea1063868c8b15f07ce0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the -stable linux-yocto trees to the latest korg -stable releases.
(From OE-Core rev: 00e0ec6c1441815a7605753e8888e45244900b63)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When qemumips64 was enabled, its machine specific SRCREV was missed.
Without it, qemumips64 builds from the wrong branch and we miss important
oprofile/ftrace fixes that are required for boot.
(From OE-Core rev: 6c94a53f7c1b674927486fdbf81613b2832bae40)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 3.8 and linux-yocto-dev kernel trees carry qemumips64 support. Adding
the board to the compatibility directly in the recipes is the first step
to adding mips64 support to the broader set of packages.
(From OE-Core rev: 0b4187fac16f78a1f9ba1c696edbc8c2aa189cb1)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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>
There are some left over tab characters in the python functions. This
removes them and resolves python 3 errors.
(From OE-Core rev: fafeb381c48291fa65c634c01c244843c8d7fad3)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the yocto 3.4 SRCREVs for the following fixes:
206d4bb powerpc/perf: run irq-work under softirq context in rt
8a969f9 arm/perf: run irq-work under softirq context in rt
79ba946 iwlwifi: fix unused variable warning
59d93fa ext4: remove unused variable in ext4_update_super()
2385eee Btrfs: fix compile warnings in extent_io.c
(From OE-Core rev: 96113b28031583af1dd42fe7660a9d5ced36d1b6)
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 shutdown sanity test that we previously saw on qemux86-64 in 2.6.37 have
started to re-appear reproducably on qemux86 in 3.4 in the Danny series. Until
this can be root-caused and fixed in the kernel, disable paravirtualisation
across all kernels and all qemu machines.
[ YOCTO #4196 ]
(From OE-Core rev: e20c3bf6ce0d8ab5653739dd02555186b78b8912)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Commit a2546fae [ftrace: Add -mfentry to Makefile on function tracer]
adds support for using -mfentry when possible, whenever the ftrace
CONFIG_FUNCTION_TRACER option is enabled.
This unfortunately causes bogus dwarf debuginfo to be generated:
gcc Bug 54793 - the location of a formal_parameter is not started from a
function entry with -mfentry
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54793
This can be fixed by applying the gcc patch above, which will be
present in gcc-4.8, but in the meantime, the problem is currently
being worked around in different ways by various tools. One of those
tools that we support in Yocto, Systemtap, requires the DW_AT_producer
string contain -mfentry, which means that it's assuming
record-gcc-switches is also used:
SystemTap Bug 15123 - workaround for bad debuginfo for -mfentry
http://sourceware.org/bugzilla/show_bug.cgi?id=15123
The lack of -grecord-gcc-switches and therefore a missing -mfentry
string in Yocto leads to the following Yocto bug:
Bug 4099 - Crosstap script check fails
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4099
Which is what this patch intends to fix.
It only affects architectures that HAVE_FENTRY when
CONFIG_FUNCTION_TRACER is turned on and in any case is just adding to
the debuginfo, so there doesn't seem to be much risk to adding it.
(From OE-Core rev: c04f611aa4bf77867fe78a005d09434226feb62c)
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A regression was introduced when implementing the ability to restrict
configuration values via include directives. Only patch and config files that
were local to a feature directory could be found. While this doesn't impact
most users of the tools, it is an issue that needs to be fixed.
Additionally, the regex that detected flags passed to includes was not
specific enough, and unfortunately named feature files would match. This
resulted in features like standard-nocfg.scc inhibiting all configuration
items, even base configs.
This change also bumps the linux-yocto 3.4 and 3.8 PR values to ensure
that kernels will be rebuilt once this change is active.
(From OE-Core rev: ddce9f375c626ef2c86f48612b3d7a24e3111b0b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the linux-yocto-3.8 recipes to fix two issues:
1) qemumips boot
This is fixed by:
Revert "Input: i8042-io - fix up region handling on MIPS"
And by disabling ftrace for qemumips boards
2) netfilter options being dropped
When KERNEL_EXTRA_FEATURES was introduced, and allowed to be
inhibited, the variable was only applied to qemux86 machines. It
should be applied ot all machine types (unless inhibited), so we
restore that functionality.
(From OE-Core rev: 0271dec64591c4d91933b3a8db875a374a63640b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREV to fix and illegal instruction that is seen
when launching X with USB pointing devices.
meta/qemumips: build USB_UHCI_HCD into the kernel
When booting qemumips and USB_UHCI_HCD built as a module, the following
trace is seen, and then prevents X from starting:
qemumips user.warn kernel: Call Trace:
qemumips user.warn kernel: [<c0028000>] uhci_check_bandwidth+0x0/0x160 [uhci_hcd]
qemumips user.warn kernel: [<c002e08c>] uhci_urb_enqueue+0xba4/0xc48 [uhci_hcd]
qemumips user.warn kernel: [<8058092c>] usb_hcd_submit_urb+0xdc/0x848
qemumips user.warn kernel: [<805b8fbc>] wacom_open+0x44/0x8c
qemumips user.warn kernel: [<805a1990>] input_open_device+0xac/0xec
qemumips user.warn kernel: [<805a8cec>] evdev_open+0x188/0x1bc
qemumips user.warn kernel: [<802331d8>] chrdev_open+0xc8/0x1c4
qemumips user.warn kernel: [<8022b338>] do_dentry_open+0x248/0x2e4
qemumips user.warn kernel: [<8022b418>] finish_open+0x44/0x68
qemumips user.warn kernel: [<8023e51c>] do_last.isra.29+0x2c0/0xcbc
qemumips user.warn kernel: [<8023efd8>] path_openat+0xc0/0x52c
qemumips user.warn kernel: [<8023f840>] do_filp_open+0x4c/0xbc
qemumips user.warn kernel: [<8022cc3c>] do_sys_open+0x128/0x20c
qemumips user.warn kernel: [<8010c07c>] stack_done+0x20/0x44
qemumips user.warn kernel: Code: (Bad address in epc)
qemumips user.warn kernel: ---[ end trace 8a48c6046870f8c2 ]---
Building the module into the kernel fixes the problem, but the root
cause is still under investigation. The pipelines around jumps to
module addresses seem to be triggering invalid instructions.
(From OE-Core rev: b7b7ebe57bd6fd248e80be0b7e517a3ceb7cfd11)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREVs to fix a number of bugs, boot issues and ktype support
additions.
standard/*:
Aufs support was misplaced on the move from the -dev to release kernel, this
commit restores the support. This is not active unless the aufs configuration
items are enabled via the aufs-enable.scc feature.
11998bd aufs: core support
f2ea9f4 aufs: standalone support
bf529b6 aufs: aufs proc_map
b6f0a04 aufs: aufs base support
55b0bc2 aufs: kbuild patch
meta:
The meta branch has updates for aufs enablement, tiny BSP configs, preempt-rt
fixes and a wifi config audit fix.
4c567e0 meta/aufs: add -enable feature and patches
059fe88 meta/aufs: create aufs configuration fragment
7d672cd0 meta: add fri2 tiny BSP config.
mti-malta32:
This fixes the graphical boot of qemumips, the offending commit is breaking
dynamic patching of ftrace on the simulation, so we revert the commit for now.
18c71ab Revert "ftrace/x86: Have x86 ftrace use the ftrace_modify_all_code()"
mti-malta64:
This enables the boot of qemumips64 by reverting the broken ftrace support for
mips64 and by stubbing out inavlid oprofile register writes.
0ec615c Revert "ftrace/x86: Have x86 ftrace use the ftrace_modify_all_code()"
bbefde3 oprofile/mips: do not set perf_irq for qemu mips 64
eb6cb79 Revert "MIPS: Function tracer: Fix broken function tracing"
[YOCTO #4052]
[YOCTO #4129]
[YOCTO #2410]
(From OE-Core rev: 3d88f61b59f0a07e199306bf3a15ab023e77e17d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta branch SRCREV to pick up the following change:
The atom-pc preempt-rt BSP was omitting the config from common-pc,
resulting in very few drivers being built, including USB_STORAGE,
preventing preliminary boot testing.
Remove the "standard features" as those are covered by the common-pc
scc files.
(From OE-Core rev: 1e20b3cbc8da3e6729d3825c62422c0dd82e1577)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The atom-pc was referencing some invalid and unecessary config
options that are causing kernel config audit warnings.
With this SRCREV update, the configuration is clean against the
3.8 kernel.
[YOCTO #3490]
(From OE-Core rev: 9f3ff1f907a0cf65d8aff82134463c4321d4b1e2)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When systemd is enabled, qemumips failed to boot with the following trace:
Reserved instruction in kernel code[#1]:
Cpu 0
$ 0 : 00000000 80232500 c0011000 80000000
$ 4 : c0017440 00000000 87032400 8704b000
$ 8 : 00000000 00000000 00000010 003fffff
$12 : 00000000 7fafbab4 00000000 87d6fbb0
$16 : 87f98780 c0017440 c0017440 00000000
$20 : 8704a000 00000000 8704a000 00000000
$24 : 00000010 80480630
$28 : 87c22000 87c23e28 7fafbc00 80232408
Hi : 00000000
Lo : 00000000
epc : c0011000 autofs_mount+0x0/0x30 [autofs4]
Not tainted
ra : 80232408 mount_fs+0x68/0x200
Status: 1000a403 KERNEL EXL IE
Cause : d0808028
PrId : 00019300 (MIPS 24Kc)
Modules linked in: autofs4
Process systemd (pid: 1, threadinfo=87c22000, task=87c28000, tls=77787490)
Stack : 809b3e28 802512bc 00000000 808b0da4 87f3d310 87936c38 87032400 8704b000
87f98780 c0017440 00000020 8704b000 87032400 87032480 00000000 80251a2c
00000006 8022f7fc 87032480 802507f0 00000000 87032400 8704b000 7fafba94
00000000 c0017440 8088275c 80253f40 7fafb9d0 00000016 38513fac 0051b2a8
8704b000 801df604 00000000 0000000a 87f5c000 801f5968 87f3d310 87936c38
...
Call Trace:
[<c0011000>] autofs_mount+0x0/0x30 [autofs4]
[<80232408>] mount_fs+0x68/0x200
[<80251a2c>] vfs_kern_mount+0x68/0x114
[<80253f40>] do_mount+0x218/0x9d0
[<8025479c>] sys_mount+0xa4/0xec
[<8010c07c>] stack_done+0x20/0x44
The policy of building AUTOFS as a module is something that can be
changed, since boot processes that use automounting can take advantage
of the built in support to reduce complexity.
The size increase of the base policy is small with this change, and
users of the linux-yocto kernel can still override this value, which
is exactly what the poky-tiny kernel does.
Keeping the configuration consistent for all boards, and not adding
and exception for qemumips makes sense in this case.
[YOCTO #4129]
(From OE-Core rev: 3570cf11b7dfa6991c43bb041abb9d47cc6f0d70)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bring linux-yocto-tiny up to the latest linux-yocto 3.8.4 version.
(From OE-Core rev: f2a2256f08287baac9cf1f9fd58b5b8244c09610)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fix the whitespace in the base functions to use TAB instead
of spaces. This is to address feedback from:
Darren Hart <dvhart@linux.intel.com>
(From OE-Core rev: ab6630df4d100ff501b33a1c7ec9d1e6a2d4f0ee)
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* This is similar to the symlinks provided for the kernel image
in the /boot directory of a file system. The goal is to have
simply named symlinks in /boot that mirror the device tree
name in the kernel sources. This is so that programs like
U-Boot can easily find the default device tree binary in the
/boot directory and use that when booting the kernel.
* Use update-alternatives to handle proper creation and removal
of the symlinks.
(From OE-Core rev: 750a9554e1b85d9bd23d18e0630723c3c193c604)
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to 3.8.4-rt2 to fix the minor issues found with -rt1.
>From the upstream commit log:
changes since v3.8.4-rt1:
- build fix for i915 (reported by "Luis Claudio R. Goncalves")
- build fix for fscache (reported by tglx)
- build fix for !RT (kernel/softirq.c did not compile)
- per-cpu rwsem fixed for RT (required only by uprobes so far)
- slub: delay the execution of the ->ctor() hook for newly created
objects. This lowers the worst case latencies.
Known issues:
- SLxB is broken on PowerPC.
(From OE-Core rev: cd9a730caf6b995c25c71c97eb76dc7a24ecf641)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
During the 3.8.4 integration there was a build issue on MIPS due to
SA_RESTORER changes. A solution was put in place for mips, but it
didn't cover other impacted architectures.
This is a backport of the proposed fix for the next 3.8-stable,
since the full -stable might not be available in the right timeframe.
(From OE-Core rev: 1d7a5ac1cea1a5bdb6a9d3dd822439c070066272)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The preempt-rt kernel was wasn't inheriting the standard kernel
configuration and hence was not able to boot on qemuarm due to
missing ABI options.
Changing the main preempt-rt kernel include to inherit standard
configuration again fixes this boot issue.
(From OE-Core rev: d569f44c296f6de1f7bb6ad9f581c237d5947321)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.8 SRCREVs with the following fix:
libtraceevent: Remove hard coded include to /usr/local/include in Makefile
commit b9e8c37220c80e78289a1e87b50c09418eb59a7e upstream
having /usr/local/include hardcoded into the makefile is not necessary
as this is automatically included by GCC. It also infects cross-compile
builds with the host systems includes.
Signed-off-by: Jack Mitchell
Acked-by: Namhyung Kim
Cc: Ingo Molnar
Cc: Paul Mackerras
Cc: Peter Zijlstra
Link: http://lkml.kernel.org/r/1362741712-21308-1-git-send-email-ml@communistcode.co.uk
Signed-off-by: Arnaldo Carvalho de Melo
This implements the fix I described in Yocto [BUG #3993][perf using
host includes], now upstream.
Integrated-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
[YOCTO #3993]
(From OE-Core rev: 90d9147068a6e2c766976b2092d5e188c45a9040)
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 tree to import the korg -stable fixes for v3.4.36.
(From OE-Core rev: 19d77ddf6c5d7822b757342a4e41ea68403889c3)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The -rt series has been updated for the 3.8 kernel. Updating the
SRCREVs to reflet its import into the tree.
(From OE-Core rev: 1daa242e78a5fddb1ae60b79f990811c85058943)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the base v3.8 kernel to the 3.8.4 -stable version.
(From OE-Core rev: 81e599c9f24c0a8937694c66ae349fcb8f618f38)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It was pointed out that the current way the KERNEL_FEATURES variable
is appended in the base linux-yocto recipe doesn't allow the appended
features to be prevented in a layer without using python code and
a recipe finalize hook.
To allow easier overriding of 'extra' or 'optional' features that are
defined in the linux-yocto recipe, we create a KERNEL_EXTRA_FEATURES
variable. This variable can be set in a layer to define extra features
or cleared to prevent the recipe's extra features from being appended
to the core functionality.
(From OE-Core rev: 779cb6e51fab87e00784bd97ec4771e69a79cf82)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The sched_deadline configuration fragmements were not optimal, so tweaking
the meta data to make an enable-only configuration fragment avaiable and
updating the options within that fragment.
(From OE-Core rev: 43d2ae5695844d29ccad2c8a2760b803352d1f67)
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.8 SRCREVs to reflect the integration of the
korg 3.8.1 -stable release.
(From OE-Core rev: 75e247ed9a8a731480bef3ab0753fbad200469be)
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 3.4 SRCREVs to incorporate the -stable release of 3.4.34 and
the latest LTSI fixes up to [36a9caf 2 more fixes added].
(From OE-Core rev: e5602b0414fca0183d5aa90d9b462ac8e8401cbb)
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>
Introducing the linux-yocto 3.8 kernel recipe. The tools and branch structure
of this tree are the same as the previous linux-yocto recipes, while the meta
data and content have been updated for the 3.8 kernel.
build and boot tested for qemu*.
(From OE-Core rev: ecf287a80c5ace2c440f8d0089934d59d25dc3ec)
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>
Some existing KERNEL_FEATURE references use a shorcut notation, but mapping
these shortcuts to actual .scc files in the tree are not obvious. So we clarify
where they are found by referencing the full .scc filename in the KERNEL_FEATURE
addtions.
(From OE-Core rev: 26c71c895e1d56d2f3576de833a576137e970fcc)
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 SRCREVs to pick up the 3.4.28 -stable update
as well as the 3.4.28-rt40 refresh.
(From OE-Core rev: f8619d777e734f3886b02bf87157761a6f78029b)
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 linux-yocto-dev recipe uses the upstream tracking linux-yocto-dev repository.
Since this tree is frequently updated, and periodically rebuilt, AUTOREV is used
to track its contents.
This recipe is just like other linux-yocto variants, with the only difference
being that to avoid network access during initial parsing, static SRCREVs are
provided and overridden if the preferred kernel provider is linux-yocto-dev.
(From OE-Core rev: 378f99eeab070e2fcea84fb47f37cd7cb15caa90)
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 2.6.37 kernel on the AB occasionally fails dmesg and shutdown
tests with general protection faults.
(From OE-Core rev: 64749308fadabb4aa7c39f360c6395827bc5eb3a)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta branch to import the following commits that cleanup and
reorganize the features that make up the graphics features of the Intel
BSPs
c0b3904 meta: add config fragment for gma600 graphics driver
f41638f meta: add config fragment for gma500 graphics driver
ff8ad3e meta: sys940x: drop vesa fragment from bsp config
fcb82ac meta: sys940x: remove emgd config from bsp config
c1677bb meta: fri2: drop vesa fragment from bsp config
7324440 meta: fri2: remove emgd config from bsp config
dd435c6 meta: emenlow: drop vesa fragment from bsp config
243b515 meta: emenlow: remove emgd config from bsp config
3e1be82 meta: crownbay: drop vesa fragment from bsp config
fc5ed4e meta: crownbay: remove emgd config from bsp config
d46236b meta: drm-emgd.cfg: add configs for dependent routines
db4bc5e meta: relocate git-merge of emgd branch
(From OE-Core rev: 8d0074ef2b61bf022ed1bb3b5f1afe526d8c921b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the yocto 3.4 kernel tree to the 3.4.25 and 3.4.26 -stable updates
as well as refreshing the preempt-rt branches to 3.4.25-rt37.
(From OE-Core rev: da536703bdcf31c8c2ef17f5a49d06280fe77600)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the linux-yocto-3.4 SRCREVS to activate the merge of the 3.4.25-ltsi
tree:
http://git.linuxfoundation.org/?p=ltsi-kernel.git;a=tag;h=refs/tags/v3.4.25-ltsi
The pristine patch queue can be seen on the "ltsi" branch in the repository.
This branch has been merged into the standard/base branch of linux-yocto-3.4
and to all BSP branches in the tree.
LTSI based BSPs or features are not activated as part of this commit, they
are controlled by the meta branch of the kernel repository and are activated
in separate patches.
[YOCTO #2396]
(From OE-Core rev: 8f03ebe9b164e0c0493c56d9eb2e7d0b039832f1)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We had a request to enable GPIO_SYSFS to allow easy use of the available
GPIOs in the board out of the box. This is a simple / contained config item
to enable, so there's no reason not to.
[YOCTO #3519]
(From OE-Core rev: 9a5948ff07b62f54d6215d37e9028384d3b430da)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel tooling can support a "shorthand" method of including other features
that doesn't require the full filename ending in .scc. This format is confusing
when compared to the source tree, and is inconsitently use. This commit updates
all shorthand includes to a full "include <foo>.scc" format.
[YOCTO #3418]
(From OE-Core rev: acf015f079907da8a4f1b80e44bb64bc7696a6ad)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto-tiny and linux-yocto had minor differences from the rest
of the linux-yocto recipes. After this commit, all the recipes are
using bareclone=1 and repository names that end with .git.
(From OE-Core rev: 1acf3ad17bbc1cdcad31c243b7b50daaea99ee7a)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREVs to integrate the korg -stable updates.
(From OE-Core rev: 88856144bf97630f4c43fd7c984343caf287a435)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The meta data branch for the kernel can be varied by changing the
KMETA variable, but that change wasn't reflected in the SRC_URI,
which means that the fetcher won't check for changes on that branch
and is a potential source of errors.
Making the meta branch specification KMETA vs meta solves the problem.
(From OE-Core rev: 5bfc678aeb65b50710384e93b64add3a62146908)
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 SRCREVs for the following commit:
[
meta/emenlow: use emgd instead of psb graphics driver
This commit essentially does just this:
Remove all the references of psb patches for emenlow BSP.
Change the emenlow scc files to use emgd instead of psb.
]
(From OE-Core rev: 06a2b9eb087d1d90213d67dc8fe14c53201afe37)
Signed-off-by: Nitin A Kamble <nitin.a.kamble@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>
