From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Hiroshi Miura <miura-yiisDzvROlQdnm+yROfE0A@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: generic hotkey driver
Date: Tue, 14 Sep 2004 22:42:07 +0200 [thread overview]
Message-ID: <20040914204207.GA12726@elf.ucw.cz> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84056B57EE@pdsmsx403>
Hi!
> >I think hotkey drivers are so differ that it is enough to decide
> >event format. ie) 'ibm KEY 00001 00001' or 'hotkey/pcc HKEY
> >000003 000001'
> >
>
> We don't need to care about the format of event. Since it is
> configurable,
> we just need to understand the internal meaning. So maybe we
> need to define the internal event number, which stands for a
> special purpose. such as:
>
> 001 turn off display
> 002 inc brightness
> 003 dec brightness
> 004 s3
> ......
>
If those are keys, you should just treat them as keys... That is hook
it into input subsystem.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
next prev parent reply other threads:[~2004-09-14 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 8:14 generic hotkey driver Yu, Luming
2004-09-07 8:49 ` Karol Kozimor
2004-09-14 20:42 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-08 15:42 Yu, Luming
2004-09-07 7:54 Yu, Luming
2004-09-07 13:13 ` John Belmonte
2004-09-01 10:32 Yu, Luming
2004-09-03 11:16 ` Hiroshi Miura
2004-09-04 8:45 ` John Belmonte
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=20040914204207.GA12726@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=miura-yiisDzvROlQdnm+yROfE0A@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