From: Mario Limonciello <mario_limonciello@dell.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Alex Hung <alex.hung@canonical.com>,
Linux ACPI Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI / blacklist: blacklist Win8 OSI for Dell Inspiron 7437
Date: Wed, 20 May 2015 15:16:08 -0500 [thread overview]
Message-ID: <555CEB88.70407@dell.com> (raw)
In-Reply-To: <20150520184242.GA32453@srcf.ucam.org>
On 05/20/2015 01:42 PM, Matthew Garrett wrote:
> On Wed, May 20, 2015 at 12:42:14PM -0500, Mario Limonciello wrote:
>
>> I've gotten some more information on this.
>> Windows: Asks for battery information update multiple times.
>> Linux: Only asks once for battery information update.
>>
>> The net result is that on Linux ACPI battery is missing. In the
>> _REV test BIOS workaround, a SMI event was added to ask for battery
>> information update.
> Hm. Why does only asking once not result in us seeing the battery?
>
I'm not sure, this is all I was told about the difference in behavior
with Windows that prompted this bios workaround. Looking through the
kernel log, i'm wondering if maybe
75646e758a0ecbed5024454507d5be5b9ea9dcbf will actually have fixed this.
Alex,
What was the last kernel validated on the 7*37 family? Can you see if a
kernel that includes 75646e758a0ecbed5024454507d5be5b9ea9dcbf does
resolve it?
next prev parent reply other threads:[~2015-05-20 20:17 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
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 [this message]
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=555CEB88.70407@dell.com \
--to=mario_limonciello@dell.com \
--cc=alex.hung@canonical.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.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).