openembedded-core.git/meta, branch master-next2 Mirror of openembedded-core tcf-agent: enable default target debugging features 2017-04-28T10:32:21+00:00 Gernot Hillier gernot.hillier@siemens.com 2017-04-26T10:57:45+00:00 004332fc15358c4088686babffd3b038798f420a A number of features were disabled in OE due to historic problems on ARM. In tcf-agent 1.4, they compile cleanly on all architectures besides mips and libc-musl. These features are required for target debugging with Eclipse Neon, CDT and TCF plugins - for example used by Xilinx Vivado SDK 2016.4. For MIPS and libc-musl, at least re-enable SERVICE_Symbols and SERVICE_LineNumbers which compile cleanly. Signed-off-by: Gernot Hillier <gernot.hillier@siemens.com> Signed-off-by: Tim Offermann <tim.offermann@siemens.com> Acked-by: Eugene Tarassov <eugene.tarassov@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
A number of features were disabled in OE due to historic problems
on ARM. In tcf-agent 1.4, they compile cleanly on all architectures
besides mips and libc-musl. These features are required for target
debugging with Eclipse Neon, CDT and TCF plugins - for example used
by Xilinx Vivado SDK 2016.4.

For MIPS and libc-musl, at least re-enable SERVICE_Symbols and
SERVICE_LineNumbers which compile cleanly.

Signed-off-by: Gernot Hillier <gernot.hillier@siemens.com>
Signed-off-by: Tim Offermann <tim.offermann@siemens.com>
Acked-by: Eugene Tarassov <eugene.tarassov@xilinx.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
tcf-agent: fix machine setting for arm64 build 2017-04-28T10:32:21+00:00 Gernot Hillier gernot.hillier@siemens.com 2017-04-26T10:57:44+00:00 c93691b3d8b300d5cdeb1c9f1a052f7c32bba23b tcf-agent uses "a64", not "aarch64", see agent/Makefile.inc. This fix allows to re-enable features like SERVICE_Breakpoints and SERVICE_ MemoryMap on arm64. Signed-off-by: Gernot Hillier <gernot.hillier@siemens.com> Acked-by: Eugene Tarassov <eugene.tarassov@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
tcf-agent uses "a64", not "aarch64", see agent/Makefile.inc. This fix
allows to re-enable features like SERVICE_Breakpoints and SERVICE_
MemoryMap on arm64.

Signed-off-by: Gernot Hillier <gernot.hillier@siemens.com>
Acked-by: Eugene Tarassov <eugene.tarassov@xilinx.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libcap: clean up gperf enabling logic 2017-04-28T10:32:21+00:00 Ross Burton ross.burton@intel.com 2017-04-25T16:07:08+00:00 abaaeeff07c88fb52a4fa70d33ed6c7946d086b2 There's no need to sed the Makefile (especially the wrong Makefile) when there's a variable we can pass. Signed-off-by: Ross Burton <ross.burton@intel.com> 
There's no need to sed the Makefile (especially the wrong Makefile) when there's
a variable we can pass.

Signed-off-by: Ross Burton <ross.burton@intel.com>
gnutls: move BBCLASSEXTEND from gnutls.inc into the gnutls recipe 2017-04-28T10:32:21+00:00 Andre McCurdy armccurdy@gmail.com 2017-04-24T19:13:16+00:00 bf901ae5a467c91758a894d4901bda93c3031bd0 There may be alternative gnutls recipes outside oe-core which include gnutls.inc but which don't want BBCLASSEXTEND = "native nativesdk". Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
There may be alternative gnutls recipes outside oe-core which include
gnutls.inc but which don't want BBCLASSEXTEND = "native nativesdk".

Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
python3: add python3 metapackage 2017-04-28T10:32:21+00:00 Ross Burton ross.burton@intel.com 2017-04-24T14:43:57+00:00 e168769fc57275fa41c704acb74ca0cea1c6a2ae Many new users add "python3" to their image using IMAGE_INSTALL and are then surprised that they can't import any of the standard library. This is because we split up the standard library into a number of packages, and python3-core (the interpreter and essential modules only) RPROVIDES 'python3'. Solve this by moving the RPROVIDES of 'python3' to python3-modules, so that the entire Python standard library is installed. [ YOCTO #11182 ] Signed-off-by: Ross Burton <ross.burton@intel.com> 
Many new users add "python3" to their image using IMAGE_INSTALL and are then
surprised that they can't import any of the standard library. This is because we
split up the standard library into a number of packages, and python3-core (the
interpreter and essential modules only) RPROVIDES 'python3'.

Solve this by moving the RPROVIDES of 'python3' to python3-modules, so that the
entire Python standard library is installed.

