All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Mario Limonciello <mario_limonciello@dell.com>
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 19:42:42 +0100	[thread overview]
Message-ID: <20150520184242.GA32453@srcf.ucam.org> (raw)
In-Reply-To: <555CC776.3030802@dell.com>

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?

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2015-05-20 18:42 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 [this message]
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=20150520184242.GA32453@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=alex.hung@canonical.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mario_limonciello@dell.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.