On 02/18/16 21:16, Ard Biesheuvel wrote:
> On 18 February 2016 at 21:14, Laszlo Ersek wrote:
>> On 02/18/16 21:03, Ard Biesheuvel wrote:
>>> The ACPI spec predates the AARCH64 architecture by 5 versions, so there
>>> is no point in supporting anything below v5.0. So set the PCD that
>>> controls t
On 18 February 2016 at 21:16, Ard Biesheuvel wrote:
> On 18 February 2016 at 21:14, Laszlo Ersek wrote:
>> On 02/18/16 21:03, Ard Biesheuvel wrote:
>>> The ACPI spec predates the AARCH64 architecture by 5 versions, so there
>>> is no point in supporting anything below v5.0. So set the PCD that
>>
On 18 February 2016 at 21:14, Laszlo Ersek wrote:
> On 02/18/16 21:03, Ard Biesheuvel wrote:
>> The ACPI spec predates the AARCH64 architecture by 5 versions, so there
>> is no point in supporting anything below v5.0. So set the PCD that
>> controls the ACPI table generation to the appropriate val
On 02/18/16 21:03, Ard Biesheuvel wrote:
> The ACPI spec predates the AARCH64 architecture by 5 versions, so there
> is no point in supporting anything below v5.0. So set the PCD that
> controls the ACPI table generation to the appropriate value.
>
> Note that the current consumers of this PCD onl
The ACPI spec predates the AARCH64 architecture by 5 versions, so there
is no point in supporting anything below v5.0. So set the PCD that
controls the ACPI table generation to the appropriate value.
Note that the current consumers of this PCD only check whether bit 1
is set or not (i.e., ACPI v1.
5 matches
Mail list logo