[ YOCTO #11182 ]

Signed-off-by: Ross Burton <ross.burton@intel.com>
classes/image_live: allow different filesystems to be used for live images 2017-04-28T10:32:21+00:00 Ming Liu peter.x.liu@external.atlascopco.com 2017-04-23T09:22:59+00:00 2152700f2b94c2c9d6810f3521b90ebb32a01b1b The idea is copied from commit df0b217f3df2c36a32e5c4afaec36a28bfc77bbb: [ classes/image_vm: allow different filesystems to be used for VM images ] The same logic should apply to image_live.bbclass, to allow other filesystems to be used vs just ext4. The default value of ext4 is kept so there is no functional change unless LIVE_ROOTFS_TYPE is set in the inherting recipe. Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
The idea is copied from commit df0b217f3df2c36a32e5c4afaec36a28bfc77bbb:
[ classes/image_vm: allow different filesystems to be used for VM images ]

The same logic should apply to image_live.bbclass, to allow other
filesystems to be used vs just ext4. The default value of ext4 is kept
so there is no functional change unless LIVE_ROOTFS_TYPE is set in the
inherting recipe.

Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
parselogs: whitelist failed to enable keyboard error on intel-corei7-64 2017-04-28T10:32:21+00:00 California Sullivan california.l.sullivan@intel.com 2017-04-21T22:18:36+00:00 f0dcc27ce2377d0a3fb706fe8952718f4a3ab440 This error is seen on the Braswell RVP platform we have been using for testing. The error is caused by atkbd.c keyboard driver, which is only for AT and PS/2 keyboards. I tested a PS/2 keyboard with the board, which worked fine, and the board does not have a separate AT connector, so this error won't cause any functional issues. [YOCTO #10110]. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
This error is seen on the Braswell RVP platform we have been using for
testing. The error is caused by atkbd.c keyboard driver, which is only
for AT and PS/2 keyboards. I tested a PS/2 keyboard with the board,
which worked fine, and the board does not have a separate AT connector,
so this error won't cause any functional issues.

[YOCTO #10110].

Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
parselogs: whitelist bluetooth firmware load error for intel-corei7-64 2017-04-28T10:32:21+00:00 California Sullivan california.l.sullivan@intel.com 2017-04-21T22:18:35+00:00 7cdb98b28453be95020e92701502fc0cbcf1287d The NUC6 has issues bringing up Bluetooth early in the boot sequence. We see: [ 4.091790] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 4.097326] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 4.145317] Bluetooth: hci0: Failed to send firmware data (-38) Followed by this later on: [ 11.509870] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.509988] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 13.090308] Bluetooth: hci0: Waiting for firmware download to complete [ 13.090829] Bluetooth: hci0: Firmware loaded in 1549114 usecs [ 13.090987] Bluetooth: hci0: Waiting for device to boot [ 13.101958] Bluetooth: hci0: Device booted in 10818 usecs Bluetooth does successfully come up and the firmware is loaded. This behavior is consistent across all kernels I've tested. [YOCTO #10628]. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
The NUC6 has issues bringing up Bluetooth early in the boot sequence. We
see:

[    4.091790] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    4.097326] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[    4.145317] Bluetooth: hci0: Failed to send firmware data (-38)

Followed by this later on:

[   11.509870] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.509988] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[   13.090308] Bluetooth: hci0: Waiting for firmware download to complete
[   13.090829] Bluetooth: hci0: Firmware loaded in 1549114 usecs
[   13.090987] Bluetooth: hci0: Waiting for device to boot
[   13.101958] Bluetooth: hci0: Device booted in 10818 usecs

Bluetooth does successfully come up and the firmware is loaded. This
behavior is consistent across all kernels I've tested.

[YOCTO #10628].

Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
libxml2: move python module to Python 3 2017-04-28T10:32:21+00:00 Alexander Kanavin alexander.kanavin@linux.intel.com 2017-04-21T12:39:54+00:00 21451351d9662bbf2a6f4048f383a39b6082f958 Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
lttng-modules: work around GCC 7 changes 2017-04-28T10:32:21+00:00 Nathan Lynch nathan_lynch@mentor.com 2017-04-25T22:33:55+00:00 b1234fc02e50c91ce9c83b2fd20c16e98cf207a8 Avoid using LTTng's BUILD_RUNTIME_BUG_ON macro, as it appears to run into a similar problem as Linux experienced with __builtin_constant_p and dead code elimination. Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Avoid using LTTng's BUILD_RUNTIME_BUG_ON macro, as it appears to run
into a similar problem as Linux experienced with __builtin_constant_p
and dead code elimination.

Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>