Kernel support is now in linux-yocto-dev and will be moved to a versioned
recipe once 3.14 is released.
(From meta-yocto rev: ba78fa236b4993efd4c2502413e92fa659c2f28b)
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adding the summary, preparation and boot information for the newly introduced
edgerouter BSP.
(From meta-yocto rev: cc8c7a3c94d2cafe899adc7f8199237d4a72f205)
Signed-off-by: Yang Wei <Wei.Yang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Switch the edgerouter from linux-yocto-dev, to the 3.14 linux-yocto
BSP.
(From meta-yocto rev: a1d02927130842c45201c1af46180e8231dcea1c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The EdgeRouter Lite is part of the EdgeMax series. It is an MIPS64 router(Cavium Octeon)
with 512MB of RAM, which uses a USB pendrive for storage.
Setup instructions
------------------
You will need the following:
* NFS root setup on your workstation
* TFTP server installed on your workstation
* Straight-thru 9-conductor serial cable (DB9, M/F) connected from your
PC to UART1
* Ethernet connected to the first ethernet port on the board
The rest of the details can be found in the BSP kernel config, and README.hardware.
(From meta-yocto rev: 473067887b9e04366c370ab123bcd14eff33fd9a)
Signed-off-by: Yang Wei <Wei.Yang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 3.14 kernel supports the generic-x86, edgerouter and beaglebone black.
All other reference BSPs stay in the 3.10 kernel until boot and regression
testing can be performed.
(From meta-yocto rev: 2a5918b141a41ebf4f8b47c35249319cb9478d48)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3.14 is now the reference for libc-headers. After building and booting 3.x based
BSPs against the 3.14 headers, we can safely remove the old version and patches
that are now part of the mainline kernel.
(From OE-Core rev: ade26bc63fdf89f297bec5f67bfff108e90438fc)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Introduce the 3.14 linux-libc-headers recipe, now that the 3.14 kernel is
available, and the default for the qemu reference BSPs.
The three patches which were required for the previous 3.10 libc-headers
are not required for 3.14 and can be ignored.
(From OE-Core rev: 6b25918ecce6d555632d9576e16ad443b5d1780a)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As of the 3.13 kernel bz2 compressed tarballs are not available. To support
older header tarballs, and newer ones that require the 'xz' compressed
bundles, we can break out a variable that allows versioned libc headers to
select the archive format that works.
(From OE-Core rev: 116228fceca7fc2a7b557133b1f8f28f41af1ee5)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The release kernel for Yocto 1.6 is the 3.14 kernel, so we introduce
the versioned recipes here.
(From OE-Core rev: 92776093766d4b0bb2613214274fa28dc59b6126)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit c581059df88d5801cc20ab24a096e4a67b737d49.
The same thing was already applied at a slightly different place in the file.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The purpose of this module is to deploy a test image on a EFI-enabled hardware
and run our runtime tests. A bit of background:
- testimage.bbclass uses the concept of TEST_TARGET which is a class name
that is responsible for target deploying. A layer can provide
it's own TEST_TARGET. Right now has OE-core has a QemuTarget and a SimpleRemoteTarget
(ssh into an already up and running machine and run tests), the default one being qemu.
- basically testimage does something like:
target.deploy()
try:
target.start()
runTests()
finally:
target.stop()
This module assumes a running EFI machine with gummiboot as bootloader and
core-image-testmaster installed (or similar). Also your hardware under test has
to be in a DHCP-enabled network that gives it the same IP for each reboot.
One time setup (master image):
- build core-image-testmaster with EFI_PROVIDER = "gummiboot"
- install the image on the target
Test image setup:
- build your test image, e.g core-image-sato as you usually do, but with these in local.conf:
IMAGE_FSTYPES += "tar.gz"
- Now run the tests:
INHERIT += "testimage"
TEST_TARGET = "GummibootTarget"
TEST_TARGET_IP = "192.168.2.3"
bitbake core-image-sato -c testimage
Other notes:
- TEST_POWERCONTROL_CMD (togheter with TEST_POWERCONTROL_EXTRA_ARGS) can be a command that runs on the host and does power cycling.
The test code passes one argument to that command: off, on or cycle (off then on). In my case I use something like
TEST_POWERCONTROL_CMD="powercontrol.exp test 10.11.12.1 nuc1" in local.conf.
Basically my expect script does: 'ssh test@10.11.12.1 "pyctl nuc1 <arg>" and runs a python script there that controls power for a label called nuc1'.
The reason why my expect script has to ssh into another machine is because of network topology, and that machine is the one actually connected
to the test rack and the power strip. That's why TEST_POWERCONTROL_CMD and _ARGS need to be customized for one's setup, the only requirement being
that it accepts: on/off/cycle as the last argument.
- if no command is defined it would use classic reboot. This is fine as long as the machine
actually reboots (as in the ssh test hasn't failed), but it's useful for "simple-setup-with-one-board-on-the-desk" scenario, where
some manual interaction is okay from time to time.
[YOCTO #5614]
(From OE-Core rev: e00f888a88d0851b088c232dec66418e575a2e90)
Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a custom recipe with custom initramfs and installers, that makes
it easy to deploy a master image for testing purposes.
We need a master image running on the target hardware, that should be a
known good build, with a set of utilities installed so that we use it
to deploy the images under test.
This core-image-testmaster recipe isn't a requirement per se, any image can
be used as long as the required conditions are met.
The test code assumes:
- that the device has a second rootfs labeled as testrootfs
- it has a properly configured bootloader entry (called test) for the second kernel and rootfs
- the master image has a /etc/masterimage file so it can differentiate between master
and test images
- the master image has tar, mount, bash (basically the normal linux utilities not the busybox
ones)
[YOCTO #5614]
(From OE-Core rev: dea237ccd9407288cd3a73e1deca270619dd6d4a)
Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These are meant to be used by a master image, for a simple
initial setup.
The install scripts are similar to the default ones, but:
- custom partitioning, replaces the swap partiton with a second root filesystem
- adds labels to the partitions
- preconfigures a boot loader entry for the second rootfs
Part of [YOCTO #5614]
(From OE-Core rev: 39fcab00cd3b85d40966689e31b4c7748f630739)
Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We do not DEPEND on libbsd, so we do not want to
build with it just because libutil.h is found by configure.
As noted in the patch, specifying --disable-libutil to
configure does not work, so we provide "cached" configure
variables.
(From OE-Core rev: 103ef2295c728e427acc27bb071e786946c459f2)
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If you try to set SDKMACHINE in a distro configuration file, it won't
take effect because by the time that is parsed the line in bitbake.conf
which includes the appropriate conf file for SDKMACHINE has already been
parsed. Check that SDK_ARCH has changed from its default value and show
an error if it hasn't in order to catch this misconfiguration.
Fixes [YOCTO #5861].
(From OE-Core rev: 25ba4042ae782016aaf1cb5d3dac09b2a1030a1e)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When install command sets the created directory mode, pseudo will change
the mode of the directory to 0700 incorrectly. Backport patch to fix it.
(From OE-Core rev: af595b09d570cbd320e4e138651144ac96bfbb83)
Signed-off-by: yanjun.zhu <yanjun.zhu@windriver.com>
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop --disable-ffmpegcomponents which is deprecated since libomxil-bellagio-0.9.1
Explicitly disable doc generation to prevent using doxygen from build machine.
Components are external and are available separately here:
http://sourceforge.net/projects/omxil/files/components/
(From OE-Core rev: ff321fec0c5611b69a99901cac74bfd76b409d77)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a patch to update the missed sstate event with
info about the sstate files locations that were found.
It's needed as to display the found file in the toaster ui.
Also fixes a bug where a setscene task may have appeared in the
missed list even if it was found in a sstate mirror.
(From OE-Core rev: ad66cd521d3e661dd57c5aa02c204585101984f3)
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
piglit and mesa-demos are not buildable in x11-less distros so we must
to add those only when opengl and x11 DISTRO_FEATURES are available.
(From OE-Core rev: ab0bb02d410e4f0713e75192eb217991b3f672aa)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Yocto 1.6 will support the LTSI 3.4/3.10 kernels and the 3.14 kernel. As
such, we remove the 3.8 linux-yocto recipes to keep our number of supported
kernels at three.
(From meta-yocto rev: 622c2582de7f413c7130c52fa143a06dde2bd353)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The v3.10.24 merge created a merge conflict, which was not properly
resolved. Fixing the merge conflict and fixing the build of qemu arm.
(From OE-Core rev: 2116e326d9d7039aac4ec6c7ae5d2a2bedfb4a74)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was a nasty sstate hash corruption issue occurring where the
fact the testimage bbclass was inherited meant that the checksum
changed due to testimage.bbclass being confused with image.bbclass.
This patch anchors the bbclass names to avoid this confusion.
(From OE-Core rev: 943a75a4f3b6877e4092dae14b59b7afef8cad3d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5357]
Added a paragraph at the end of this section to address the fact
that the user can now debug Bitbake's processing of signatures.
This introduces the -S bitbake option and the fact that the
user can provide a couple parameters with it: "none" and
"printdiff".
(Bitbake rev: 4093fa6c96eebe0bbafb93dc27d8a978cca436c4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The new -S syntax is in there now.
(Bitbake rev: 5a406a69c14b6ddf179fea2c4bc68cddf9eddeea)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the buildhistory directory. Added the deploy/sdk directory.
Beefed up the tmp and build directory descriptions.
(From yocto-docs rev: 3ac9435a48b6da730e640b204ba3f41daebc39e8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided better link to Wayland and a new link to Weston.
(From yocto-docs rev: 95086f7d4bf8ce3b3c33c2863435f2896c73cc3f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some minor changes as a result of a read-through of the section.
(From yocto-docs rev: 4139f67d3615d6fe3eca79356c92937a314b200e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some items found reading through the section. Needed some
cross-referencing to better targets based on newer information.
The text was quite dated in this section.
(From yocto-docs rev: eba809fd709d801bec50a820d7e6a5a79707dde6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Minor fixes throughout.
(From yocto-docs rev: d44ae0da21d84acbe1556824e228c7ab0af1ba2c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Along with some minor things I did the following:
* Added a brief explanation and reference to the reporting error
tool. It seemed like a good chapter to include it. I put it
in the debugging section.
* I added a pointer to the BitBake manual right at the top of a
section that had many usages of the bitbake command.
(From yocto-docs rev: 9317433bc715e9fdac2fc629ed659ac926d67531)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
During the read-through, I noticed that I did not have a complete
list of YP manuals in the "Introduction" section. I also added
the new BitBake manual to the list of external manuals.
(From yocto-docs rev: 46ae0400d807c733bc0c32b07b4b59cc8d6d2618)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This had been negleted and many new sections were not on the list.
It is all up to date now.
(From yocto-docs rev: 3291491ec41146a1dfa0cb2f1387fba85b1c7d24)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This information now exists in the separate BitBake User Manual.
To remove this information, the ref-bitbake.xml file was taken
out of the ref-manual.xml build, an overview bullet describing
BitBake chapter was removed from the "Introduction" chapter,
and one cross-reference link to a sub-section of the old BitBake
chapter had to be re-routed into the similar section of the BitBake
Manaul.
(From yocto-docs rev: 3828291699b5997c28a782600c9d472b8449ecd3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I made sure that the first occurrence of each "BitBake" term linked
into the "BitBake" term as defined in the dev-manual.
(From yocto-docs rev: 83e6e43d13cf5447b8ef65836d532abbb1f8b15e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #1562]
In the dev-manual, I created a new section called "Using the
Error Reporting Tool" that describes how to use this feature.
The text was based on information I received from Andreea Proca.
In the ref-manual, I added a new variable entry for ERR_REPORT_DIR
in the glossary and a new report-error class in the class chapter.
(From yocto-docs rev: 70a5538fefcc1b77958fe4b2f29be00354f4137a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5442]
Updated the TMPDIR variable to call out the scenario where a user
might want to separtely set TMPDIR to a local drive and thus be
able to have the Build Directory on NFS.
Updated the "Build Directory" term with a note indicating that by
default, TMPDIR is inside the Build Directory and thus cannot be
on NFS. However, the user is able to by-pass that per setting
TMPDIR separately outside of the Build Directory.
(From yocto-docs rev: a5a308c512a3f4285bce16f17974dbf6b67432b2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5766]
In the ref-manual, I added "Eclipse" use in the title for the
"Graphics Support" packages because the "xterm" package is required
for graphics support across all distributions.
In the dev-manual, I specifically called out the need for "xterm"
as a host package at the top of the section describing workflow
with Eclipse. I also updated the cross-reference links to the
host package and Linux distro requirements to point into the
ref-manual, which is more comprehensive, than into the QS.
(From yocto-docs rev: d3405be506fcb113f01d4fcba4631db80a1ed5dc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie
Denys Dmytriyenko
Yang Wei
Bruce Ashfield
Stefan Stanacar
Joe Slater
Paul Eggleton
yanjun.zhu
Matthieu Crapet
Cristiana Voicu
Alexandru DAMIAN
Otavio Salvador
Scott Rifenbark