mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wolfgang Fritz <wolfgang.fritz@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: ati_remote for medion
Date: Thu, 19 Aug 2004 08:00:39 +0200	[thread overview]
Message-ID: <cg1fm7$b76$1@fritz38552.news.dfncis.de> (raw)
In-Reply-To: <1092856969.11811.12.camel@kryptonix>

Karel Demeyer wrote:
> I got a remote control with my PC ("Medion 8080 XL titanium") that works
> with an USB-receiver (via radio-waves).  As it was not supported, I
> experimented a bit and found out I could 'use' the ati-remote module in
> the 2.6.x-kernel.  I had to change some stuff like the "#define
> ATI_REMOTE_PRODUCT_ID   0x0006" and then it gave some input for some
> keys.  I also had to change the whole "Translation table from hardware
> messages to input events" which took a lot oftime for me as I had to try
> out very much as I don't know about what I had to use and the keys all
> had other hex-codes then those of the ati-remotes.
> 
> I sent my changes to Torrey Hoffman <thoffman@arnor.net> a long time ago
> and I thought he answered me he would put support for my kind of remote
> in his module, but since then nothing happened in that way.  I'm not a
> coder, so I can't give 'patches' of diffs of whatever ... I even can't
> recode the module to support both remotes ... 
> 

I sent a patch to support the Medion RC to the linux-usb-devel list in
April 04 (http://thread.gmane.org/gmane.linux.usb.devel/20928) but it
got ignored. I think the main problem is to support the different key
mappings in the driver. The easiest approach would be to expand the hard
coded key translation table for each supported RC. If that would be
acceptable, I could prepare a patch.

Is there a another way to handle remote control key mappings in the
input subsystem?

Wolfgang

> My question is: could someone please do this for me?  I spent a lot of
> time on it and I want to give back to the comunnity.  There are more
> people out there using linux who maybe already gave their remote away as
> they couldn't use it with linux.  But I use it for xmms, TVtime, Totem,
> gxine and all those other nice apps.  I don't need my name in the
> credits.  Yours should be if you code it :| ... please ? :)
> 
> friendly greeting,
> 
> Karel "scapor" Demeyer.
> 
> PS: attached is the code with changes (derivated of the ati-remote.c in
> 2.6.8.1)
> 
> 
> 
> 
[cut]



  reply	other threads:[~2004-08-19  6:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 19:22 Karel Demeyer
2004-08-19  6:00 ` Wolfgang Fritz [this message]
2004-08-19  8:28 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
2004-08-20 20:15   ` Karel Demeyer

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='cg1fm7$b76$1@fritz38552.news.dfncis.de' \
    --to=wolfgang.fritz@gmx.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®