linux-acpi.vger.kernel.org archive mirror
 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: Re: [PATCH] ACPI / blacklist: blacklist Win8 OSI for Dell Inspiron 7437
Date: Thu, 14 May 2015 20:13:59 +0100	[thread overview]
Message-ID: <20150514191358.GB23853@srcf.ucam.org> (raw)
In-Reply-To: <5554F12A.3010003@dell.com>

On Thu, May 14, 2015 at 02:02:02PM -0500, Mario Limonciello wrote:

> * Battery information was not displayed in the OS.  The BIOS team
> found that the Linux wasn't asking for battery information in the OS
> in the same way that Windows does.  The delta path creates a SMI
> event to get battery information.

Huh. Is there any chance we can find out what the difference is so we 
can make them equivalent?

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

  reply	other threads:[~2015-05-14 19:14 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 [this message]
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=20150514191358.GB23853@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 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).