[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Duplicated memory node in the Device-Tree (WAS [XEN] Re: Duplicated memory nodes cause the BUG())
- To: Stefano Stabellini <sstabellini@xxxxxxxxxx>, Julien Grall <julien.grall@xxxxxxx>
- From: Andrii Anisov <andrii_anisov@xxxxxxxx>
- Date: Wed, 26 Jul 2017 12:08:58 +0300
- Cc: devicetree@xxxxxxxxxxxxxxx, Wei Liu <wei.liu2@xxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
- Delivery-date: Wed, 26 Jul 2017 09:09:19 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Hello,
On 25.07.17 21:11, Stefano Stabellini wrote:
On Tue, 25 Jul 2017, Julien Grall wrote:
Furthermore, if you look at the wikipage for Renesas R-Car on Xen (see [1]), a
specific DT for Xen is provided.
Well, we introduced a specific DT as a faster way to get the system up
and running. But the target is to get rid of it.
Except that nasty issue with memory banks, there is another one: how to
handle reserved memory regions needed for some IP's functionality (e.g.
ADSP).
As I already said I do cleanup remaining nits one by one.
That's true. It does not make sense to do this until we get rid of the
Xen specific R-Car device tree on the wiki.
IMO, we it should appear correspondent functionality in XEN first, and
latter get rid of specific device tree on the wiki. So that we will have
the wiki steps adequate to the current master.
--
*Andrii Anisov*
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel
|
