On 01/23/2015 08:43 AM, Rafael J. Wysocki wrote:
> Hi Al,
>
> On Thursday, January 22, 2015 05:44:37 PM al.st...@linaro.org wrote:
>> From: Al Stone
>>
>> The use of the ACPI _OSI method in Linux has a long and sordid history.
>> Instead of perpetuating past complications on new architectures,
Hi Al,
On Thursday, January 22, 2015 05:44:37 PM al.st...@linaro.org wrote:
> From: Al Stone
>
> The use of the ACPI _OSI method in Linux has a long and sordid history.
> Instead of perpetuating past complications on new architectures, the
> consensus amongst those writing the ACPI
On 01/23/2015 08:43 AM, Rafael J. Wysocki wrote:
Hi Al,
On Thursday, January 22, 2015 05:44:37 PM al.st...@linaro.org wrote:
From: Al Stone al.st...@linaro.org
The use of the ACPI _OSI method in Linux has a long and sordid history.
Instead of perpetuating past complications on new
Hi Al,
On Thursday, January 22, 2015 05:44:37 PM al.st...@linaro.org wrote:
From: Al Stone al.st...@linaro.org
The use of the ACPI _OSI method in Linux has a long and sordid history.
Instead of perpetuating past complications on new architectures, the
consensus amongst those writing the
From: Al Stone
The use of the ACPI _OSI method in Linux has a long and sordid history.
Instead of perpetuating past complications on new architectures, the
consensus amongst those writing the ACPI specification and those using
it seems to be to ultimately deprecate the use of _OSI. I plan to
From: Al Stone al.st...@linaro.org
The use of the ACPI _OSI method in Linux has a long and sordid history.
Instead of perpetuating past complications on new architectures, the
consensus amongst those writing the ACPI specification and those using
it seems to be to ultimately deprecate the use of
6 matches
Mail list logo
