From: Karel Demeyer <kmdemeye@vub.ac.be>
To: Tom Felker <tcfelker@mtco.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ati_remote for medion
Date: Fri, 20 Aug 2004 19:16:47 +0200 [thread overview]
Message-ID: <1093022207.2875.5.camel@kryptonix> (raw)
In-Reply-To: <200408191209.26139.tcfelker@mtco.com>
> Actually, since the codes are different, we don't need separate tables,
> because it shouldn't do any harm to have codes for the other remote in the
> same table. The remote sends a code, and we look it up in the table - as
> long as there aren't two entries in the table with the same code, there's no
> problem.
>
> Anyway, please try the attached file. I just put your codes on the bottom of
> the key table, added your vendor/product ID to the device table, tore out the
> check in probe() (as I think the system does this for us), and noted my
> changes.
>
> Hopefully the module doesn't freak out when other USB devices are plugged in
> after the module is loaded, otherwise I can fix that. And we still need to
> add some comments / help text showing that we support the medion remote, and
> maybe put your ascii art in somewhere.
>
>
> > Don't shoot me if I say anything irrevelant, and I'll stay around for
> > testing and stuff, even my evolution-filters arenot what they should be
> > - they copy it both in my Inbox and my 'Linux-kernel'-directory :|
>
> That's my fault, I've been CC:ing you, so you get mail from both me and the
> list.
Seems that the codes for the numbers are the same which is probvlematic
for me. I mapped those keys as the keys in the "numlock-area" of the
keyboard. I did it because I have a azerty-keyboard layout (be-latin1),
if I press the numbers it gives now &,é,",',(,§,... I also mapped the
numlock-button on the 'rename'-button right under the '7'-button (cfr.
ASCII-thingie in source). This way I could them use as numbers and as
Home,PgUp,PgDn,Arrows... though I mapped those on ther keys too.
I think it will need 2 different tables thus :| Maybe some other codes
are used twice now ... for other keys, I don't know as I didn't test it
alot and didn't look up in the source.
friendly greeting,
Karel "scapor" Demeyer
next prev parent reply other threads:[~2004-08-20 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 8:28 ati_remote for medion Karel Demeyer
2004-08-19 15:16 ` Tom Felker
2004-08-19 15:51 ` Karel Demeyer
2004-08-19 17:09 ` Tom Felker
2004-08-20 17:16 ` Karel Demeyer [this message]
2004-08-20 20:15 ` Karel Demeyer
-- strict thread matches above, loose matches on Subject: below --
2004-08-18 19:22 Karel Demeyer
2004-08-19 6:00 ` Wolfgang Fritz
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=1093022207.2875.5.camel@kryptonix \
--to=kmdemeye@vub.ac.be \
--cc=linux-kernel@vger.kernel.org \
--cc=tcfelker@mtco.com \
/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