public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Clifton <pcjc2@cam.ac.uk>
To: emisca <emisca.ml@gmail.com>
Cc: xorg@lists.freedesktop.org, linux-acpi@vger.kernel.org
Subject: RE: i810, mergedfb and lid switch and acpi video
Date: Wed, 17 Jan 2007 14:23:39 +0000	[thread overview]
Message-ID: <1169043819.6273.10.camel@localhost> (raw)
In-Reply-To: <1C601A6A3344064EB423D0C1E83B717BE6FD77@pdsmsx411.ccr.corp.intel.com>

SORRY - sent back to Luming by mistake - meant to send to all.

On Wed, 2007-01-17 at 12:20 +0800, Yu, Luming wrote:

> But there is NO _BQC. Instead of _BQC, there do have a _BCQ in DSDT.
> Is this a bug of BIOS? Acpi video drvier needs _BQC to get the
> current brightness level, and to get the next level to set on
receiving
> notification of 0x86 (Increase Brightness) , 0x87 (decrease
Brightness).

I can ACK that my HP had a similar typo / feature with its intel based
video:

00:02.0 VGA compatible controller: Intel Corporation Mobile 
945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)

The _BQC is absent, but a strange _BCQ is there - which looks to give
the correct functionality.

The ONLY place I can find any reference to _BCQ is in a couple of
Windows Vista design documents about making display brightness work with
Vista.

Thank you Microsoft, for that typo - presuming thats what it is!

Peter Clifton



  reply	other threads:[~2007-01-17 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <414cba4e0701150039j27d5ffcaw78e31e4119779872@mail.gmail.com>
2007-01-17  4:20 ` i810, mergedfb and lid switch and acpi video Yu, Luming
2007-01-17 14:23   ` Peter Clifton [this message]
2007-01-17 15:08     ` emisca
     [not found] <200701120312.53809.lenb@kernel.org>
2007-01-15  6:01 ` Yu, Luming
2007-01-11 20:07 emisca

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=1169043819.6273.10.camel@localhost \
    --to=pcjc2@cam.ac.uk \
    --cc=emisca.ml@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=xorg@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox