>
> To address your comment, I was trying to differentiate between the existence
> of the _STR method and the failure to evaluate it.
> If an STR method exists, we create the sysfs file. If it fails to
evaluate, we will see "No Description" when we read the file.
> This would indicate that
To address your comment, I was trying to differentiate between the existence
of the _STR method and the failure to evaluate it.
If an STR method exists, we create the sysfs file. If it fails to
evaluate, we will see No Description when we read the file.
This would indicate that something
.kernel.org; linux-a...@vger.kernel.org
> Subject: Re: [PATCH] ACPI: Add new sysfs interface to export device
> description
>
> Hi Lance,
>
> 2012/09/08 1:28, Lance Ortiz wrote:
> > Add support to export the device description obtained from the ACPI
> _STR
> > method, if
-a...@vger.kernel.org
Subject: Re: [PATCH] ACPI: Add new sysfs interface to export device
description
Hi Lance,
2012/09/08 1:28, Lance Ortiz wrote:
Add support to export the device description obtained from the ACPI
_STR
method, if one exists for a device, to user-space via a sysfs
interface.
This new
Hi Lance,
2012/09/08 1:28, Lance Ortiz wrote:
> Add support to export the device description obtained from the ACPI _STR
> method, if one exists for a device, to user-space via a sysfs interface.
> This new interface provides a standard and platform neutral way for users
> to obtain the
Hi Lance,
2012/09/08 1:28, Lance Ortiz wrote:
Add support to export the device description obtained from the ACPI _STR
method, if one exists for a device, to user-space via a sysfs interface.
This new interface provides a standard and platform neutral way for users
to obtain the description
6 matches
Mail list logo