From: joeyli <jlee@suse.com>
To: Samuel Sieb <samuel@sieb.net>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: Acer ES1-522 wifi blocked and Fn keys don't work (WMI)
Date: Wed, 8 Feb 2017 11:34:38 +0800 [thread overview]
Message-ID: <20170208033438.GN15025@linux-l9pv.suse> (raw)
In-Reply-To: <2203db7c-4b11-9766-2b97-a7adf3bda7bd@sieb.net>
Hi Samuel,
On Tue, Jan 31, 2017 at 02:07:23PM -0800, Samuel Sieb wrote:
> On 01/23/2017 07:48 PM, joeyli wrote:
> >Could you please create two bugs on https://bugzilla.kernel.org/ ? One for
> >function key, another one for accelerometer. I prefer to collect debug
> >messages/files on bugzilla for reference in the future. Please send bug
> >number to me after you created it.
> >
> >On the other hand, please attach your acpidump result on bugzilla:
> > # acpidump > acpidump.raw
> >
> >I want to check the DSDT table for more detail.
> >
> Sorry for the delay. I don't have physical access to the laptop right now,
> so I had to wait for someone to make it remotely available.
>
Thanks for your help to create bugs. I added comments on bugzilla.
> Wifi hard block: https://bugzilla.kernel.org/show_bug.cgi?id=193751
For this issue, please try Chris Chiu's patch:
acer-wmi: Inform firmware that RF Button Driver is active
> accelerometer: https://bugzilla.kernel.org/show_bug.cgi?id=193761
>
For this one, please try this patch that it's merged to testing branch:
platform/x86: acer-wmi: setup accelerometer when machine has appropriate notify event
> I will create another one for the function keys when I am on-site again, but
> that won't be for at least a month.
Thanks
Joey Lee
prev parent reply other threads:[~2017-02-08 3:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 20:05 Acer ES1-522 wifi blocked and Fn keys don't work (WMI) Samuel Sieb
2017-01-22 14:36 ` joeyli
2017-01-23 23:23 ` Samuel Sieb
2017-01-24 3:48 ` joeyli
2017-01-24 3:51 ` joeyli
2017-01-24 4:41 ` Samuel Sieb
2017-01-31 22:07 ` Samuel Sieb
2017-02-08 3:34 ` joeyli [this message]
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=20170208033438.GN15025@linux-l9pv.suse \
--to=jlee@suse.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=samuel@sieb.net \
/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