From: Dmitry Tunin <hanipouspilot@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Aaron Lu <aaron.lu@intel.com>
Subject: Re: [PATCH v3 1/2] acpi: Add "acpi_osi=" for ASUS X200MA to enable, brightness keys
Date: Thu, 18 Dec 2014 17:40:19 +0300 [thread overview]
Message-ID: <5492E753.7090505@gmail.com> (raw)
In-Reply-To: <20141218143623.GA7335@srcf.ucam.org>
But at least two devices work well with this quirk.
That must be some ASUS UEFI firmware fault, but still it is a workaround.
You can find some more information in those bugzilla reports.
https://bugzilla.kernel.org/show_bug.cgi?id=89401
https://bugzilla.kernel.org/show_bug.cgi?id=70241
18.12.2014 17:36, Matthew Garrett пишет:
> That's odd - it looks like the default behaviour in the absence of any
> OSI strings is to just default to an OSYS value that matches Windows
> 2012, so disabling the 2013 value should be equivalent. If it's not,
> it's definitely not safe to turn off all values - there are several
> devices that change behaviour as a result.
>
next prev parent reply other threads:[~2014-12-18 14:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 12:16 [PATCH v3 1/2] acpi: Add "acpi_osi=" for ASUS X200MA to enable, brightness keys Dmitry Tunin
2014-12-18 12:19 ` [PATCH 2/2] acpi: Add "acpi_osi=" for ASUS UX302LA " Dmitry Tunin
2014-12-18 13:25 ` [PATCH v3 1/2] acpi: Add "acpi_osi=" for ASUS X200MA " Josh Boyer
2014-12-18 13:27 ` Matthew Garrett
2014-12-18 13:28 ` Dmitry Tunin
2014-12-18 13:40 ` Dmitry Tunin
2014-12-18 13:57 ` Matthew Garrett
2014-12-18 14:03 ` Dmitry Tunin
2014-12-18 14:04 ` Dmitry Tunin
2014-12-18 14:09 ` Matthew Garrett
2014-12-18 14:22 ` Dmitry Tunin
2014-12-18 14:26 ` Matthew Garrett
2014-12-18 14:34 ` Dmitry Tunin
2014-12-18 14:36 ` Matthew Garrett
2014-12-18 14:40 ` Dmitry Tunin [this message]
2014-12-18 14:43 ` Matthew Garrett
2014-12-18 14:50 ` Matthew Garrett
2014-12-18 18:09 ` Len Brown
2014-12-18 18:20 ` Dmitry Tunin
2014-12-18 20:04 ` Matthew Garrett
2014-12-18 21:20 ` Dmitry Tunin
2014-12-18 14:06 ` Dmitry Tunin
2014-12-19 1:46 ` Aaron Lu
2014-12-19 3:23 ` Aaron Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5492E753.7090505@gmail.com \
--to=hanipouspilot@gmail.com \
--cc=aaron.lu@intel.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).