public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Stephan Krings <stephan-MC3rjLPHZ0jJ0Y7HFzmx4Q@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Compaq evo n800v
Date: Wed, 12 Mar 2003 14:12:57 +0100	[thread overview]
Message-ID: <20030312131257.GA1636@hell.org.pl> (raw)
In-Reply-To: <15981.52449.352495.551945-i6UgHu6VvmYwLeuMs8dnSMnRjscXObHh@public.gmane.org>

Thus wrote Stephan Krings:
> > I don't know how about the Evo, but on Asus those keys generate ACPI
> > events, yet there are methods in DSDT for handling those events and they
> > work irregardless to external conditions.
> Just out of curiousity: How are these methods called or do these
> methods comply with the VGA extensions, which are described in the
> ACPI spec?

No, they do not. These are internal \_SB.PCI0.PX40.ECD0._Q0E and
\_SB.PCI0.PX40.ECD0._Q0F to increase and decrease brightness (these are 
mapped to the hotkeys in the DSDT), and GPLV and SPLV to get and set it 
directly, probably designed for ospm (which I use in the driver).

> > Search your DSDT for such methods.
> Already did so: And none of the methods get hit when toggling the
> display brightness. Which is pity, because that would have made it
> possible to write a module like the one for Toshiba notebooks to alter
> display parameters programmatically.

Well, these might not be obvious to spot. Cross-referencing and indexing
help a lot in that. Check for IndexFields with interesting names, perhaps
you'll find something anyway.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

      parent reply	other threads:[~2003-03-12 13:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-08 12:07 Compaq evo n800v Anders Persson
     [not found] ` <1047125223.5077.28.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-03-08 19:59   ` Daniele Boffi
2003-03-10  9:19   ` Stephan Krings
     [not found]     ` <15980.22695.764082.140067-/D6BEnooUbBSBwh6+m2SNzw7hsPlABbXrfATN7qnIZ4@public.gmane.org>
2003-03-10 10:08       ` Karol Kozimor
     [not found]         ` <20030310100824.GB32516-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-03-10 20:37           ` Stephan Krings
     [not found]             ` <15980.63370.956274.280152-/D6BEnooUbBSBwh6+m2SNzw7hsPlABbXrfATN7qnIZ4@public.gmane.org>
2003-03-10 20:45               ` Karol Kozimor
     [not found]                 ` <15981.52449.352495.551945@stephan.convergence.de>
     [not found]                   ` <15981.52449.352495.551945-i6UgHu6VvmYwLeuMs8dnSMnRjscXObHh@public.gmane.org>
2003-03-12 13:12                     ` Karol Kozimor [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=20030312131257.GA1636@hell.org.pl \
    --to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=stephan-MC3rjLPHZ0jJ0Y7HFzmx4Q@public.gmane.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