On Monday, May 05, 2014 11:38:09 AM Hans de Goede wrote:
> Without this this EEE PC exports a non working WMI interface, with this it
> exports a working "good old" eeepc_laptop interface, fixing brightness control
> not working as well as rfkill being stuck in a permanent wireless blocked
> state.
>
> This is not an ideal way to fix this, but various attempts to fix this
> otherwise have failed, see:
> https://bugzilla.redhat.com/show_bug.cgi?id=1067181
>
> Cc: [email protected]
> Reported-and-tested-by: [email protected]
> Signed-off-by: Hans de Goede <[email protected]>
Queued up for 3.15 and -stable, thanks!
> ---
> drivers/acpi/blacklist.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/acpi/blacklist.c b/drivers/acpi/blacklist.c
> index 51b8f64..b08e65a 100644
> --- a/drivers/acpi/blacklist.c
> +++ b/drivers/acpi/blacklist.c
> @@ -299,6 +299,19 @@ static struct dmi_system_id acpi_osi_dmi_table[]
> __initdata = {
> DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad T500"),
> },
> },
> + /*
> + * Without this this EEEpc exports a non working WMI interface, with
> + * this it exports a working "good old" eeepc_laptop interface, fixing
> + * both brightness control, and rfkill not working.
> + */
> + {
> + .callback = dmi_enable_osi_linux,
> + .ident = "Asus EEE PC 1015PX",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK Computer INC."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "1015PX"),
> + },
> + },
> {}
> };
>
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
