All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Aaron Lu <aaron.lwe@gmail.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	Len Brown <lenb@kernel.org>, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH] acpi: video: improve quirk check
Date: Mon, 5 Aug 2013 09:41:04 -0500	[thread overview]
Message-ID: <CAMP44s0+d2ffXC-k8+kxQ4XCfF8M_VSBZ02M5seDSj99oPkXZw@mail.gmail.com> (raw)
In-Reply-To: <23723258.099Re4s3PJ@vostro.rjw.lan>

On Mon, Aug 5, 2013 at 9:04 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:

>> In my machine I think the issue is slightly different, I think _BCM is
>> failing, at least until enabling the _DOS thing, but at the end of the
>> day it's the same thing for the check; _BQC is always returning the
>> same value, and the code above will find that out, regardless of which
>> values are tested.
>>
>> For my particular machine though, I think it's more interesting to
>> find out why _BCM is failing before _DOS, and why efaa14c made it
>> work. If that is actually the case.
>
> That depends on how the BIOS+platform is designed and that may change from
> one system to another quite a bit.

Maybe, but it seems there's at least another ASUS machine with the
same behavior, and it seems a lot of ASUS machines behave very
similarly.

> The only common denominator is what Windows expects (and that unfortunately
> depends on the version of Windows too), because that's the functionality
> which is likely to have been tested.  Anything else is likely to be untested
> and therefore most probably buggy.

Maybe, or maybe we are doing something wrong.

It's worth to try to find that out.

-- 
Felipe Contreras

  reply	other threads:[~2013-08-05 14:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 19:37 [PATCH] acpi: video: improve quirk check Felipe Contreras
2013-08-02 23:47 ` Rafael J. Wysocki
2013-08-03  1:04   ` Felipe Contreras
2013-08-03  1:16     ` Rafael J. Wysocki
2013-08-03  1:07       ` Felipe Contreras
2013-08-03  1:19         ` Rafael J. Wysocki
2013-08-03  1:30           ` Felipe Contreras
2013-08-03  8:14   ` Aaron Lu
2013-08-03 11:34     ` Rafael J. Wysocki
2013-08-03 20:24       ` Felipe Contreras
2013-08-03 21:40         ` Rafael J. Wysocki
2013-08-03 22:20           ` Felipe Contreras
2013-08-03 22:38             ` Rafael J. Wysocki
2013-08-03 22:37               ` Felipe Contreras
2013-08-04  1:47             ` Aaron Lu
2013-08-04  6:54               ` Felipe Contreras
2013-08-04 14:14                 ` Rafael J. Wysocki
2013-08-04 14:08                   ` Felipe Contreras
2013-08-04  1:18       ` Aaron Lu
2013-08-04  6:42         ` Felipe Contreras
2013-08-04 14:19           ` Rafael J. Wysocki
2013-08-04 14:19             ` Felipe Contreras
2013-08-05 14:04               ` Rafael J. Wysocki
2013-08-05 14:41                 ` Felipe Contreras [this message]
2013-08-07  4:35               ` Aaron Lu

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=CAMP44s0+d2ffXC-k8+kxQ4XCfF8M_VSBZ02M5seDSj99oPkXZw@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=aaron.lwe@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=rui.zhang@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.