LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Blogs > Caysho
User Name
Password

Notices



Rate this Entry

AverTV DVB-T 777 and the remote

Posted 08-24-2007 at 06:39 AM by Caysho

I started to look at what is needed to get the remote working.

This indicates patching is possible, but there's a note about support being in more recent kernels.
http://www.linuxtv.org/wiki/index.php/AVerMedia_AVerTV_DVB-T_777_%28A16AR%29#Remote_control

The board is referenced as SAA7134_BOARD_AVERMEDIA_777 in the saa7134 source; SAA7134_BOARD_AVERMEDIA_A16AR is also mentioned, and seems to be the chipset reference - I've seen it in the win32 inf, so the 777 may simply be a derivative (?).
Searching on this finds a couple of things ...

This contains a reference to linux-2.6.19-rc6:
http://72.14.253.104/search?q=cache:9V0IrHWc38IJ:crypto.riken.go.jp/archives/linux/kernel.org/kernel/people/agk/patches/2.6/2.6.19/patch-2.6.19-rc5-rc6+%22mask_keycode+%3D+0x02F200%22&hl=en&ct=clnk&cd=4&gl=au&client=firefox-a
I'm guessing this is when support first got into the kernel.

This contains the same information, but a bit cleaner:
http://grmso.net:8090/blob/1b6dfd801cc1f6e9d0c3c95571b0eaf4974bf3b7/

This indicates there are values that need to be passed to lirc_gpio
http://osdir.com/ml/hardware.lirc/2004-04/msg00181.html
but I'm not clear on what they all are, or how to get them.

KnoppMyth R5F1 uses kernel 2.6.18-chw-13, so I'll either have to do some hacking, or get a more recent MythTV distro to use the remote right now.

One interesting bit of info is what
Code:
cat /proc/bus/input/devices
returns:
Code:
I: Bus=0001 Vendor=1461 Product=2c05 Version=0001
N: Name="saa7134 IR (AverTV DVB-T 777)"
P: Phys=pci-0000:00:0c.0/ir0
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=100003
B: KEY=40fc310 82140000 0 0 0 0 2048000 180 4001 9e0000 0 0 ffc

I: Bus=0001 Vendor=1461 Product=2c05 Version=0001
N: Name="saa7134 IR (AverTV DVB-T 777)"
P: Phys=pci-0000:00:0d.0/ir0
S: Sysfs=/class/input/input3
H: Handlers=kbd event3
B: EV=100003
B: KEY=40fc310 82140000 0 0 0 0 2048000 180 4001 9e0000 0 0 ffc
I gather this can be used in xorg, but I wonder if remote buttons can be mapped to different functions depending on which application is used ? I gather lirc can do this.

Some progress:
Code:
Section "ServerLayout"
   ...
   InputDevice    "Remote" "AlwaysCore
   ...
EndSection
 
Section "InputDevice"
    Identifier "AverTV DVB-T 777 Remote"
    Driver "kbd"
    # http://people.debian.org/~terpstra/attach/4@20070802.030346.6a45d794.attach
    # this link contains a reference to an additional keyboard using the Phys ID from 
    # cat /proc/bus/input/devices
    Option "Phys"	"pci-0000:00:0c.0/ir0"
end section
This gets the remote recognised as an additional keyboard.
Using Driver "evdev" also works, but there was no difference with respect to the keycodes returned.

I then played with xev to get the keycodes, and some didn't do anything. There are references to the syslog containing information about the key presses, but I didn't see anything.
showkey -k gives the raw data recieved.

Below are my findings [RM-FP model remote delivered with the 777):

Format is:
Button [OTHER FN]
keycode response on button press
RAW data with showkey -k

Code:
SOURCE
nothing
0x00 0x82 0xf9 0x80 0x82 0xf9

POWER
keycode 222
0x74 0xf4

1
keycode 10
0x02 0x82

2
keycode 11
0x03 0x83

3
keycode 12
0x04 0x84

4
keycode 13
0x05 0x85

5 [DRAG]
keycode 14
0x06 0x86

6
keycode 15
0x07 0x87

7
keycode 16
0x08 0x88

8
keycode 17
0x09 0x89

9
keycode 18
0x0a 0x8a

0
keycode 19
0x0b 0x8b

L [DISPLAY]
nothing
0x00 0x82 0xf2 0x80 0x82 0xf2

R [Ch RTN]
keycode 152
0x00 0x81 0xa8 0x80 0x81 0xa8

SNAP SHOT
nothing
0x00 0x83 0x9a 0x80 0x83 0x9a

16-CH PREV
keycode 185
0x00 0x81 0xd2 0x80 0x81 0xd2

CH Up
Nothing
0x00 0x83 0x92 0x80 0x83 0x92

VOL Down
keycode 174
0x72 0xf2

FULL SCREEN
Nothing
0x00 0x82 0xf4 0x80 0x82 0xf4

VOL Up
keycode 176
0x73 0xf3 

CH Down
Nothing
0x00 0x83 0x93 0x80 0x83 0x93 

MUTE
keycode 160
0x71 0xf1 

AUDIO
Nothing
0x00 0x83 0x88 0x80 0x83 0x88 

RECORD
keycode 177
0x00 0x81 0xa7 0x80 0x81 0xa7 

PLAY
keycode 179
0x00 0x81 0xcf 0x80 0x81 0xcf 

STOP
keycode 232
0x00 0x81 0x80 0x80 0x81 0x80 

TIMESHIFT/PAUSE
keycode 110
0x77 0xf7 

PURPLE/PINK <<
Nothing
0x00 0x83 0x8e 0x80 0x83 0x8e 

YELLOW >>
Nothing
0x00 0x83 0x90 0x80 0x83 0x90 

TELETEXT
Nothing
0x00 0x83 0x84 0x80 0x83 0x84 

GREEN |<<  [WAKEUP]
Nothing
0x00 0x83 0x8f 0x80 0x83 0x8f 

BLUE >>|   [SLEEP]
Nothing
0x00 0x83 0x91 0x80 0x83 0x91 

EPG
Nothing
0x00 0x83 0x89 0x80 0x83 0x89 

MENU
keycode 229
0x00 0x81 0xd9 0x80 0x81 0xd9
Posted in Uncategorized
Views 1649 Comments 0
« Prev     Main     Next »

  



All times are GMT -5. The time now is 08:15 PM.

Main Menu
Advertisement

Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration