From: Roman Shaposhnik <roman@zededa.com>
To: Elliott Mitchell <ehem+xen@m5p.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen on RP4
Date: Fri, 27 Nov 2020 23:59:10 -0800 [thread overview]
Message-ID: <CAMmSBy_4ry2DwMNT1Ai1-11wBHHuO71muvkfEWLRV=h0QiKyoA@mail.gmail.com> (raw)
In-Reply-To: <X78irfLB6DQhkPvd@mattapan.m5p.com>
On Wed, Nov 25, 2020 at 7:36 PM Elliott Mitchell <ehem+xen@m5p.com> 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.
next prev parent reply other threads:[~2020-11-28 7:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 3:37 Xen on RP4 Elliott Mitchell
2020-11-25 4:01 ` Roman Shaposhnik
2020-11-25 4:41 ` Elliott Mitchell
2020-11-25 4:45 ` Roman Shaposhnik
2020-11-25 5:16 ` Elliott Mitchell
2020-11-25 18:57 ` Stefano Stabellini
2020-11-26 3:36 ` Elliott Mitchell
2020-11-28 7:59 ` Roman Shaposhnik [this message]
2020-11-28 18:15 ` Elliott Mitchell
2020-11-28 4:56 ` Elliott Mitchell
2020-11-25 19:45 ` Roman Shaposhnik
[not found] <20201011051933.GA77136@mattapan.m5p.com>
[not found] ` <alpine.DEB.2.21.2010121138480.10386@sstabellini-ThinkPad-T480s>
[not found] ` <20201012215751.GB89158@mattapan.m5p.com>
[not found] ` <c38d78bd-c011-404b-5f59-d10cd7d7f006@xen.org>
[not found] ` <20201016003024.GA13290@mattapan.m5p.com>
[not found] ` <23885c28-dee5-4e9a-dc43-6ccf19a94df6@xen.org>
[not found] ` <20201022021655.GA74011@mattapan.m5p.com>
[not found] ` <alpine.DEB.2.21.2010221620230.12247@sstabellini-ThinkPad-T480s>
[not found] ` <20201023005629.GA83870@mattapan.m5p.com>
[not found] ` <alpine.DEB.2.21.2010221801490.12247@sstabellini-ThinkPad-T480s>
[not found] ` <20201023211941.GA90171@mattapan.m5p.com>
2020-10-23 23:59 ` Stefano Stabellini
2020-10-24 1:56 ` Elliott Mitchell
2020-10-24 3:13 ` Elliott Mitchell
2020-10-24 4:34 ` Elliott Mitchell
2020-10-24 5:35 ` Elliott Mitchell
2020-10-26 13:31 ` Julien Grall
2020-10-26 16:03 ` Elliott Mitchell
2020-10-26 18:44 ` Julien Grall
2020-10-26 21:32 ` Elliott Mitchell
2020-10-28 1:54 ` Elliott Mitchell
2020-10-29 0:37 ` Stefano Stabellini
2020-10-29 5:20 ` Jürgen Groß
2020-10-29 19:57 ` Stefano Stabellini
2020-11-10 23:25 ` Elliott Mitchell
2020-11-11 2:59 ` Christopher Clark
2020-10-29 21:29 ` Elliott Mitchell
2020-10-30 20:10 ` Stefano Stabellini
2020-11-01 17:26 ` Ash Wilding
2020-11-02 21:22 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMmSBy_4ry2DwMNT1Ai1-11wBHHuO71muvkfEWLRV=h0QiKyoA@mail.gmail.com' \
--to=roman@zededa.com \
--cc=ehem+xen@m5p.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).