Age | Commit message (Collapse) | Author |
|
Update machine include files to allow overriding of KERNEL_IMAGETYPE.
[
with the following 2 tweaks by Trevor:
- remove the "v3" from the commit's subject
- extended patch to rk3308 and rk3588s, which were added in between this patch
being submitted, and this patch being applied
]
Signed-off-by: Anthony Davies <anthony.t.davies@gmail.com>
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
Remove the non-rockchip architectures from the kernel build since these are
all a waste of build time, filesystem space, and runtime memory.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
The _virtual notation is not an override. These syntax "fixes" need to be
reverted.
In the case of the kernel override, when it was added, the rock-pi-e needed
the latest kernel (linux-yocto-dev) but now the default linux-yocto kernel
will suffice. So this mistake actually switched the rock-pi-e from
linux-yocto-dev back to linux-yocto inadvertently but at a time when
linux-yocto-dev was no longer required.
In the case of the bootloader overrides, u-boot was always the default, so
these overrides were always redundant.
Therefore, in the end, simply removing these overrides is the best way
forward (considering these aren't doing anything, and the builds are working
fine regardless).
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
With bitbake commit 7dcf317cc141dc980634f8c18bfa84f83e57206a
("bitbake: Switch to using new override syntax"), applied on
Aug 2, 2021, the OVERRIDE separator is now a colon instead of
an underscore. Therefore all builds performed with a bitbake
before this change must use a meta-rockchip commit before this
one, and any builds performed with a bitbake after this change
must use a meta-rockchip starting from this commit onwards.
Build-tested for all meta-rockchip MACHINEs.
Run tested on:
- tinker-board
- nanopi-m4-2gb
- rock64
- rock-pi-4b
- rock-pi-e
The tinker-board and rock-pi-e work fine. The rest of the boards
seem to have a, hopefully unrelated, issue running a
5.13-yocto-standard kernel. However, all boards work with the
5.10-yocto-standard kernel.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
By exporting a couple more variables the wks file for every rockchip device
can be built from one template instead of having separate wks files for each
board and platform.
The following BSP variables were checked before and after this change to make
sure they remained valid/sensible:
- WKS_FILE
- UBOOT_SUFFIX
- SPL_BINARY
- IMAGE_FSTYPES
Built-tested for every MACHINE in this BSP.
Run-tested on the following devices to ensure they continue to boot correctly
to a cmdline (core-image-base):
- tinker-board
- rock-pi-e
- rock-pi-4b
- rock64
- nanopi-m4-2gb
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
Consolidate all the various console definitions to the common
conf/machine/include/rockchip-defaults.inc file and create
RK_CONSOLE_BAUD and RK_CONSOLE_DEVICE variables that can be
reused in the wks files.
The following variables were checked before and after this patch
to make sure they are sensible:
- SERIAL_CONSOLES
- RK_CONSOLE_DEVICE
- RK_CONSOLE_BAUD
A boot test was performed on the following boards to make sure
they all continue to boot to a cmdline:
- tinker-board
- rock-pi-e
- nanopi-m4-2gb
- rock64
- rock-pi-4b
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
Updates all machines to use the linux-yocto kernel from OE-core instead
of maintaining distinct kernels in this repository.
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Adds support for the rk3399 SoC. Notably:
*) Split out the default kernel config and image type from
rockchip-defaults.inc now that not all support chips are ARMv7
*) Apply a patch to Arm Trusted Firmware to fix a compile issue
*) Arm Trusted Firmware requires the arm-none-eabi-native compiler to
compile the M0 firmware.
*) Modify u-boot to pull in the ATF files when compiling
*) The rk3399 is support by the panfrost driver in mesa, so enable it
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Coverts the firefly-rk3288, tinker-rk3288, and vyasa-rk3288 machines to
use wic instead of the rockchip-gpt-img class. The rock2-squared machine
has to keep the older image class because u-boot doesn't provided a
combined idbloader for it.
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Appends the GPT image type to IMAGE_FSTYPES instead of overriding. This
allows additional types to be preserved if they are specified in
local.conf
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Recent versions of u-boot use a combined SPL/TPL (called idbloader.img)
in the loader1 partition, which then loads the full u-boot from the
loader2 partition. Update the GPT partition class to reflect this
change. Additionally, remove the u-boot bbappend since it is no longer
needed.
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
The upstream u-boot bootloader seems to work fine for both the tinker-rk3288
and the firefly-rk3288, so switch to it by default for rk3288 boards.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
Create a conf/machine/include/rockchip-defaults.inc that includes
rockchip-wide defaults, then organize the conf/machine/include/rk*.inc and
individual machine files accordingly.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
Allow the user to ultimately choose the kernel. Make 'linux' the _preferred_,
not the _required_.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Reviewed-by: Eddie Cai <eddie.cai.linux@gmail.com>
|
|
Configure any rk3288 build to generate the new GPT image which is then either
flashed to eMMC or dd'ed to an SDcard.
Reviewed-by Eddie Cai <eddie.cai.linux@gmail.com>
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
Set the default preferred bootloader for firefly-rk3288 to be u-boot-rockchip
and set the default name of the SPL binary.
Reviewed-by Eddie Cai <eddie.cai.linux@gmail.com>
Reviewed-by: Jacob Chen <jacob-chen@iotwrt.com>
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
Enable machine overrides for RK3288.
Signed-off-by: Eddie Cai <eddie.cai.linux@gmail.com>
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
|
|
The DEFAULTTUNE configuration should not be set at the BSP layer but in a
DISTRO layer (or a user's conf/local.conf). Remove the two DEFAULTTUNEs that
are currently in the layer and add a note in the README to inform users of
this issue and potential settings.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Reviewed-by: Romain Perier <romain.perier@collabora.com>
|
|
KBUILD_DEFCONFIG already existed in the yocto project. When it is used
with the kernel-yocto bbclass, it specifies an "in-tree" kernel
configuration file for use during a kernel build. So instead of use our
own variable we use the standard variable designed for that purpose
Signed-off-by: Romain Perier <romain.perier@free-electrons.com>
|
|
This variable will hold the name of the in-tree defconfig to use
to configure the kernel before compile it. This is better to use
in-tree config file now, is we don't plan to maintain a defconfig
file per board and it is also synced with upstream.
Signed-off-by: Romain Perier <romain.perier@free-electrons.com>
Reviewed-by: Trevor Woerner <twoerner@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>
|
|
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>
|
|
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>
|