Paul Eggleton [Mon, 4 Apr 2016 05:02:20 +0000 (17:02 +1200)]
classes/buildhistory: fix filtering of depends-nokernel.dot
For images we produce a number of filtered dependency .dot files for
readability, the first of which is depends-nokernel.dot which filters
out just the kernel itself (not kernel modules). Unfortunately the
filter specifications hadn't been updated for the dash-to-underscore
removal or the 4.x kernel upgrade, thus the filtering wasn't actually
doing anything.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Mon, 4 Apr 2016 05:02:19 +0000 (17:02 +1200)]
classes/buildhistory: optimise getting package size list
Invoking oe-pkgdata-util in turn for every package in the list was slow
with a large image. Modify oe-pkgdata-util's read-value command to take
an option to read the list of packages from a file, as well as prefix
the value with the package name; we can then use this to get all of the
package sizes at once. This reduces the time to gather this information
from minutes to just a second or two.
Fixes [YOCTO #7339].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Sun, 3 Apr 2016 09:09:49 +0000 (10:09 +0100)]
populate_sdk_ext: Exclude BBTASKDEPDATA from task signature
Otherwise the task hash changes between server and worker context
leading to changing task checksums. The dependency data here is
tracked by other pieces of the signature.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Sat, 2 Apr 2016 00:09:26 +0000 (20:09 -0400)]
kernel-yocto: enforce SRC_URI specified branch
During the simplication and cleanup of branches and kernel meta data
handling, the ability to force build a branch that didn't match the
meta data was dropped.
There are valid uses cases when a different branch should be built
(testing, development, etc), so we restore the capability with this
change.
If after the kernel meta data is processed the current branch does
not match the SRC_URI specified branch, a warning is generated
about the impending branch switch and that the user should double
check that they are building what they expect.
WARNING: After meta data application, the kernel tree branch is standard/base. The
WARNING: SRC_URI specified branch standard/gt. The branch will be forced to standard/gt,
WARNING: but this means the board meta data (.scc files) do not match the SRC_URI specification.
WARNING: The meta data and branch standard/gt should be inspected to ensure the proper
WARNING: kernel is being built.
Reported-by: Steve Sakoman" <steve.sakoman@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Sat, 2 Apr 2016 00:09:25 +0000 (20:09 -0400)]
linux-yocto/4.4: UVC: Add support for R200 depth camera
Integrating the following commit:
[
Add support for Intel R200 depth camera in uvc driver.
This includes adding new uvc GUIDs for the new pixel formats,
adding new V4L pixel format definition to user api headers,
and updating the uvc driver GUID-to-4cc tables with the new formats.
Bruce Ashfield [Sat, 2 Apr 2016 00:09:24 +0000 (20:09 -0400)]
linux-yocto/4.4: fix PAT for 32bit x86
Integrating the following mainline destined commits to fix PAT issues with
32bit x86 and qemu:
bc22b90fb583 x86/pat: Document the PAT initialization sequence c534b1ec1991 x86/xen, pat: Remove PAT table init code from Xen cd47692e804f x86/mtrr: Fix PAT init handling when MTRR is disabled 039434bdc165 x86/mtrr: Fix Xorg crashes in Qemu sessions c08196e8064c x86/mm/pat: Replace cpu_has_pat with boot_cpu_has() 6928fce8c766 x86/mm/pat: Add pat_disable() interface 3163c8d5468d x86/mm/pat: Add support of non-default PAT MSR setting
With this change applied, we once again have working graphics and no special
work arounds.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Sat, 2 Apr 2016 00:09:21 +0000 (20:09 -0400)]
linux-yocto/4.1: ahci: backport AHCI runtime PM
enabling AHCI runtime PM support via the following commits:
f5b08e95bc03 ahci: Add runtime PM support for the host controller e05e05973f39 ahci: Add functions to manage runtime PM of AHCI ports 558571930e2d ahci: Convert driver to use modern PM hooks 4a2c2074f209 ahci: Cache host controller version 21641413456c scsi: Drop runtime PM usage count after host is added 254ab69f652d scsi: Set request queue runtime PM status back to active on resume 61c02cb167ed block: Add blk_set_runtime_active() 7bcfbac98f3c ahci: Store irq number in struct ahci_host_priv a5a093b7f6e4 ahci: Move interrupt enablement code to a separate function
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Sat, 2 Apr 2016 00:09:20 +0000 (20:09 -0400)]
linux-yocto/4.4: gpio-pca953x: add PCAL9535 interrupt support
Reverting two previous gpio commits to allow the application of proper
upstream ready patches to add this support:
08943f2bbd50 gpio-pca953x: add "drive" property a517d5b72e76 gpio: pca953x: provide GPIO base based on _UID c91063f44368 gpio-pca953x: add PCAL9535 interrupt support 58f3c9f0ac6d Revert "gpio-pca953x: add "drive" property" 7abbd5fec15d Revert "gpio: pca953x: provide GPIO base based on _UID"
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wic/isoimage-isohybrid.py: change cpio generated uid&gid to root
By default cpio preserves the uid&guid's of the original user which
leads to host contamination and boot failures because commands like
mount from initramfs expect to be run by root and the original host
user might not even exist on the target.
Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wic/isoimage-isohybrid.py: use glob to find initramfs location
Some filenames can omit 'initramfs', or use other names. This makes
detection more flexible by using only the image name, machine arch and
image type in a glob wildcard.
Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bill Randle [Fri, 1 Apr 2016 16:49:12 +0000 (09:49 -0700)]
insane.bbclass: avoid false positives on library location
package_qa_check_libdir() reports that the file libsoletta.so.0.0.1-gdb.py
in /usr/share/gdb/auto-load is in the wrong location. Before generating
a warning for files in non-standard locations, check that the file is an
actual elf file (and hence a real library file).
[YOCTO #9215]
Signed-off-by: Bill Randle <william.c.randle@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert Yang [Fri, 1 Apr 2016 07:32:55 +0000 (00:32 -0700)]
grub-efi.bbclass: use GRUB_ROOT rather than APPEND for root device
Use APPEND for grub's root device may cause confusion, for example, when
building efi + pcbios, there maybe be two root=/dev/ram0, one of them
would be carried to the installed target, and the target would fail to
boot. Use GRUB_ROOT to fix the problem, and remove SYSLINUX_ROOT from
APPEND will fix the problem.
[YOCTO #9354]
Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Sat, 2 Apr 2016 16:11:56 +0000 (17:11 +0100)]
bitbake.conf: Add BB_WORKERCONTEXT to HASHBASE_WHITELIST
We never want checksum to vary depending on whether we calculate them
in server or worker context, that would make no sense. This was happening
in do_rootfs tasks since they reference the BB_WORKERCONTEXT variable.
Whitelist the variable to avoid this class of problem.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Fri, 1 Apr 2016 17:02:07 +0000 (18:02 +0100)]
base: Fixup PACKAGECONFIG incorrect mappings
PACKAGECONFIG doesn't work in cross-canadian recipes at the moment as
DEPENDS are prepended with mlprefix.
A recipe is either nativesdk, native or target so adjust the if
statements accordingly, use inherits_class for more accurate recipe
classification and add cross-canadian support.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Andre McCurdy [Fri, 1 Apr 2016 05:00:59 +0000 (22:00 -0700)]
default-distrovars.inc: remove libassuan from LGPLv2_WHITELIST_GPL-3.0
The libassuan recipe is now buildable in distros which blacklist
GPL-3.0 without needing to be explicitly whitelisted (since it
provides at least one non GPLv3 package).
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Andre McCurdy [Fri, 1 Apr 2016 05:00:58 +0000 (22:00 -0700)]
libassuan: use package specific licensing
- The main libassuan.so library is LGPLv2.1+
- Test apps (in tests sub directory) and documentation are GPLv3+
- Windows CE specific binaries (gpgcedev.dll and gpgcemgr) are GPLv3+
When building the current OE recipe, the test apps are compiled but
not installed. The Windows CE specific binaries are not compiled.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Thu, 31 Mar 2016 22:54:34 +0000 (23:54 +0100)]
selftest/signing: Use packagedata to obtain PR value for signing test
Using PF to calculate the rpm filename doesn't work when PR server is
enabled and an extra PR value can be injected. Add code to use packagedata
to obtain the full name, allowing the test to work when PR server is
in use.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Andre McCurdy [Thu, 31 Mar 2016 18:13:06 +0000 (11:13 -0700)]
base.bbclass: drop obsolete HOSTTOOLS_WHITELIST_GPL-3.0
base.bbclass sets 'check_license' to False (and therefore skips
license checking completely) for native, nativesdk, etc recipes
(ie anything which could potentially be classed as "host tools"),
so supporting a dedicated whitelist of GPLv3 host tools is not
necessary.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bill Randle [Thu, 31 Mar 2016 05:11:35 +0000 (22:11 -0700)]
man: use BUILD_CC and target include files for configure
The configure script was using the cross-compiler for feature tests,
which fails to execute when the target is different than the host.
Change the script to use the build compiler instead, but use the
target include files to check for the target features.
[YOCTO #9359]
Signed-off-by: Bill Randle <william.c.randle@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bill Randle [Wed, 30 Mar 2016 23:50:49 +0000 (16:50 -0700)]
man: fix several annoying compile/build warnings
Fixed the build error when building man.config.5 (a remnant of a long
ago previous patch). Optimized the manpages Makefile for parallel
builds. Drop a FHS patch that is no longer needed, as the standard
Makefile puts the man pages in the proper location. Also, fix compile
warnings in a couple other files.
[YOCTO #9341]
Signed-off-by: Bill Randle <william.c.randle@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
image.bbclass: Make unneeded packages for a read-only rootfs configurable
Previously the list of packages that are considered unneeded for a
read-only rootfs was hardcoded. This made it impossible to, e.g., have
shadow installed on a system with a read-only rootfs, but where /etc
is mounted writable.
This also lists ${VIRTUAL-RUNTIME_update-alternatives} rather than
update-alternatives (as was previously the case) since this should
actually remove the intended package.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Juro Bystricky [Thu, 31 Mar 2016 00:13:54 +0000 (17:13 -0700)]
relocate_sdk: additional error checks
When installing SDK in a non-default location and the path length
of the SDK install location is longer than the path length of the
default SDK location, relocation of .ldsochache section will overwrite
file location outside of the .ldsocache section size.
In addition, additional checks were added to ensure that any
path in sections .gccrelocprefix and .ldsochache will not exceed
the space allocated for it within the file, which would also result
in file corruption.
[YOCTO #9268]
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Thu, 31 Mar 2016 08:53:35 +0000 (21:53 +1300)]
devtool: modify: call shutdown on tinfoil when done
Strictly speaking we ought to explicitly shut down a tinfoil instance
when we're done with it. This doesn't affect modify's operation but is
important if you want to be able to call into modify() from another
plugin (though anyone doing so should be advised that the function is
by no means a stable API and is subject to change in future releases).
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Thu, 31 Mar 2016 08:53:34 +0000 (21:53 +1300)]
toolchain-shar-extract.sh: ensure all_proxy is allowed through
all_proxy is referred to by oe-git-proxy so ensure it is allowed through
into the installer environment in case the extensible SDK install
process needs to query a remote git repository.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Thu, 31 Mar 2016 08:53:33 +0000 (21:53 +1300)]
oe-publish-sdk: exclude sstate-cache if publishing minimal SDK
If SDK_EXT_TYPE is set to "minimal" then the SDK won't contain many
sstate artifacts, and you're required to set up an sstate mirror in this
case anyway so there's no point publishing the "stub" sstate-cache
directory from within the SDK since it won't be useful for update
purposes and may be confused with the real sstate-cache.
There is however a possibility that people might publish the real
sstate-cache directory under the same output directory provided to
oe-publish-sdk, thus deleting it after extracting (as we were doing with
other files we wanted to clean up at the end) would be problematic,
besides which extracting it and then deleting it is wasteful. Thus,
introduce a "-p" command line option to the SDK installer that we can
use to tell tar not to extract the items we don't want when publishing.
This has the added benefit of mostly keeping references to these in the
place they belong i.e. in populate_sdk_ext.bbclass.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Thu, 31 Mar 2016 08:53:31 +0000 (21:53 +1300)]
classes/populate_sdk_ext: support setting vars from environment at build time
When running bitbake you may pass in values of variables from the
external environment (making use of BB_ENV_EXTRAWHITE), and you may
choose to do this when building the extensible SDK, for example:
You would naturally expect those settings to be reflected in the
extensible SDK itself; however they were not, since we were only
considering local.conf and auto.conf. Check the variables mentioned in
BB_ENV_EXTRAWHITE to see if any are different than the values set in
local.conf/auto.conf and add lines setting them in the SDK's local.conf
if so.
Fixes [YOCTO #9339].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Thu, 31 Mar 2016 11:46:38 +0000 (12:46 +0100)]
scripts, lib: Don't limit traceback lengths to arbitrary values
There appears to have been a lot of copy and pasting of the code
which prints tracebacks upon failure and limits the stack trace to
5 entries. This obscures the real error and is very confusing to the user
it look me an age to work out why some tracebacks weren't useful.
This patch removes the limit, making tracebacks much more useful for
debugging.
[YOCTO #9230]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
/home/ricardo/curro/qt5022/oe/openembedded-core/build/tmp-glibc/sysroots
/qemux86-64/usr/lib/python2.7/site-packages/numpy/core/include/numpy/
npy_common.h:140:9: warning: "NPY_SIZEOF_OFF_T" is not defined [-Wundef]
#if NPY_SIZEOF_OFF_T == NPY_SIZEOF_SHORT
^
/home/ricardo/curro/qt5022/oe/openembedded-core/build/tmp-glibc/sysroots/
qemux86-64/usr/lib/python2.7/site-packages/numpy/core/include/numpy
/npy_common.h:142:11: warning: "NPY_SIZEOF_OFF_T" is not defined [-Wundef]
#elif NPY_SIZEOF_OFF_T == NPY_SIZEOF_INT
^
/home/ricardo/curro/qt5022/oe/openembedded-core/build/tmp-glibc/sysroots/
qemux86-64/usr/lib/python2.7/site-packages/numpy/core/include/numpy/
npy_common.h:144:11: warning: "NPY_SIZEOF_OFF_T" is not defined [-Wundef]
#elif NPY_SIZEOF_OFF_T == NPY_SIZEOF_LONG
^
/home/ricardo/curro/qt5022/oe/openembedded-core/build/tmp-glibc/sysroots/
qemux86-64/usr/lib/python2.7/site-packages/numpy/core/include/numpy/
npy_common.h:146:11: warning: "NPY_SIZEOF_OFF_T" is not defined [-Wundef]
#elif NPY_SIZEOF_OFF_T == NPY_SIZEOF_LONGLONG
^
/home/ricardo/curro/qt5022/oe/openembedded-core/build/tmp-glibc/sysroots/
qemux86-64/usr/lib/python2.7/site-packages/numpy/core/include/numpy/
npy_common.h:149:10: error: #error Unsupported size for type off_t
#error Unsupported size for type off_t
Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert Yang [Thu, 31 Mar 2016 10:47:02 +0000 (03:47 -0700)]
image-live.bbclass: DEPENDS on syslinux
The mkisofs requires syslinux/isolinux.bin which is provided by
target syslinux, for pcbios, the depends is already there, but for
EFI, it isn't, so add the depends.
Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Clemens Lang [Wed, 30 Mar 2016 13:22:49 +0000 (15:22 +0200)]
ldconfig-native: Fix ELF flags on 64-bit binaries
Yocto's ldconfig-native was exported from an old version of glibc and
generates an ld.so.cache that is partially ignored by current versions
of glibc when loading libraries. This occurs for 64-bit binaries, where
glibc expects FLAG_ELF_LIBC6, but ldconfig-native only generates the
standard ELF flag. Fix this with an additional patch on top of the patch
for now.
You can verify this by applying the patch below to your target copy of
glibc and running
Aníbal Limón [Wed, 30 Mar 2016 20:21:42 +0000 (14:21 -0600)]
recipes-support/rng-tools: Change runlevel start from S to 2, 3, 4, 5.
When using systemd as init rng-tools is causing a circular dependency
between units,
[ 7.706250] systemd[1]: basic.target: Found ordering cycle on
basic.target/start
[ 7.706934] systemd[1]: basic.target: Found dependency on
sysinit.target/start
[ 7.707795] systemd[1]: basic.target: Found dependency on
rng-tools.service/start
[ 7.708692] systemd[1]: basic.target: Found dependency on
basic.target/start
[ 7.709461] systemd[1]: basic.target: Breaking ordering cycle by
deleting job rng-tools.service/start
[ 7.710404] systemd[1]: rng-tools.service: Job rng-tools.service/start
deleted to break ordering cycle starting with basic.target/start
The problem is related to systemd running sysvinit scripts by default
add dependency of basic.target for sysvinit script so when sysvscript
is at rcS is added also as dependency of sysinit.target causing a
cirular dependency in this case: basic.target -> sysinit.target ->
rng-tools.service -> basic.target.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Aníbal Limón [Wed, 30 Mar 2016 20:21:41 +0000 (14:21 -0600)]
oeqa/runtime/parselogs.py: Add systemd unit circular dependencies errors.
When systemd is enabled as init we need to notice when circular
dependencies in units happen because systemd try to solve this situation
removing the unit itself.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Awais Belal [Wed, 30 Mar 2016 09:35:15 +0000 (14:35 +0500)]
systemd-serialgetty: allow baud rate overriding
In case a getty is required on a UART which is not being
used as the kernel console, the current agetty invocation
fails to obey the baud rate configured through the
SERIAL_CONSOLES variable because it uses --keep-baud.
Signed-off-by: Awais Belal <awais_belal@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Wed, 30 Mar 2016 12:25:06 +0000 (08:25 -0400)]
linux-yocto/4.4: broxton and usb type-c backports
c43425f73287 mfd: lpss: Add PCI IDs for Intel Broxton B-Step platform 2d6cc1d3e71f spi: pxa2xx: Add support for Intel Broxton B-Step 1df3674b7626 usb: dwc3: gadget: don't send extra ZLP 222ab0043e48 usb: dwc3: gadget: handle request->zero 3f01b2c0295a usb: dwc3: gadget: simplify dwc3_gadget_ep_queue() 729b5a1f8f65 usb: dwc3: gadget: set the OTG flag in dwc3 gadget driver. 65740f5d1a0d usb: dwc3: gadget: simplify next_request() return check a82442f90ea7 usb: dwc3: Fix assignment of EP transfer resources d99293bbaa50 usb: dwc3: ep0: fix setup_packet_pending initialization
Signed-off-by: Matt Ranostay <matt.ranostay@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Wed, 30 Mar 2016 12:25:04 +0000 (08:25 -0400)]
linux-yocto/4.1: Intel Broxton: pwm backports
Integrating the following mainline changes:
afaf425e796c pwm: Add the pwm_is_enabled() helper 023721c3d067 pwm: atmel: Fix incorrect CDTY value after disabling cd9fe8adb313 pwm: atmel: Fix incorrect CDTY value after enabling 3f445ca6df1f pwm: lpss: Rework the sequence of programming PWM_SW_UPDATE 9a51f622bdc9 pwm: lpss: Select core part automatically 8ee11b6f80ba pwm: lpss: Update PWM setting for Broxton 148228a52c2d pwm: lpss: Remove ->free() callback e20d95bcd0b3 pwm: lpss: Add support for runtime PM b2248acf6f8b pwm: lpss: Add more Intel Broxton IDs 85e8566bd241 pwm: lpss: Support all four PWMs on Intel Broxton 1bcdcb6275bf pwm: lpss: Add support for multiple PWMs
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Wed, 30 Mar 2016 12:25:03 +0000 (08:25 -0400)]
linux-yocto/4.1: Apollo Lake/Broxton mmc backports
Backporting the following commits:
2b0cc0f0ca23 mmc: It is not an error for the card to be removed while suspended 67903c1f4c77 mmc: sdhci: 64-bit DMA actually has 4-byte alignment 4e434f483381 mmc: sdhci: Do not BUG on invalid vdd 05be442eb234 mmc: mmc: Fix incorrect use of driver strength switching HS200 and HS400 97a5f396dca6 mmc: core: Make runtime resume default behavior for MMC/SD b6ee1ac07f14 mmc: mmc: Improve reliability of mmc_select_hs400() 45de48ce0b3c mmc: mmc: Move mmc_switch_status() 9d6aaaa0f6b7 mmc: mmc: Fix HS setting in mmc_select_hs400() d7795de930c5 mmc: mmc: Improve reliability of mmc_select_hs200() ac98e33a088d mmc: sdhci-acpi: Add more ACPI HIDs for Intel controllers 87f52cce8123 mmc: sdhci-pci: Add more PCI IDs for Intel controllers cf3a4d2d4c7d mmc: sdhci-pci: Add another PCI ID for an Intel eMMC host controller b3ef45585504 mmc: sdhci-pci: Build o2micro support in the same module b32a4e71f49d mmc: sdhci: enable tuning for DDR50 f8e213bee1e1 mmc: sdhci: call sdhci_init() before request irq ece0925eb94e mmc: sdhci-pci: Enable HS400 for some Intel host controllers 1c01bcdceaf6 mmc: sdhci-pci: Add support for drive strength selection for SPT c1d6e92915a9 mmc: sdhci: Add a callback to select drive strength 40deb3ac3331 mmc: mmc: Add driver strength selection e7d602f5992f mmc: mmc: Read card's valid driver strength mask bc193a886571 mmc: core: Record card drive strength a548d3993cc8 mmc: core: Factor out common code in drive strength selection 6713f5cf3164 mmc: core: Add 'card' to drive strength selection callback 852e6bd69b77 mmc: core: Simplify card drive strength mask 0bb40266bbb9 mmc: core: Allow card drive strength to be different to host 940d30f1a212 mmc: core: Reset driver type to default efbc6ba8cd27 mmc: cast u8 to unsigned long long to avoid unexpected error bafe0e5beba9 mmc: core: Don't print reset warning if reset is not supported 5b2789151852 mmc: block: Retry errored data requests when re-tuning is needed d14211a4b2fe mmc: block: Check re-tuning in the recovery path 1ff15c648159 mmc: core: Flag re-tuning is needed on CRC errors 12544ee1cdbb mmc: sdhci: Change to new way of doing re-tuning 995073b182f7 mmc: core: Add support for HS400 re-tuning 53a0d731e824 mmc: core: Separate out the mmc_switch status check so it can be re-used d3f59f108bf7 mmc: mmc: Hold re-tuning in mmc_sleep() 465db9504a27 mmc: core: Hold re-tuning while bkops ongoing 60cacf85ee10 mmc: core: Hold re-tuning during erase commands 5bd43535f4c1 mmc: core: Hold re-tuning during switch commands 4baa45ff8d15 mmc: core: Add support for re-tuning before each request cd2ca27f9282 mmc: core: Enable / disable re-tuning 65723236b746 mmc: host: Add facility to support re-tuning
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Wed, 30 Mar 2016 12:25:01 +0000 (08:25 -0400)]
linux-yocto/4.1: device property backports
Integrating the following 4.4 backports:
630b726098c9 mfd: make mfd_remove_devices() iterate in reverse order aab24907568b driver core: Do not overwrite secondary fwnode with NULL if it is set 89775462ef50 device property: return -EINVAL when property isn't found in ACPI a9eebae4a2c0 device property: check fwnode type in to_of_node()
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Wed, 30 Mar 2016 12:25:00 +0000 (08:25 -0400)]
linux-yocto/qemuarm64: enable 32 bit compatibility
It was requested that CONFIG_COMPAT be enabled for qemuarm64 so that
32bit applications could be tested. This is simple enough to do, so
there is now a 32bit compat feature, and it is included only in
qemuarm64 to avoid impacting any other ARM targets (but the feature
is available for others to use).
[YOCTO #8646]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Andre McCurdy [Wed, 30 Mar 2016 20:08:30 +0000 (13:08 -0700)]
default-distrovars.inc: remove gnutls + libtasn1 from LGPLv2_WHITELIST_GPL-3.0
With the modern license handling code, gnutls and libtasn1 are both
buildable in distros which blacklist GPL-3.0 without needing to be
explicitly whitelisted (since they both provide at least one non
GPLv3 package).
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Wed, 30 Mar 2016 19:55:42 +0000 (20:55 +0100)]
sanity.bbclass: Use pythonexception to raise real exceptions without backtraces
If the sanity code encounters a version change is doesn't understand, the current
output is unreadable and confusing for the user, particularly due to the presence
of the backtrace.
Use improved functionality in bitbake to improve this and correctly pass python
exceptions around.
[YOCTO #9291]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bill Randle [Tue, 29 Mar 2016 22:26:39 +0000 (15:26 -0700)]
man: fix src/Makefile to work with parallel make
The Makefile for man has a rule to create two generated targets with
a program run from the shell. Because the rule was run twice, with
parallel make, the generated files were being overwritten at the same
time they were being compiled. This patch forces the rule to be run
only once.
[YOCTO #9333]
Signed-off-by: Bill Randle <william.c.randle@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Khem Raj [Mon, 28 Mar 2016 04:00:16 +0000 (04:00 +0000)]
gcc: Backport fixes for musl ssp configuration
We were trying to inject cached configure variables via
EXTRA_OECONF, but that was not working due to the fact
that gcc configure is called recursively via makefiles
and hence these were getting lost.
These backports from master fixes the problem by
defining the options in configure itself
dl_iterate_phdr is provided by musl as well, so lets
not depend on glibc defines like inhibit_libc alone
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Khem Raj [Mon, 28 Mar 2016 04:00:14 +0000 (04:00 +0000)]
musl: Update to tip
Rich Felker (2):
fix padding string formats to width in wide printf variants
fix outdated pathnames in COPYRIGHT file
Szabolcs Nagy (7):
deduplicate bits/mman.h
mips64: add recent linux syscall numbers
add copy_file_range syscall numbers from linux v4.5
add IPV6_HDRINCL socket option from linux v4.5
add SO_ATTACH_REUSEPORT_[CE]BPF socket options from linux v4.5
add EPOLLEXCLUSIVE epoll flag from linux v4.5
add MADV_FREE madvise command from linux v4.5
Timo Teräs (1):
fix gethostbyaddr_r to fill struct hostent.h_length as appropriate
Patrick Ohly [Mon, 28 Mar 2016 13:27:57 +0000 (15:27 +0200)]
buildhistory.bbclass: create image directory when needed
buildhistory_get_imageinfo() assumed that the buildhistory directory
for the image had already been created earlier. That assumption is not
true for special images (like the virtual swupd images from
meta-swupd) where the entire traditional do_rootfs/do_image is
skipped.
Creating files-in-image.txt still makes sense for such images, so
support them by creating the directory also in
buildhistory_get_imageinfo().
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert Yang [Tue, 29 Mar 2016 07:49:52 +0000 (00:49 -0700)]
init-live.sh: fix overlay fs
* The name changes from overlayfs to overlayo
* The workdir is a must when mount
* The updir must be a subdir of rootfs.rw
This patch plus with another one which has been sent to linux-yocto can
fix the error when boot iso:
EXT4-fs (loop0): re-mounted. Opts: data=ordered
Populating dev cache
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/rcS.d/S36udev-cache: line 73: can't create /etc/udev-cache.tar.gz:
Read-only file system
udev-cache: update failed!
rm: can't remove '/etc/udev/cache.data': Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
rm: can't remove '/tmp': Read-only file system
ln: /tmp/tmp: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
ln: /etc/resolv.conf: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
/etc/init.d/rc: /etc/rcS.d/S37populate-volatile.sh: line 1: can't create
/etc/volatile.cache.build: Read-only file system
Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
While in there, added a few non-functional changes:
Added sample proxy settings into .bashrc
Added environmental variable with SRCREV actually used to populate the Build
Appliance into .bashrc (BA_SRCREV)
[YOCTO#9314]
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Hongxu Jia [Mon, 21 Mar 2016 08:46:20 +0000 (04:46 -0400)]
conf/bitbake.conf package.bbclass: fix dbg package not contain sources while -fdebug-prefix-map used
Tweak DEBUG_FLAGS to use "/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR}"
as source target path in DWARF. While use gdb to debug binary, it could
work with sources in dbg package.
While -fdebug-prefix-map is used for compiling, we do not need invoking
debugedit to edit DWARF at do_package time, but list where sources files
are.
The copydebugsources uses the list to copy sources to dbg package. It
works whether -fdebug-prefix-map used or not.
[YOCTO #9305]
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Markus Lehtonen [Tue, 22 Mar 2016 16:01:10 +0000 (18:01 +0200)]
externalsrc: remove nostamp from do_configure
Extend the srctree_hash_files() function in externalsrc.bbclass to
handle non-Git source trees. If the source tree is not a git
repository, srctree_hash_files() now simply adds the whole source tree
as a dependency, causing bitbake to basically hash every file in it.
Hidden files and directories in the source tree root are ignored by the
glob currently used. This has the advantage of automatically ignoring
.git directory, for example.
During the first bitbake run preparing of the task runqueue may take
much longer if the source tree is not a git repository. The reason is
that all the files in the source tree are hashed. Subsequent builds are
not significantly slower because (most) file hashes are found from the
cache.
[YOCTO #8853]
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Markus Lehtonen [Tue, 22 Mar 2016 16:01:09 +0000 (18:01 +0200)]
externalsrc: do not use do_configure[nostamp] for git srctrees
Be a bit more intelligent than mindlessly re-compiling every time.
Instead of always using 'nostamp' flag for do_compile run a python
function to get a list of files to add as 'file-checksums' flag. The
intention is to only re-run do_compile if something in the source tree
content changes.
This python function, srctree_hash_files(), works differently, depending
if the source tree is a git repository clone or not. If the source tree
is a git repository, the function runs 'git add .' and 'git write tree'
to get a hash of the working tree and writes this hash into a file under
the .git directory. This file containing the hash is then returned as
the file for the task to depend on. Hash is changed if any changes are
made in the source tree causing the task to be re-run. A trick is used
to parse the recipe every time so that the hash file gets updated.
If the source tree is not a git repository behaviour remains the same.
In this case srctree_hash_files() currently sets the 'nostamp' flag for
do_compile causing it to be re-run every time.
This method of tracking changes source tree changes to determine if
re-build is needed does not work perofectly, though. Many packages are
built under ${S} which effectively changes the source tree causing some
unwanted re-compilations. However, if do_compile of the recipe does not
produce new/different artefacts on every run (as commonly is and should
be the case) the re-compilation loop stops. Thus, you should usually see
only one re-compilation (if any) after which the source tree is
"stabilized" and no more re-compilations happen.
[YOCTO #8853]
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Humberto Ibarra [Thu, 24 Mar 2016 00:32:02 +0000 (18:32 -0600)]
scripts:/oe-selftest: Use timestamp instead of test names in coverage data file
This fixes the problem by changing the name to the coverage data file,
using the timestamp as an identifier.
The name for the coverage data file is constructed based on the tests
ran; this has created a couple of issues so far, affecting coverage report.
If --run-tests-by option is given, the data file name won't have any
identifier, causing following runs to overwrite themselves. On the
other hand, if too many tests are given, the file name exceeds linux
limits and fails to store the coverage data all together.
[Yocto #9253]
Signed-off-by: Humberto Ibarra <humberto.ibarra.lopez@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Johannes Pointner <johannes.pointner@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
