Rename the MACHINE configurations to better match the OE pattern of using the
board's name.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Reviewed-by: Romain Perier <romain.perier@gmail.com>
None of the machines based on the RK3066 (or compatible) use an initrd image,
therefore an update image can't be successfully generated for them. Therefore
remove the request to try building this artifact.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Reviewed-by: Romain Perier <romain.perier@gmail.com>
As of the 2015/09/04 commit 039211f0d8fe79d07b65f2f02e299b9656034214 on
openembedded-core, gcc 5.2 (5.%) is now the default on master. Therefore there
is no need to request it explicitly.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Reviewed-by: Romain Perier <romain.perier@gmail.com>
This is the chrome OS verified boot utils, required to generate
partition layout and sign kernel on veyron platforms
Signed-off-by: Romain Perier <romain.perier@gmail.com>²
This includes modules and firmwares to have a working drm and wifi. It also
defines the right x11 packages and dependencies.
Signed-off-by: Romain Perier <romain.perier@gmail.com>
This is the xorg driver required to work with the Rockchip DRM.
It works with both the one from linux-veyron and the one in the
linux mainline kernel.
Signed-off-by: Romain Perier <romain.perier@gmail.com>
It includes firmware and system files for Broadcom bcm4354 required
to work with the linux kernel. These are the files from chromeos.
Signed-off-by: Romain Perier <romain.perier@gmail.com>
This is the chromeos Broadcom patchram utility. We need it in order
to kick bluetooth device dynamically and "patch" bcm4354 chip with
the right firmware. It will be only required on linux-veyron, not
with linux mainline.
Signed-off-by: Romain Perier <romain.perier@gmail.com>
None of the machines based on the RK3066 (or compatible) use an initrd image,
therefore an update image can't be successfully generated for them. Therefore
remove the request to try building this artifact.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Reviewed-by: Romain Perier <romain.perier@gmail.com>
As of the 2015/09/04 commit 039211f0d8fe79d07b65f2f02e299b9656034214 on
openembedded-core, gcc 5.2 (5.%) is now the default on master. Therefore there
is no need to request it explicitly.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Update documentation to show that we now support yocto 1.9_M2
Signed-off-by: Romain Perier <romain.perier@gmail.com>
Reviewed-by: Trevor Woerner <twoerner@gmail.com>
Which is formally known as the Asus C201 Chromebook
Signed-off-by: Romain Perier <romain.perier@gmail.com>
Reviewed-by: Trevor Woerner <twoerner@gmail.com>
Support for this tune is now supported in yocto 1.9. As it comes
with gcc 5, we also need to require gcc 5.2 and minimal compiler
version.
Signed-off-by: Romain Perier <romain.perier@gmail.com>
Reviewed-by: Trevor Woerner <twoerner@gmail.com>
This section explains how to send patches to the Yocto Project mailing list
and the required patches format
Signed-off-by: Romain Perier <romain.perier@gmail.com>
Machine descriptions are shown on layers.openembedded.org, so we need something
clear and understandable for the user.
Signed-off-by: Romain Perier <romain.perier@gmail.com>
Reviewed-by: Trevor Woerner <twoerner@gmail.com>
As rk3288 itself is not a machine nor a generic one that we plan to support,
and as this file was created to factorize code between rk3288-based platforms,
that's better to move it into the include directory.
Signed-off-by: Romain Perier <romain.perier@gmail.com>
Reviewed-by: Trevor Woerner <twoerner@gmail.com>
It does not match any machine, and I think that it might be difficult to ensure
that it will work on all rk3188-based devices if we are not able to test...
Signed-off-by: Romain Perier <romain.perier@gmail.com>
Reviewed-by: Trevor Woerner <twoerner@gmail.com>
This include file is used by rk3066 and rk3188 based devices. So this
is better to rename it rk3066.inc and to create another include file
rk3188.inc which simply includes it. In that way, we have one include
file for each SoC and it reduces confusions.
Signed-off-by: Romain Perier <romain.perier@gmail.com>
Reviewed-by: Trevor Woerner <twoerner@gmail.com>
That's very important to be able to redefine some variables for the need
of custom kernels. As on rockchip-based devices the serial interface might
change from a kernel to another, makes it overridable using '?='.
Signed-off-by: Florent Revest <revestflo@gmail.com>
Reviewed-by: Romain Perier <romain.perier@gmail.com>
In fido, "base-files" now creates symlinks /var/log and /var/tmp which
are redirected to /var/volatile/log and /var/volatile/tmp. These
subdirectories are created by init managers like systemd or sysvinit, so
petitboot initramfs needs to create them, as well. Otherwise pb-discover logs
everything to the standard output as its log directory does not exist.
