On 2016/3/31 0:47, Julien Grall wrote:
> Hi,
>
> On 30/03/16 17:11, Konrad Rzeszutek Wilk wrote:
>> On Wed, Mar 30, 2016 at 06:08:13PM +0800, Shannon Zhao wrote:
>>> From: Shannon Zhao
>>>
>>> It needs to map platform or amba device mmio to Dom0 on ARM. But when
>>> booting with ACPI, it can't
Hi,
On 30/03/16 17:11, Konrad Rzeszutek Wilk wrote:
On Wed, Mar 30, 2016 at 06:08:13PM +0800, Shannon Zhao wrote:
From: Shannon Zhao
It needs to map platform or amba device mmio to Dom0 on ARM. But when
booting with ACPI, it can't get the mmio region in Xen due to lack of
AML interpreter to p
On Wed, Mar 30, 2016 at 06:08:13PM +0800, Shannon Zhao wrote:
> From: Shannon Zhao
>
> It needs to map platform or amba device mmio to Dom0 on ARM. But when
> booting with ACPI, it can't get the mmio region in Xen due to lack of
> AML interpreter to parse DSDT table. Therefore, let Dom0 call a
>
>>> On 30.03.16 at 12:08, wrote:
> From: Shannon Zhao
>
> It needs to map platform or amba device mmio to Dom0 on ARM. But when
> booting with ACPI, it can't get the mmio region in Xen due to lack of
> AML interpreter to parse DSDT table. Therefore, let Dom0 call a
> hypercall to map mmio region
From: Shannon Zhao
It needs to map platform or amba device mmio to Dom0 on ARM. But when
booting with ACPI, it can't get the mmio region in Xen due to lack of
AML interpreter to parse DSDT table. Therefore, let Dom0 call a
hypercall to map mmio region when it adds the devices.
Here we add a new
