Richard Purdie [Sat, 6 Jan 2018 10:02:10 +0000 (10:02 +0000)]
local.conf.sample: Weakly set BB_DISKMON_DIRS
For various reasons we need to be able to set and override this from
auto.conf on our test infrastructure. We have tried forcing the variable
but this then breaks other selftests. In the interests of not complicating
things further and needing to modify the tests across releases, weaken
the default assignment.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Joshua Lock [Thu, 9 Nov 2017 14:59:06 +0000 (14:59 +0000)]
beaglebone-yocto: rename beaglebone machine to beaglebone-yocto
The beaglebone BSP provided in this layer is a reference implementation
usingonly mainline components available in core Yocto Project layers,
whereas Texas Instruments maintain a full-featured BSP in the meta-ti
layer.
Rename the reference machine to prevent namespace collisions with the
version maintained by the SoC vendor.
[YOCTO #12326]
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Joshua Lock [Fri, 3 Nov 2017 13:45:25 +0000 (13:45 +0000)]
poky: remove old Fedora releases from SANITY_TESTED_DISTROS
* Fedora 24 reached end-of-life on 2017-08-08 and hasn't been tested in
some time.
* Fedora 25 reaches end-of-life in Q4 2017 and is exhibiting a bug which
makes it an extremely unreliable host OS for workers on the Yocto
Autobuilder. For that reason we'll no longer be using this distro on the
Yocto Autobuilder and thus cannot claim the distro is sanity tested.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drew Moseley [Tue, 10 Oct 2017 01:59:08 +0000 (21:59 -0400)]
beaglebone: Find /boot partition on mmcblk0
After commit edcf39820f94c84b29c95a0d7b16b8d36857e87b the beaglebone
builds fail to mount the boot partition as it is specified in
/etc/fstab with the device node /dev/mmcblkp1. With systemd in
particular this is considered an error and the system drops into
emergency mode.
Signed-off-by: Drew Moseley <drew.moseley@northern.tech> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Martin Kelly [Fri, 6 Oct 2017 17:42:12 +0000 (10:42 -0700)]
poky: add debian-9 to SANITY_TESTED_DISTROS
I have been working with OE on debian-9 for several months now without
issue. In addition, I tested a build + runqemu for core-image-sato
following the quickstart guide and had no issues.
Signed-off-by: Martin Kelly <mkelly@xevo.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Slater, Joseph [Thu, 3 Aug 2017 17:59:58 +0000 (17:59 +0000)]
packagegroups: remove a bbappend
Force items into packagegroup-core-tools-profile? I don't think so.
Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Thu, 14 Sep 2017 11:00:35 +0000 (12:00 +0100)]
meta-yocto: Restructure and tidy up READMEs
The YP Compat v2 standard requres a more specific README structure. Bring
meta-yocto to the required standard and clean up some of the data in the
READMEs whilst in there.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Jussi Kukkonen [Tue, 18 Jul 2017 07:30:33 +0000 (10:30 +0300)]
poky.conf: Enable vulkan by default
Things to note:
* This ends up enabling dri3 in mesa
* It does not completely enable dri3 in xorg with xf86-video-intel
because that requires a run time configuration (xorg.conf)
So vulkan in poky with xf86-video-intel still requires a xorg.conf
snippet to enable dri3. Otherwise (weston or X with other drivers)
it just works.
Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bsp/help: include a warning showing deprecation of create-layer plugin
This plugin will be removed starting 2.5 development in favour
of using 'bitbake-layers create-layer' script/plugin, offering a single
script to manage layers.
Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
tested the quickstart guide on Fedora 26 and confirmed that it
can build a core-image-sato and run the image via runqemu.
Signed-off-by: Benjamin Esquivel <code@esquibits.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
brian avery [Fri, 21 Jul 2017 19:39:53 +0000 (12:39 -0700)]
poky: Remove machine specific kernel overrides
This patch removes the machine specific overrides in poky.conf for all
the qemu machines. With this patch, if you set
PREFERRED_VERSION_linux-yocto="X%" then all the qemu machines as well as
the sample hardware boards will use that version. Without this patch,
the hardware boards would have used version X but the qemu machines
would have needed to have a PREFERRED_VERSION_linux-yocto_qemuarm="X%"
for qemuarm to use that version, for example. If we need to force a
specific machine (hardware or qemu) to a particular default version we
should add it to the machine conf files for that machine, not in the
distro conf.
Signed-off-by: brian avery <brian.avery@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
brian avery [Fri, 21 Jul 2017 19:39:52 +0000 (12:39 -0700)]
meta-yocto-bsp: Remove superfluous kernel set
The genericx86 and genericx86-64 machine confs do not need to set the
PREFERRED_PROVIDER_virtual/kernel as they will use the one set by the
distribution. If there needed to be a different version for one of these
machines in the future, we could add it in to the machine.conf.
Signed-off-by: brian avery <brian.avery@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
poky: add Ubuntu 17.04 Zesty Zapus to SANITY_TESTED_DISTROS
The new Ubuntu releases on 2017-04-13, after cutoff for Yocto Project 2.3.
I've been running builds of some images and a world build in a container
over the past couple of days without issue. I've also run a complete
oe-selftest run (with SANITY_TESTED_DISTROS = "") and did not observe any
errors.
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ming Liu [Tue, 4 Jul 2017 08:32:21 +0000 (10:32 +0200)]
local.conf.sample: drop image-swab reference
The image swabber had been dropped by commit e18657df:
[ meta: Drop swabber ]
We need also drop its reference in local.conf.
Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oeqa/selftest/systemdboot: Add Test to check boot file is created correctly
Add Test case to verify if EFI bootloader for
systemd boot is correctly build inside of image.
[YOCTO #9903]
Signed-off-by: Jose Perez Carranza <jose.perez.carranza@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto: remove user-specific description/config files from machine description
Remove user-specific descrition files and config fragments from main machine
description file otherwise double patch/config inclusion may happen. These
files/fragments are already included on the SRC_URI (see poky commit 2db8f3),
so no need to reference these inside machine.scc files.
[YOCTO #11586]
Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ed Bartosh [Wed, 7 Jun 2017 12:22:46 +0000 (15:22 +0300)]
README.hardware: update flashing instructions for MPC8315
Using 1000000 memory address for kernel and a00000 for dtb
can cause kernel image to overwrite dtb when uncompressing
and u-boot crashing with:
ERROR: image is not a fdt - must RESET the board to recover.
Updated flashing instructions for the board to use addresses 1000000 and 2000000 to avoid this error.
Got rid of resetting loadaddr and ftdaddr u-boot variables.
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
scripts/lib: removes bsp 4.8 kernel bbappends as the version is no longer supported
These files should be removed as version 4.8 is no longer supported (6751dce4cf
and 1632f6623c) and errors may be produced when executing some commands.
For instance, "yocto-bsp list <karch> --property <property_name>" expects the
SRC_URI of the 4.8 kernel recipe, which doesn't exist anymore, throwing the
following exception:
$ yocto-bsp list arm --property existing_kbranch
Getting branches from remote repo None...
Traceback (most recent call last):
...
SyntaxError: function specified for 'gen' property returned nothing : input type:
"choicelist" name:"existing_kbranch" nameappend:"i386" gen:"bsp.kernel.all_branches"
branches_base:"standard" prio:"20" msg:"Please choose a machine branch to base this
BSP on:" default:"standard/base"
[YOCTO #9867]
Signed-off-by: Daniela Plascencia <daniela.plascencia@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Kevin Hao [Sat, 8 Apr 2017 13:45:59 +0000 (21:45 +0800)]
meta-yocto-bsp: workaround the X malfunction on beaglebone
After the change in kernel commit a291b6b3d287 ("ARM: dts:
am335x-boneblack: Add blue-and-red-wiring -property to LCDC node"),
the pixel format we support for 32bit bpp has been changed from
XRGB8888 to XBGR8888. But the fbdev created by modesetting driver use
the XRGB8888 format by default, this causes the X malfunction. There is
no easy way to adjust the pixel format of the fbdev created by the
modesetting driver. So we create a xorg.conf to use the 16bit bpp to
work around this issue.
[YOCTO #11267]
Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Thu, 6 Apr 2017 02:17:20 +0000 (14:17 +1200)]
poky-world-exclude.inc: add python-pyqt
python-pyqt in meta-qt4 is about to require sip 4.19 that only meta-oe
provides; as we only bring in meta-qt4 for LSB, there's no need to be
building this as part of world and it would fail without meta-oe anyway.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since we do not set the 64 bit flags, newer kernels seem to build 64bit
config files by default. This is due to a hard-coded uname -m check that
selects the KBUILD_DEFCONFIG based on the host, not the cross target.
projects / thirdparty / openembedded / openembedded-core-contrib.git / log
