| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
The 6.10 build has been tested on both a BeaglePlay and qemu, so we can
remove the pinning now.
(From meta-yocto rev: d19d6046e96b1c94ee50a6140b1338a50a2cef20)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
We want to introduce the 6.10 linux-yocto recipe, but genericarm64
hasn't been valided for it yet. As such, let's temporarily set the
preferred version to 6.6 so the builds don't break.
(From meta-yocto rev: 6ba3b6f15bf2460432da3a3aee782976e778381c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
genericarm64 supports runqemu, so testimage should work. However, out of
the box it does not:
runqemu - ERROR - BIOS .../tmp/deploy/images/genericarm64/u-boot.bin not found
That is because we make the user explicitly build the qemu-targetting u-boot
to avoid the confusing situation where they have real hardware but the
deploy directory contains a u-boot for qemu.
In automated testing situations, however, we can be a bit more helpful
and make testimage depend on u-boot. This will lead to u-boot binaries
being in deploy, but at this point the user is already running the images
inside a qemu.
Reported-by: James McGregor <James.McGregor2@arm.com>
(From meta-yocto rev: 90b45c62d34396a20078b55d7d36f66b4e2177f7)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
testimage on core-image-sato fails in parselogs and xorg tests. We can
add the virtio gpu to address these issues (like what is being done in
qemuarm, qemuarm64, and qemuarmv5).
(From meta-yocto rev: ddf075e2abfba6479efc2bc5fe1c41ba6079e355)
Signed-off-by: Jon Mason <jdmason@kudzu.us>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A basic SystemReady IR system can be provided by qemu-system-aarch64
and u-boot, so tell u-boot to build the qemu_arm64 machine and configure
qemuboot to start that u-boot and search the virtio-attached wic image
for the EFI boot partition.
Currently this machine support emulated (Cortex-A76) and virtualised (KVM)
execution, and virtio storage/network/console. Display support will be
added shortly.
Note that this machine still doesn't build U-Boot by default, as a u-boot
binary for qemu in deploy would potentially confuse users who want to
boot on real hardware and think this u-boot is needed. If you wish to
use genericarm64 with runqemu, you'll need to manually bitbake u-boot.
(From meta-yocto rev: cd40f405844c1ccfabcbe64ad6be5d98d0221f72)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't install _all_ of the firmware, as that's huge (almost 1GB). Instead
install a few pieces of firmware for common hardware.
Also use the same list of packages to populate the initramfs, so there's
no need to manually sync the package lists (as initramfs doesn't install
the MACHINE_EXTRA_RRECOMMENDS automatically).
(From meta-yocto rev: a5aa914990f36cc5175577983dd1ad1aa0bb81f2)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
This is a new 64-bit "generic" Arm machine, that expects the hardware to
be SystemReady IR compatible.
(From meta-yocto rev: 68de209f58917d8e7108caacfefc55bbe0e0c5a2)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
