[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Xen on RP4
On Wed, Nov 25, 2020 at 7:36 PM Elliott Mitchell <ehem+xen@xxxxxxx> wrote: > > On Wed, Nov 25, 2020 at 10:57:31AM -0800, Stefano Stabellini wrote: > > On Tue, 24 Nov 2020, Elliott Mitchell wrote: > > > My testing section for Xen is: > > > xen_hypervisor /boot/xen-4.14-arm64.efi > > > xen_module /boot/vmlinuz-5.8.10-2rp4-6.1.7 > > > root=UUID=01234567-dead-beef-d13d-456789abcdef ro > > > devicetree /boot/dtb-5.8.10-2rp4-6.1.7 > > > xen_module --nounzip /boot/initrd.img-5.8.10-2rp4-6.1.7 > > > > > > I've frankly got no idea how to ensure the correct device-tree is passed > > > to Xen. Is GRUB's `devicetree` command correct when loading Xen? Is a > > > device-tree matched to the Linux kernel appropriate for Xen? > > > > > > (I'm guessing the second is "yes", but the first I don't have a clue) > > > > Yes, devicetree is correct. I have not used the graphical output, so I > > cannot help you there but yes the best bet is to use the devicetree that > > comes with the kernel. > > Well, I've now got everything together for a "proper" Debian Raspberry PI > installation. Apparently since 5.2 (perhaps earlier, but 5.2 is > confirmed), Debian's kernel source packages have had their Raspberry PI > device-trees garbled. I do have full untouched Linux kernel source > handy, but I tend to stick with the distribution until that proves > untenable. Yup. Same here. I started with upstream kernel, wasted a lot of time, threw in the towel and imported all of the RPi Foundation patches wholesale :-( Thanks, Roman.
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |