First off, I need to thank both h0leman and billytwowilly for spending some time on IRC with me that ultimitely got this to work! This will install ati_remote which is a Linux kernel module which allows use of the ATI remote as a regular input device -- no need for lirc

You can purchase this product from a number of vendors. I got mine for $39 out the door at newegg dot com.



Files Needed

ati_remote-2.1.1.tgz get it here
ati_remote.diff get it here all the way at the bottom of the page

HOWTO install

These instructions assume you have Knopmyth R4 installed.

I placed both files listed above in my /home/mythtv directory and did:

$ tar zxvf ati_remote-2.1.1.tgz
$ mv ./ati_remote.diff ./ati_remote
$ cd ati_remote
$ patch -p 0 < ati_remote.diff
show it the file's location (/home/mythtv/ati/ati_remote/ati_remote.c)
$ su
# make
# make install
# nano /etc/modules

add the following lines at the end
input
mousedev
keybdev
hid
ati_remote

REBOOT

_________________
Retired KM user (R4 - R6.04); friend to LH users.

since i have this exact remote.. i'm really intrested here.. any further instruction to get it working with myth? and the mouse controller to act like a mouse under X?

Did my HOWTO not work for you? As to the part about it working as a mouse: I tried the instructions I found (need to add it as a pointer) didn't work for me at all.

_________________
Retired KM user (R4 - R6.04); friend to LH users.

actually no i havent tried it yet.. was just ramping up to give it a run.. i'll see if i can get the pointer working as well..

I just wanted to say kudos graysky for taking the time to put this together. I'm lazy;) here's a link to the original thread in case anyone's interested:
http://mysettopbox.tv/phpBB2/viewtopic. ... highlight=

Man, is it just mine or does it seem like only 6 or 8 buttons on this thing actually work? I can jump, skip, play, and pause. Seems like there should be a way to skip around the commerical flags and control the volumn.

Anyone else?

_________________
Retired KM user (R4 - R6.04); friend to LH users.

I just used the default patch because it was easy. If you look at the source code it is actually pretty easy to figure out what to change to get other buttons doing things. Look on the mythtv mailing lists for some pointers. If you find a config that works well please post it.

Cheers,

Chris

I have an X10 PC remote, which is looks almost identical to the ATI remote wonder (in form and spec), and I've heard that the ati is basicall a rebranded X10.

Does anyone know if the gatos drivers will work with the X10?

Ta muchly,

Matt

I dunno man, looking at the source is kind of confusing. Some of it makes sence, but there are some other parts (hex maybe) that does not. I don't think I could edit that and feel confortable that it would work.

At a minimum, I'd like to see the following added to the remote:

skip to next program marker (Z and Q)
increase/decrease volume ([ and ])
increase/decrease play speed (U and J)

Anyone doing it w/ gato's drivers? What about lirc? If so, please post your /home/mythtv/lircrc

_________________
Retired KM user (R4 - R6.04); friend to LH users.

couch /home/mythtv/.mythtv/lircrc couch
couch You'd also need /etc/lircd.conf couch
couch You'd also need to recompile lirc. couch

_________________
cesman

When the source is open, the possibilities are endless!

graysky, all you do to change it is scroll down in the source until you see a bunch of hex followed by a letter, or number (depending on what the key corresponds to) and a ; followed by a little description of the key. you just change the letter or number to what you want it to be and then recompile. That's all that diff does. look through the mythtv mailing lists like I recommended and you will find a better description with examples. I'm on the crappy windows 98 lab at school right now so I can't easily untar/gzip the source and give you examples here. It really is quite easy, especially when you start with the source already diffed to something nearly acceptable.

I'm at home now. here's some example code from at_remote.c

/* keyboard.. */
{KIND_FILTERED, 0xe2, 0x1d, EV_KEY, KEY_LEFT, 1}, /* key left */
{KIND_FILTERED, 0xe4, 0x1f, EV_KEY, KEY_RIGHT, 1}, /* key right */
{KIND_FILTERED, 0xe7, 0x22, EV_KEY, KEY_DOWN, 1}, /* key down */
{KIND_FILTERED, 0xdf, 0x1a, EV_KEY, KEY_UP, 1}, /* key left */

{KIND_FILTERED, 0xe3, 0x1e, EV_KEY, KEY_ENTER, 1}, /* key enter */

{KIND_FILTERED, 0xd2, 0x0d, EV_KEY, KEY_1, 1},
{KIND_FILTERED, 0xd3, 0x0e, EV_KEY, KEY_2, 1},
{KIND_FILTERED, 0xd4, 0x0f, EV_KEY, KEY_3, 1},
{KIND_FILTERED, 0xd5, 0x10, EV_KEY, KEY_4, 1},
{KIND_FILTERED, 0xd6, 0x11, EV_KEY, KEY_5, 1},
{KIND_FILTERED, 0xd7, 0x12, EV_KEY, KEY_6, 1},
{KIND_FILTERED, 0xd8, 0x13, EV_KEY, KEY_7, 1},


see where it says KEY_7, KEY_UP, etc? all you do is edit it to say KEY_WHATEVERYOUWANTITTOBE. ie change key_6 to key_R would make the number 6 send R as its signal

in your case you just look through the code and find the keys you want to change then change them to KEY_Z, KEY_Q, etc, etc. increasing volume won't necessarily work because you are probably running the volume through your tv. if you have your tv speakers at full volume and adjust the computer's output sound signal, then you will likely get very distorted sound.

When R4V2 is released the remote will be detected! The module will load on boot! Unfortunately it doesn't load the modules needed before it, so I wrote a quick script.

add_ati_remote

The remote isn't detected on the USB bus, so there is no way to automate this...
Maybe if I have time next week, I'll work on a patch that make the remote more functional! THANKS Jesse!

_________________
cesman

When the source is open, the possibilities are endless!

Cesman,

I am shortly going to load an R4V2 but like u said, if we are running good we may skip for now.

Anyways, I do want to add my RemoteWonder - and was wondering with my current build - .14 all good, can u pass us any data on a good keyboard map file as discussed in this thread or do we still need to self create.

Just curious if we could access any of this without a full up to v4r2

This is a killer thread, great work, and just was wondering if some of the keys had been completed on the remote

Thanks

I guess the things I am kinda concerned/confused about are:

1) Is my USB support enabled (how would I verify)?

2) Proper editing of the modules.conf file .... still novice here?

3) Do I need to rid of anything from the Hauppauge remotes prior?

I think I am close - just those pieces.

Thanks very much for any help