From: Robert Hancock <hancockrwd@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Lan Tianyu <tianyu.lan@intel.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, fcr@adinet.com.uy, l@dorileo.org
Subject: Re: [PATCH V2] ACPI/Battery: Add a _BIX quirk for NEC LZ750/LS
Date: Wed, 15 Jan 2014 00:17:56 -0600 [thread overview]
Message-ID: <52D62814.2000401@gmail.com> (raw)
In-Reply-To: <5255063.SeYbBZqxVQ@vostro.rjw.lan>
On 01/14/2014 03:37 PM, Rafael J. Wysocki wrote:
> On Tuesday, January 14, 2014 04:06:01 PM Matthew Garrett wrote:
>> On Mon, Jan 06, 2014 at 11:25:53PM +0100, Rafael J. Wysocki wrote:
>>
>>> Queued up as a fix for 3.13 (I fixed up the indentation).
>>
>> Ah, sorry, I missed this chunk of the thread. If the system provides
>> valid _BIF data then we should possibly just fall back to that rather
>> than adding another quirk table.
>
> The problem is to know that _BIX is broken. If we could figure that out
> upfront, we woulnd't need the quirk table in any case.
>
> Tianyu, can we do some effort during the driver initialization to detect
> this breakage and handle it without blacklisting systems?
Yes, the usual question in such cases is "how does Windows manage to
function on such systems, (almost certainly) without a system-specific
hack, and can we replicate that behavior?"
prev parent reply other threads:[~2014-01-15 6:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 14:50 [PATCH V2] ACPI/Battery: Add a _BIX quirk for NEC LZ750/LS Lan Tianyu
2014-01-06 17:59 ` Dmitry Torokhov
2014-01-06 22:25 ` Rafael J. Wysocki
2014-01-14 16:06 ` Matthew Garrett
2014-01-14 21:37 ` Rafael J. Wysocki
2014-01-14 21:24 ` Matthew Garrett
2014-01-14 22:17 ` Rafael J. Wysocki
2014-01-15 14:42 ` Lan Tianyu
2014-01-15 14:47 ` Matthew Garrett
2014-01-15 15:06 ` Lan Tianyu
2014-01-15 16:48 ` Moore, Robert
2014-01-15 16:48 ` Moore, Robert
2014-01-15 6:17 ` Robert Hancock [this message]
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=52D62814.2000401@gmail.com \
--to=hancockrwd@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=fcr@adinet.com.uy \
--cc=l@dorileo.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@rjwysocki.net \
--cc=tianyu.lan@intel.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.