aboutsummaryrefslogtreecommitdiffstats
path: root/meta/classes/kernel.bbclass
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2016-08-31 10:54:11 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-08-31 22:00:03 +0100
commit478bc0bfcab68f4c129b6dfeaa91541030ea5e8d (patch)
treecbe75a498c628aecb08e1338619ccef05a389a72 /meta/classes/kernel.bbclass
parent73f064df931bf02595d3fc4b756531d25834137c (diff)
downloadopenembedded-core-contrib-478bc0bfcab68f4c129b6dfeaa91541030ea5e8d.tar.gz
oeqa/parselogs/qemuarm: Whitelist amba and jitter for 4.8+ kernels
With the update to the 4.8 kernel the versatile platform (and hence qemuarm) has switched to a device tree boot. We are using an ummodified mainline kernel versatilepb device tree, which includes definitions of multiple amba devices. These devices are not present in the qemu system emulation, hence throw warnings during boot. These warnings are not unique to oe-core, and rather than carry kernel patches to the device tree (for now), we whitelist the known warnings so qa testing will pass. We also can't turn amba off completely, since it is providing valid devices (like the serial port) and AMBA is force selected by other kconfig values. We also have a jitterentropy warning that shows up on some hosts. This warning is harmless, and like amba we can't turn it off in a fragment since it is force selected by crypto (and we'd rather not turn all crypto off). So we add it to the whitelist while investigations continue into what is needed in the host to support this fully. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/kernel.bbclass')
0 files changed, 0 insertions, 0 deletions