Re: ati_remote for medion

[Tom Felker <tcfelker@mtco.com>]

On Thursday 19 August 2004 03:28 am, Karel Demeyer wrote:
> > 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
>
> I'm not sure if my key-mappings are the best, but for my use they are
> excellent.  I added a 'Ctrl', 'Alt', 'Tab', 'Esc' and some more keys.
> The 'fullscreen'-button acts as a 'f', as it makes Totem, TVtime, gXine
> etc go fullscreen ...
>
> I don't know how, but if I still could help in any way, make it clear
> how :)
>
> friendly greets,
>
> Karel "scapor" Demeyer

Are the keycodes unique enough that you can just put the keymaps for both 
remotes into the same table?  I.E. when you wrote your keymaps, did you have 
to remove some of the others to get it to work, or was that just for 
cleanliness?  Otherwise, we'd need to have multiple tables and choose which 
to use based on which remote is being used.

Oh, and do stick around, Karel, someone will need to test the result.

BTW, does anyone know whether the probe function actually needs to check 
whether the product and vendor IDs match the device?  I've seen docs that 
imply yes, but many drivers don't check, and I feel stupid iterating thru the 
table if no.

Have fun,

-- 
Tom Felker, <tcfelker@mtco.com>
<http://vlevel.sourceforge.net> - Stop fiddling with the volume knob.

If nature has made any one thing less susceptible than all others of exclusive 
property, it is the action of the thinking power called an idea.