[gatesgarth,hardknott,honister,kirkstone,master][PATCH 0/11] Xen on Raspberry Pi 4 fixes
A series of fixes applied to master and across stable branches where
needed to fix running Xen on the Raspberry Pi 4 board.
This updates Linux kernel configuration for Xen to remove tracking from
the linux-yocto-dev kernel, either by applying a fixed revision and
specification of a stable branch or replacing it with the linux-yocto
kernel. The Xen build configuration is updated to remove the hypervisor
defconfig for the Raspberry Pi and drop the arm64 prelink patch as a
license correction and since the build no longer needs it with the newer
Tested on hardware.
01: linux-yocto-dev, raspberrypi: apply fixed revision to kernel
02: xen: drop patch to workaround prelink on aarch64
03: xen: fix boot on the Raspberry Pi 4
04: linux-yocto-dev, raspberrypi: apply fixed revision to kernel
05: xen: drop patch to workaround prelink on aarch64
06: xen: fix boot on the Raspberry Pi 4
07: linux-yocto-dev, xen, raspberrypi: remove tracking bbappend
08: xen: drop patch to workaround prelink on aarch64
09: xen: fix boot on the Raspberry Pi 4 with Xen 4.14
10: xen, raspberry pi: replace linux-yocto-dev with linux-yocto 5.15
11: xen, raspberry pi: replace linux-yocto-dev with linux-yocto 5.15
On 21 May 2022, at 20:04, Christopher Clark <christopher.w.clark@...> wrote:Hardknott and gatesgarth are EOL so I do not think those patches are needed.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On Sat, May 21, 2022 at 3:04 PM Christopher Clark
I appreciate the patches for all the branches, it gives more
confidence in how thorough things look!
I will avoid the EOL branches, but if someone really wants them, they
are on the list and I wouldn't fight too hard about not applying them.
Just so I'm clear, there aren't actually 11 patches, just some of the
patches repeated across the various branches .. totalling 11. If that
is wrong, please do follow up to the branches with more patches, as I
definitely didn't get 11.
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
On Wed, May 25, 2022 at 8:36 AM Bruce Ashfield
Just so I'm clear, there aren't actually 11 patches, just some of theIt is a bit confusing, sorry - I sent 11 patches in total, so I put
"0/11" on the cover letter, but that's the total over 5 branches.
(They are in sequence starting here:
listed in the first message in this thread)
When I sent each patch, I put the branch name that the patch applies
to in the Subject line.
There are at most 3 patches for any given branch, and although the
patches do look similar between branches, there are small differences:
eg. selection of "v5.10/standard/bcm-2xxx-rpi" for gatesgarth vs
"v5.12/standard/bcm-2xxx-rpi" for hardknott, reflecting the state of
linux-yocto-dev at the point that the branch was active.
So I sent the patches that I tested in each branch, and I would
recommend applying the sent one rather than picking similar ones
across between branches for these.