From: Alex Hung <alex.hung@canonical.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Linux ACPI Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI / blacklist: blacklist Win8 OSI for Dell Inspiron 7437
Date: Mon, 27 Apr 2015 16:30:11 +0800 [thread overview]
Message-ID: <CAJ=jquYe97ObpE=3eTij705QsopnH4+hChssdj0qu7YFHGsSXg@mail.gmail.com> (raw)
In-Reply-To: <20150424082115.GA3783@srcf.ucam.org>
I don't have any Win8 media to test it but I will try to look for one.
I recalled that kernel 4.1rc has a patch "ACPICA: Permanently set _REV
to the value '2'" that may also change firmware's behaviours, but it
does not fix Inspiron 7437's ACPI event just for references.
On Fri, Apr 24, 2015 at 4:21 PM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Thu, Apr 23, 2015 at 11:24:35AM +0800, Alex Hung wrote:
>> Dell Inspiron 7437's ACPI events does not work well with Win8 OSI.
>> Disabling Win8 OSI can fix wireless hotkey and ACPI battery.
>
> Does this machine work if you actually install Windows 8 on it?
> --
> Matthew Garrett | mjg59@srcf.ucam.org
--
Cheers,
Alex Hung
next prev parent reply other threads:[~2015-04-27 8:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 3:24 [PATCH] ACPI / blacklist: blacklist Win8 OSI for Dell Inspiron 7437 Alex Hung
2015-04-24 8:21 ` Matthew Garrett
2015-04-27 8:30 ` Alex Hung [this message]
2015-04-27 17:46 ` Matthew Garrett
2015-04-28 4:53 ` Alex Hung
2015-04-28 5:24 ` Matthew Garrett
2015-04-28 9:51 ` Alex Hung
2015-04-28 17:11 ` Matthew Garrett
2015-04-29 10:09 ` Alex Hung
2015-05-14 19:02 ` Mario Limonciello
2015-05-14 19:13 ` Matthew Garrett
2015-05-14 19:17 ` Mario Limonciello
2015-05-20 17:42 ` Mario Limonciello
2015-05-20 18:42 ` Matthew Garrett
2015-05-20 20:16 ` Mario Limonciello
2015-06-02 3:20 ` Alex Hung
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='CAJ=jquYe97ObpE=3eTij705QsopnH4+hChssdj0qu7YFHGsSXg@mail.gmail.com' \
--to=alex.hung@canonical.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@rjwysocki.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;
as well as URLs for NNTP newsgroup(s).