public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: what about the sony_acpi driver?
Date: Mon, 6 Jun 2005 18:27:07 +0200	[thread overview]
Message-ID: <20050606162707.GB8555@message-id.s3e.de> (raw)
In-Reply-To: <20050606152829.GA5067-qYCAlGQNbcFrdx17CPfAsdBPR1lH4CV8@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

On Mon, Jun 06, 2005 at 11:28:29PM +0800, Yu, Luming wrote:

> I admit the so-called generic-acpi-hotkey-driver is hard to use. :-(
> And I'm trying to make it easy to use. 

Ok, i will try it out on a hotkey-enabled machine (asus)

> Please try tool: acpidm. And send it to me unless you got zero.

attached

> > yes, but those specific drivers work. Today. And they do even more than
> > hotkeys (which are non-existent on this machine), e.g. adjusting LCD backlight
> > or switching the ASUS custom LEDs.
> Believe me, generic-hotkey-driver and acpi-video-driver can handle these, if this is a acpi system.

Ok. I tried the video driver and got lots of (mostly irritating) information,
could not do anything with it. After compiling and insmod'ing sony_acpi, i
could immediately adjust my brightness ;-)

I am willing to try out all kinds of stuff.
-- 
Stefan Seyfried

[-- Attachment #2: acpidmp.gz --]
[-- Type: application/x-gunzip, Size: 22797 bytes --]

  parent reply	other threads:[~2005-06-06 16:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06 11:09 what about the sony_acpi driver? Stefan Seyfried
     [not found] ` <20050606110952.GA9447-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2005-06-06 13:29   ` Yu, Luming
     [not found]     ` <20050606132911.GA4633-qYCAlGQNbcFrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2005-06-06 15:12       ` Stefan Seyfried
     [not found]         ` <20050606151235.GA28528-l0tNAEGuAhiXoBlonBaIS7NAH6kLmebB@public.gmane.org>
2005-06-06 15:28           ` Yu, Luming
     [not found]             ` <20050606152829.GA5067-qYCAlGQNbcFrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2005-06-06 15:55               ` Matthew Garrett
2005-06-06 16:19                 ` Yu, Luming
     [not found]                   ` <20050606161931.GC5067-qYCAlGQNbcFrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2005-06-07 14:08                     ` Bruno Ducrot
     [not found]                       ` <20050607140838.GM8899-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-06-09  7:03                         ` Yu, Luming
2005-06-06 16:27               ` Stefan Seyfried [this message]
     [not found]                 ` <20050606162707.GB8555-l0tNAEGuAhiXoBlonBaIS7NAH6kLmebB@public.gmane.org>
2005-06-06 18:59                   ` Herman Sheremetyev
2005-06-07  8:01                   ` Yu, Luming
     [not found]                     ` <20050607080111.GA3622-qYCAlGQNbcFrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2005-06-07  9:16                       ` Stefan Seyfried

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=20050606162707.GB8555@message-id.s3e.de \
    --to=seife-t+3qhdtrtvdv8lqoku5mv4hbzq1bdw0s@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@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