From: Julien Grall <julien.grall@arm.com>
To: Andrii Anisov <andrii_anisov@epam.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Andrii Anisov <andrii.anisov@gmail.com>
Subject: Re: Renesas R-Car Gen3 SoCs earlyprintk support.
Date: Thu, 6 Jul 2017 12:43:11 +0100 [thread overview]
Message-ID: <50f7bba4-2d3c-ae1c-a56b-e5e51870b5fd@arm.com> (raw)
In-Reply-To: <0c445063-a265-e5e9-388e-34b9405635d9@epam.com>
Hi Andrii,
On 06/07/17 12:31, Andrii Anisov wrote:
>
> On 05.07.17 20:18, Julien Grall wrote:
>> I prefer to say: "This is not supported today because of XXX. With the
>> following patches, it is possible to boot.". Rather than "This is
>> supported if you download from this github, I don't give Xen version
>> and don't even mention the patches on top...".
> Actually statements "Xen is fully supported" and "changes are required
> in the BSP" do not contradict each other, if we treat those changes
> (disabling OP-TEE) as a matter of BSP configuration (which they are). Do
> you agree?
Well, I would expect no changes in either in the BSP, kernel,
device-tree when you run with Xen.
For all the platform currently supported, we can boot Xen with the
device-tree provided by the firmware or from Linux upstream. The Linux
kernel is not modified but recompiled with XEN options enabled.
Xen should take care of the missing mappings and/or disabling device not
supported.
So I don't see how the Renesas board should be different here. If you
need to modify the device-tree or Linux. Then there is missing pieces in
Xen or the BSP is not doing the right thing (i.e auto-detect support).
>
>> The wiki page gives the false impression that Xen upstream is fully
>> supported on Renesas, whilst from what you said this is not true and
>> change are required in the BSP.
> I would say in different words: XEN upstream is fully supported on
> Renesas, but due to XEN functionality gaps the BSP should be adjusted
> appropriately.
You can't say in the same sentence, the board is fully supported and
there are missing functionality that requires change in the BSP. They
are incompatible.
I agree that we are able to boot Xen on Renesas (not sure to which
extend without modification). But you can't claim it is fully supported
until all those gaps are fixed.
Anyway, we should at least list the gaps on the wiki page for helping
potential users.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-06 11:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 16:29 Renesas R-Car Gen3 SoCs earlyprintk support Andrii Anisov
2017-07-05 16:29 ` [PATCH 1/2] xen:arm64: Add SCIF UART support for earlyprintk Andrii Anisov
2017-07-26 15:25 ` Andrii Anisov
2017-07-26 15:33 ` Julien Grall
2017-07-26 15:39 ` Andrii Anisov
2017-07-05 16:29 ` [PATCH 2/2] xen:arm: earlyprintk configuration for R-Car Gen3 boards Andrii Anisov
2017-07-26 15:25 ` Andrii Anisov
2017-07-26 15:34 ` Julien Grall
2017-07-05 16:34 ` Renesas R-Car Gen3 SoCs earlyprintk support Julien Grall
2017-07-05 16:41 ` Andrii Anisov
2017-07-05 16:50 ` Julien Grall
2017-07-05 17:00 ` Andrii Anisov
2017-07-05 17:18 ` Julien Grall
2017-07-06 11:31 ` Andrii Anisov
2017-07-06 11:43 ` Julien Grall [this message]
2017-07-06 12:24 ` Andrii Anisov
2017-07-06 12:35 ` Julien Grall
2017-07-07 10:47 ` Andrii Anisov
2017-07-07 10:55 ` Julien Grall
2017-07-07 12:11 ` Andrii Anisov
2017-07-14 17:00 ` Andrii Anisov
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=50f7bba4-2d3c-ae1c-a56b-e5e51870b5fd@arm.com \
--to=julien.grall@arm.com \
--cc=andrii.anisov@gmail.com \
--cc=andrii_anisov@epam.com \
--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).