Re: ARM - Successful install on RockPro64

From: Julien Grall <julien@xen.org>
To: Richard Simpson <xen@huskydog.org.uk>,
	Bertrand Marquis <Bertrand.Marquis@arm.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, nd <nd@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>
Subject: Re: ARM - Successful install on RockPro64
Date: Wed, 24 Jun 2020 13:42:16 +0100	[thread overview]
Message-ID: <e786262c-d326-66d0-e3ed-bfb9e6e3bd93@xen.org> (raw)
In-Reply-To: <49e5b539-145a-726a-fb80-a93e65e44ca0@huskydog.org.uk>

On 17/06/2020 23:28, Richard Simpson wrote:
> Hello Julien,

Hello Richard,

Apologies for the late answer.

> I have just tried 4.14-rc2 and it seems to work fine.

Glad to hear that. Thank you for the testing!

> I think that the most useful page regarding the board is the one for the 
> Ibox3399 since this refers to the RK3399 chip which the RockPro64 uses 
> (shouldn't the page actually be called RK3399 to make it more generic).

I agree with the renaming here.

> Perhaps I can most usefully record what I did by updating that page and 
> making sure that the instructions work correctly. If there is additional 
> stuff relevant to the RockPro64 over and above the generic RK3399 info 
> then I'll give some thought to how to best record it.  I will eventually 
> be writing a fuller report on my progress on my blog at 
> funfoodfreedom.huskydog.org.uk.

Any additional content on the wiki will be greatly appreciated. By 
default new wiki account doesn't have write permission, but we can 
enable it for you if you provide us your username.

> 
> I now need to finish automating the boot process (still requires manual 
> u-boot command) and figure out how to get the console log to work. 

I wrote a small u-boot script in the past to try to automate the boot 
(see [2]).

I vaguely remember some quoting issue and missing 0x in front of values 
depending on the U-boot configuration you use. So you may have to tweak 
it a bit.

> Currently I can either see the xen and linux kernel boot messages OR see 
> the dom0 console, but not both.

Can you provide the kernel/xen command lines you use in the two cases?

As an aside, I know that on some setup Linux will try to disable the 
clock of the UART used by Xen. One of the symptoms is the UART is 
becoming completely unusable half way through Linux boot.

You may want to try to pass clk_ignored_unused to see if it helps.

> On one more related note:  I suspect that Xen would run on the 
> PineBookPro as well as I get the impression that it uses very similar 
> hardware.  Of course that would rely on the GPU etc which I haven't 
> tested at all as I am using the serial console.
I wouldn't expect any issue to use the GPU in dom0 at least if you don't 
have an IOMMU on the platform. The trouble may be more with the 
bootloader if it doesn't drop you in hypervisor mode.

> 
> Finally, when I joined this mailing list I asked for a daily digest. 
> However I seem to be getting a new digest every hour or so.  Is this right?

I haven't used the digest myself. I CC Ian Jackson who may be able to 
help you.

Cheers,

[2] https://xenbits.xen.org/people/julieng/load-xen-tftp.scr.txt

-- 
Julien Grall