From: Julien Grall <julien@xen.org>
To: Bertrand Marquis <Bertrand.Marquis@arm.com>,
Richard Simpson <xen@huskydog.org.uk>
Cc: xen-devel <xen-devel@lists.xenproject.org>, nd <nd@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: ARM - Successful install on RockPro64
Date: Tue, 16 Jun 2020 11:14:37 +0100 [thread overview]
Message-ID: <bf07693e-af2f-9d13-3ef5-e33a33956c1f@xen.org> (raw)
In-Reply-To: <6AB44468-BD6A-4140-B0EF-3D2E5EDC99A0@arm.com>
Hi,
On 16/06/2020 09:03, Bertrand Marquis wrote:
> Hi Richard,
>
> + Julien and Stefano
>
>> On 15 Jun 2020, at 23:29, Richard Simpson <xen@huskydog.org.uk> wrote:
>>
>> Hello,
>>
>> Just to report that I have successfully installed Xen on a Pine RockPro64 ARM SBC.
>
> Very nice :-)
>
>>
>> I am using Xen 4.13 booting directly from u-boot on an SD card and my dom0 distribution is Gentoo.
>>
>> I haven't tried to create a domU yet and I am doing everything via the serial console so I can't say anything about the graphics.
>>
>> My biggest hurdle (apart from understanding u-boot) was needing to apply the vgic-v3: fix GICD_ISACTIVER patch.
>
> What version of Linux are you running ?
> I added Julien and Stefano so that we reactivate the discussion on this patch.
A temporary patch to mark the register RAZ has been merged a couple of
months ago. See 0796cb907f2c "xen/arm: vgic-v3: fix GICD_ISACTIVER
range". This should probably be backported to Xen 4.13 and 4.12.
Although, I haven't seen any update for a proper fix yet.
Cheers,
--
Julien Grall
prev parent reply other threads:[~2020-06-16 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 22:29 ARM - Successful install on RockPro64 Richard Simpson
2020-06-16 8:03 ` Bertrand Marquis
2020-06-16 8:33 ` Richard Simpson
2020-06-16 10:26 ` Julien Grall
2020-06-17 22:28 ` Richard Simpson
2020-06-24 12:42 ` Julien Grall
2020-06-26 23:02 ` Richard Simpson
2020-06-27 20:58 ` Richard Simpson
2020-06-16 10:14 ` Julien Grall [this message]
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=bf07693e-af2f-9d13-3ef5-e33a33956c1f@xen.org \
--to=julien@xen.org \
--cc=Bertrand.Marquis@arm.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xen@huskydog.org.uk \
/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).