From: Jonathan Nieder <jrnieder@gmail.com>
To: Alex Hung <alex.hung@canonical.com>
Cc: corentincj@iksaif.net, mjg@redhat.com,
acpi4asus-user@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] asus-wmi: use ASUS_WMI_METHODID_DSTS2 as default DSTS ID.
Date: Tue, 26 Jun 2012 16:39:58 -0500 [thread overview]
Message-ID: <20120626213958.GA17871@burratino> (raw)
In-Reply-To: <1340164055-1062-1-git-send-email-alex.hung@canonical.com>
Hi Alex,
Alex Hung wrote:
> According to responses from the BIOS team, ASUS_WMI_METHODID_DSTS2
> (0x53545344) will be used as future DSTS ID. In addition, calling
> asus_wmi_evaluate_method(ASUS_WMI_METHODID_DSTS2, 0, 0, NULL) returns
> ASUS_WMI_UNSUPPORTED_METHOD in new ASUS laptop PCs. This patch fixes
> no DSTS ID will be assigned in this case.
Tested-by: Carsten Otto <otto@informatik.rwth-aachen.de> # 3.2.21, Asus UX31A
More precisely, Carsten was unable to use asus_wmi, getting the
following message from a distro kernel based on 3.4.1 and from
unpatched 3.2.21:[1]
| asus_wmi: Can't find DSTS
After applying the patch described above to 3.2.21, multimedia keys
work.
| The patch works, dmesg before and after are attached.
|
| With the patched kernel I can (at least) change the volume using the
| Fn keys, gnome shows some audio related icons and a changing (volume)
| bar. I did not try further than that (yet).
This is on an Asus Zenbook Prime (UX31A). acpidump, logs, and other
info are at [1]. Could you remind me when this hits mainline so we
can make sure it gets applied to earlier kernels, for example by
adding "Cc: stable@vger.kernel.org" to the commit message?
Thanks and hope that helps,
Jonathan
[1] http://bugs.debian.org/679158
next prev parent reply other threads:[~2012-06-26 21:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 3:47 Alex Hung
2012-06-20 3:50 ` Alex Hung
2012-06-26 21:39 ` Jonathan Nieder [this message]
2012-06-26 21:58 ` Carsten Otto
2012-06-27 7:53 ` Alex Hung
2012-06-27 22:17 ` Jonathan Nieder
2012-06-28 8:18 ` Carsten Otto
2012-09-18 10:21 ` Carsten Otto
2012-09-18 20:54 ` Corentin Chary
2012-06-29 12:21 ` Corentin Chary
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=20120626213958.GA17871@burratino \
--to=jrnieder@gmail.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=alex.hung@canonical.com \
--cc=corentincj@iksaif.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@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
Powered by JetHome