public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Jacek Blizinski <azidog-SDTLKeebBdLQT0dZR+AlfA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Please Help!
Date: Tue, 13 Jan 2004 08:57:31 +0100	[thread overview]
Message-ID: <20040113075731.GA8923@hell.org.pl> (raw)
In-Reply-To: <200401121952.35240.azidog-SDTLKeebBdLQT0dZR+AlfA@public.gmane.org>

Thus wrote Jacek Blizinski:
> I've tried to find guides online but have come up with anything. Any help 
> would be greatly appreciated as this is a crucial feature for me and many 
> others. Thank you in advance for your time.

The way ASUS does it is to only send notifies to a specific device (HOTK 
/ ATKD) once the system is in ACPI mode. Those notifies are then passed to
userspace by the driver. Although I don't see any specific notifies (except
the one that probably has to do with display output switching) in your
DSDT, you may try calling acpi_bus_register_driver() anyway. Another option
yould be to enable some debug to determine what methods are called upon the
keypress.
Best regards,

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


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html

  parent reply	other threads:[~2004-01-13  7:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  0:52 Please Help! Jacek Blizinski
     [not found] ` <200401121952.35240.azidog-SDTLKeebBdLQT0dZR+AlfA@public.gmane.org>
2004-01-13  7:57   ` Karol Kozimor [this message]
2004-01-15 12:25   ` subjects [was Re: Please Help!] Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-01-13  2:46 Please Help! Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720CBD-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-13  4:11   ` Jacek Blizinski
2004-01-13  6:59   ` Nate Lawson
     [not found]     ` <20040112225811.B59750-Y6VGUYTwhu0@public.gmane.org>
2004-01-13  7:35       ` Jacek Blizinski
2004-01-13  7:39       ` Jacek Blizinski

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=20040113075731.GA8923@hell.org.pl \
    --to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=azidog-SDTLKeebBdLQT0dZR+AlfA@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