All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <matthew.garrett@nebula.com>
To: "crmafra@gmail.com" <crmafra@gmail.com>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"andreas.noever@gmail.com" <andreas.noever@gmail.com>,
	"crmafra2@gmail.com" <crmafra2@gmail.com>,
	"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>
Subject: Re: Bisected regression from 3.17 still present in 3.19-rc1
Date: Tue, 30 Dec 2014 11:36:53 +0000	[thread overview]
Message-ID: <1419939412.25226.2.camel@nebula.com> (raw)
In-Reply-To: <20141230101624.GA5339@linux-g29b.site>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 579 bytes --]

On Tue, 2014-12-30 at 10:16 +0000, Carlos R. Mafra wrote:
> On Tue, 30 Dec 2014 at  1:28:21 +0000, Matthew Garrett wrote:
> > What is CONFIG_ACPI_SBS set to?
> 
> CONFIG_ACPI_SBS is not set

There's your problem. The Darwin call results in the firmware exposing
the battery via SBS, not as an ACPI control method battery. Enable
CONFIG_ACPI_SBS and you should be good.

-- 
Matthew Garrett <matthew.garrett@nebula.com>
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2014-12-30 11:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-28 18:54 Bisected regression from 3.17 still present in 3.19-rc1 Carlos R. Mafra
2014-12-29 21:49 ` Rafael J. Wysocki
2014-12-29 21:57   ` Carlos R. Mafra
2014-12-29 22:20     ` Andreas Noever
2014-12-29 22:53       ` Carlos R. Mafra
2014-12-30  1:28 ` Matthew Garrett
2014-12-30 10:16   ` Carlos R. Mafra
2014-12-30 11:36     ` Matthew Garrett [this message]
2014-12-30 15:18       ` Carlos R. Mafra
2015-01-01 20:40       ` Andreas Mohr

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=1419939412.25226.2.camel@nebula.com \
    --to=matthew.garrett@nebula.com \
    --cc=andreas.noever@gmail.com \
    --cc=crmafra2@gmail.com \
    --cc=crmafra@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=torvalds@linux-foundation.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 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.