openembedded-core.git/meta, branch master-next Mirror of openembedded-core tcf-agent: enable default target debugging features 2017-05-04T12:49:46+00:00 Gernot Hillier gernot.hillier@siemens.com 2017-04-26T10:57:45+00:00 5f311765b5f4bd6f4a768adab6a20d29230651ea 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-05-04T12:49:46+00:00 Gernot Hillier gernot.hillier@siemens.com 2017-04-26T10:57:44+00:00 e36b018dccf6909f3352d545bbdbed8b65355a09 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-05-04T12:49:46+00:00 Ross Burton ross.burton@intel.com 2017-04-25T16:07:08+00:00 95effa43d24b3ddfd489ca6dd991b1e292617ba7 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-05-04T12:49:46+00:00 Andre McCurdy armccurdy@gmail.com 2017-04-24T19:13:16+00:00 f371eb3334eb497a40f2a07f4694bff6e935400f 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-05-04T12:49:46+00:00 Ross Burton ross.burton@intel.com 2017-04-24T14:43:57+00:00 e1dd85c0fac171e2e99543705117acff9afd713b 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-05-04T12:49:46+00:00 Ming Liu peter.x.liu@external.atlascopco.com 2017-04-23T09:22:59+00:00 70b145715d335f5177b39dae398e789dc84f1fd3 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-05-04T12:49:46+00:00 California Sullivan california.l.sullivan@intel.com 2017-04-21T22:18:36+00:00 3fdce873a2a4aee2be169149ee9d2867c50b1667 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-05-04T12:49:46+00:00 California Sullivan california.l.sullivan@intel.com 2017-04-21T22:18:35+00:00 297be6619e3141c32cb1167cb91c4d4f13ff8248 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-05-04T12:49:46+00:00 Alexander Kanavin alexander.kanavin@linux.intel.com 2017-04-21T12:39:54+00:00 4483809d0b99428561dc4a4d95fdfa5cc46100ad 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-05-04T12:49:46+00:00 Nathan Lynch nathan_lynch@mentor.com 2017-04-25T22:33:55+00:00 f36d6a82339ddcc74a1f3801ef4360016704207a 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>