Add pine64 plus patches for jailhouse v0.12. This enables us to test
pine64-plus with Jailhouse release 0.12, the latest release as of this
writing.

Signed-off-by: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

- Add the necessary machine, multiconfig and wks file.
- Add entry in images list.
- Add info in README.

Signed-off-by: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
[Jan: wrap a long README line]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Add bash history and dummy postinst script for pine64-plus.

Signed-off-by: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Add support for building pine64-plus u-boot. Use mainline u-boot + ATF.

Build only the necessary envtools. u-boot tools-only build is broken
upstream and hence not supported here.

Signed-off-by: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Enable support for pine64-plus ethernet, watchdog, pmic and regulators
in arm64_defconfig_5.4.

Signed-off-by: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Refresh some dependency versions and add a note on the ESPRESSObin that
it requires a newer, self-installed firmware for XHCI suppport.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Note that the RPi tree is rebasing, therefore also our jailhouse branch
for it. IOW, the previous RPi revision might have been broken
meanwhile. We will have to look into how to deal with that mess in the
future, possibly by not updating RPi at all.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

crosstool-ng.org is down for a couple of days. Better us the more
reliable github source. This just requires some minor adjustments to
paths and the rules file because github packages a git snapshot, not a
real release package. The snapshot also already contains a debian
folder, but we better rely on our version that is tuned for the
microblaze use case - and known to work.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

We have a new stable version, switch to it as default. As usual, this
allows to drop merged patches, and we can also remove the deviating
NUC6CAY configs for 0.11.

Unfortunately, 0.12 had a regression in some configs that affects
supported targets. So we need to add a new patch from the beginning.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Not supported so far.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Add the machine, multiconfig and wks file, extend the images.list.

The image is assembled very similarly to Raspbian, just focusing on the
support for the model 4. It is using the Raspberry bootloader to start
Linux directly but pulls in ATF before that. This implies that Linux
kernel updates on a target would need another manual step to update also
kernel.img in the boot partition.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Nothing special about this for the RPi 4, just needs the right names.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

These needs to be installed at the right place on the target rootfs so
that the driver starts to work.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This pulls the needed blobs (yeah...) for the RPi 4 from the official
repo, adds a config that loads ATF prior to starting 64-bit Linux with a
Jailhouse-specific command line, and puts all that into a package for
the assembly by the wic imager.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This will be the key to enable PSCI-based CPU hotplugging on the RPi4:
Include ATF into the boot process and patch it to provide also the
CPU_OFF functionality. The patch is pending for ATF upstream.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

The Raspberry Pi 4 is still on its way towards mainline, probably the
next LTS will look much brighter. For now, we need to maintain a
separate branch and provide a separate recipe here in order to have a
functioning kernel with the required Jailhouse patches.

The defconfig is derived from bcm2711_defconfig in that downstream
kernel.

We do not have an -rt variant at the moment because the RPi hackers
didn't provide one for 5.4 yet. So, building with --rt will just fail.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

We are no long compatible with 0.11. Therefore, build for latest by
default until 0.12 is available.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Move to 5.4-based kernel which is also needed for supporting latest
Jailhouse.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This driver comes with jailhouse-enabling/5.4 and needs to be built in
so that it is also available for the non-root cells.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Update the upstream version that brings support for kernel 5.4.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

The virtual PCI devices were relocated, and this caused changes to their
topology-derived interface names.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Account for the config format changes, including the addition of a demo
ivshmem device to the non-root linux cell. Changes are analogous to
those to qemu-x86 and linux-x86-demo.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

The gic-demo config is now called inmate-demo.

This starts the conversion to upcoming Jailhouse 0.12 / current next
branch. For a couple of commits, we have to live with a non-working
state.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Pull the ivshmem-demo code from current Jailhouse, build it for the
targets and install it in the initramfs images. This allows to test
ivshmem in non-root Linux cells.

This recipe change is avoiding a direct dependency on the Jailhouse
package for obtaining the source file so that changes to the latter do
not start to trigger the lengthy non-root-initramfs build. There aren't
many changes to the demo application in Jailhouse expected, so this
should be fine.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This comes with a reworked kernel recipe which applies config fragments
automatically.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This allows to drop the now included zynqmp fix from ATF.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

No longer needed since we no longer build our own versions.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Our public source, an OpenSUSE contrib rpm, is no longer available for
direct download. So it's no longer avoidable to adopt the two generated/
pre-built binaries we need to compile boot.bin. They originate from

https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:Zynq:ZCU100/zynqmp-hdf
https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:Zynq:ZCU100/zynqmp-fsbl



That's a bitstream for the Ultra96 which enables the console UART and a
fitting first-stage bootloader. Both are originally generated by the
proprietary Xilinx toolchain. The fsbl is then widely available in
source code, but the some binary-only bit require a specific, old
toolchain to link against. Trying that path would likely end up in
pulling most of petalinux.

Yes, this is a huge mess. We just didn't invent it.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

This brings bitbake 1.44 which changed its multiconfig syntax.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

As we are switching to the new bitbake multiconfig syntax, this is
mandatory.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

With the next QEMU release, VMX CPU features will no longer be passed
through from the host when using kvm64 as CPU. Rather use "host" as
model and ensure that incompatible PV features are off.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

These are needed on x86 to run with upcoming start-qemu.sh changes and
to fix issues with PREEMPT-RT.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Buster brings gcc 8, and that means we need the related patch for
Jailhouse 0.11.

The non-root-initramfs has to be switches to newer rules format that
allows to disable fakeroot reliably (to avoid the nesting issue).

And the orangepi target can drop the u-boot backport pick - injecting
additional apt sources via the machine conf was broken anyway and would
have exploded when adding a second ARM target.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Required with upcoming gcc 8.3.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>