[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: Julien Grall <julien.grall@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>
- From: Andrii Anisov <andrii_anisov@xxxxxxxx>
- Date: Wed, 26 Jul 2017 15:10:17 +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 12:10:29 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Dear Julien.
On 26.07.17 12:22, Julien Grall wrote:
It sounds like to me that a non-modified DT for Xen on R-Car is not
for tomorrow...
Yep, unfortunately it is not for tomorrow.
So here, the first and only sensible option is to work with the vendor
to modify the device-tree.
OK, I'll move in that direction instead of pushing changes into hypervisor.
If the vendor is not willing to do it, then we can discuss about
implementing a fix in Xen.
I had it in my mind as a generic stuff. Partially inspired by LK approach.
--
*Andrii Anisov*
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel
|
