Hi Stefano,
On 20/02/17 18:13, Julien Grall wrote:
On 20/02/17 18:12, Stefano Stabellini wrote:
On Mon, 20 Feb 2017, Julien Grall wrote:
Hi Stefano,
On 02/16/2017 01:41 AM, Stefano Stabellini wrote:
On Fri, 3 Feb 2017, Julien Grall wrote:
On ARM, when the user put 'acpi=force' Xen will use
On Mon, 20 Feb 2017, Julien Grall wrote:
> Hi Stefano,
>
> On 02/16/2017 01:41 AM, Stefano Stabellini wrote:
> > On Fri, 3 Feb 2017, Julien Grall wrote:
> > > On ARM, when the user put 'acpi=force' Xen will use ACPI over DT.
> > > Currently, if Xen fails to initialize ACPI it will fallback on DT.
Hi Stefano,
On 20/02/17 18:12, Stefano Stabellini wrote:
On Mon, 20 Feb 2017, Julien Grall wrote:
Hi Stefano,
On 02/16/2017 01:41 AM, Stefano Stabellini wrote:
On Fri, 3 Feb 2017, Julien Grall wrote:
On ARM, when the user put 'acpi=force' Xen will use ACPI over DT.
Currently, if Xen fails
Hi Stefano,
On 02/16/2017 01:41 AM, Stefano Stabellini wrote:
On Fri, 3 Feb 2017, Julien Grall wrote:
On ARM, when the user put 'acpi=force' Xen will use ACPI over DT.
Currently, if Xen fails to initialize ACPI it will fallback on DT.
This behavior makes difficult for a user to notice Xen
On Fri, 3 Feb 2017, Julien Grall wrote:
> On ARM, when the user put 'acpi=force' Xen will use ACPI over DT.
> Currently, if Xen fails to initialize ACPI it will fallback on DT.
>
> This behavior makes difficult for a user to notice Xen didn't used ACPI
> has requested on platform where the
On ARM, when the user put 'acpi=force' Xen will use ACPI over DT.
Currently, if Xen fails to initialize ACPI it will fallback on DT.
This behavior makes difficult for a user to notice Xen didn't used ACPI
has requested on platform where the firmware is providing both ACPI and DT.
Rather than
