<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Hi Herman<br><br>Thankyou very much for your response. The card comes with a remote and a dongle that you plug in to the back, so I assume it includes an IR decoder chip. I think I have found the wiki entry you mentioned at http://www.linuxtv.org/v4lwiki/index.php/Remote_controllers and I will work through the instructions with my card when I get home tonight. I assume that will pose more questions but I greatly appreciate this pointer.<br><br>Thanks again<br><br>Ben<br><br>> Subject: Re: [linux-dvb] Please - can't someone help - saa7134-input Avermedia Super 007 Support (Remote)<br>> From: hermann-pitton@arcor.de<br>> To: ben_v_johnson@hotmail.com<br>> CC: linux-dvb@linuxtv.org<br>> Date: Thu, 31 Jul 2008 20:03:32 +0200<br>> <br>> Hi Ben,<br>> <br>> Am Donnerstag, den 31.07.2008, 19:48 +1000 schrieb Ben Johnson:<br>> > Hi<br>> > <br>> > I sent in this a few days ago, but no one has been able to help yet.<br>> > Please can someone help me.<br>> > <br>> <br>> if this card also has no IR decoder chip on board, like the analog only<br>> ones, then Mauro seems to have a solution.<br>> <br>> Plaese be patient, he is not free in what is on top of his todo list.<br>> <br>> Else for simple gpio remotes we have instructions on the v4l wiki at<br>> linutv.org. If it has an IR controller, you can look up other Avermedia<br>> cards and remotes also at the http://www.bttv-gallery.de<br>> <br>> If already known, then you simply add the card to the gpio remotes in<br>> saa7134-cards.c and accordingly in saa7134-input.c.<br>> <br>> An example for a solution without IR controller chip is the patch for<br>> the recent Asus PC-39 remote. This has an unknown transmitter chip and a<br>> 3.3 Volts only receiver talking some sort of RC5. A potential deadlock,<br>> if irqs are delayed, was fixed later.<br>> <br>> Cheers,<br>> Hermann<br>> <br>> <br>> ________________________________________________________________________<br>> > <br>> > Hi<br>> > <br>> > I am a complete newbie looking for help getting the Remote for an<br>> > Avermedia Super 007 (Digital only) working. After looking around I<br>> > believe that adding support should only require adding a new case to<br>> > the (dev->board) switch in the saa7134-input.c file titled:<br>> > <br>> > SAA7134_BOARD_AVERMEDIA_SUPER_007<br>> > <br>> > Questions:<br>> > 1. Is this forum the right place to be asking these questions? If<br>> > not, where is please?<br>> > 2. Should adding the relevant information to the saa7134-input.c file<br>> > for an otherwise supported saa7134 dvb-t card result in the remote<br>> > being supported?<br>> > 3. If so, how do I determine what information needs to be supplied.<br>> > ie:<br>> > - are the ir_codes_avermedia appropriate for this card<br>> > - how do you tell what the mask_keycode and mask_keydown should be?<br>> > - how do you work out the appropriate polling interval<br>> > - what part does saa_setb play in all this.<br>> > <br>> > I have the card working and am able to upload any supported<br>> > information needed.<br>> > <br>> > Thanks in advance for your help - BVJ.<br>> > <br>> > My New Box:<br>> > 2.6.24-19-generic x86_64 GNU/Linux (Mythbuntu 8.04 fully patched)<br>> > AMD Athalon X2 64 B4850<br>> > Gigabyte MA78GM-S2H with AMD 780 Northbridge & ATI HD 3200 Graphics<br>> > Avermedia Super 007 (Digital Only) saa7133 & tda8290<br>> > <br>> > LSPCI output:<br>> > 03:06.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135<br>> > Video Broadcast Decoder (rev d1)<br>> > Subsystem: Avermedia Technologies Inc Unknown device f01d<br>> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-<br>> > ParErr- Stepping- SERR- FastB2B-<br>> > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-<br>> > <TAbort- <MAbort- >SERR- <PERR-<br>> > Latency: 32 (21000ns min, 8000ns max)<br>> > Interrupt: pin A routed to IRQ 20<br>> > Region 0: Memory at fdcff000 (32-bit, non-prefetchable) [size=2K]<br>> > Capabilities: [40] Power Management version 2<br>> > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA<br>> > PME(D0-,D1-,D2-,D3hot-,D3cold-)<br>> > Status: D0 PME-Enable- DSel=0 DScale=1 PME-<br>> > 00: 31 11 33 71 06 00 90 02 d1 00 80 04 00 20 00 00<br>> > 10: 00 f0 cf fd 00 00 00 00 00 00 00 00 00 00 00 00<br>> > 20: 00 00 00 00 00 00 00 00 00 00 00 00 61 14 1d f0<br>> > 30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 54 20<br>> > 40: 01 00 02 06 00 20 00 1c 00 00 00 00 00 00 00 00<br>> > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br>> > <br>> > <br>> > DMESG output:<br>> > <br>> > [ 47.222507] Linux video capture interface: v2.00<br>> > [ 47.407888] saa7130/34: v4l2 driver version 0.2.14 loaded<br>> > [ 47.407972] saa7133[0]: found at 0000:03:06.0, rev: 209, irq: 20,<br>> > latency: 32, mmio: 0xfdcff000<br>> > [ 47.407979] saa7133[0]: subsystem: 1461:f01d, board: Avermedia<br>> > Super 007 [card=117,autodetected]<br>> > [ 47.407988] saa7133[0]: board init: gpio is 40000<br>> > [ 47.542574] saa7133[0]: i2c eeprom 00: 61 14 1d f0 54 20 1c 00 43<br>> > 43 a9 1c 55 d2 b2 92<br>> > [ 47.542581] saa7133[0]: i2c eeprom 10: ff ff ff ff ff 20 ff ff ff<br>> > ff ff ff ff ff ff ff<br>> > [ 47.542586] saa7133[0]: i2c eeprom 20: 01 40 01 32 32 01 01 43 88<br>> > ff 00 55 ff ff ff ff<br>> > [ 47.542590] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff<br>> > ff ff ff ff ff ff ff<br>> > [ 47.542595] saa7133[0]: i2c eeprom 40: ff 21 00 c0 96 10 03 02 15<br>> > 16 ff ff ff ff ff ff<br>> > [ 47.542599] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff<br>> > ff ff ff ff ff ff ff<br>> > [ 47.542603] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff<br>> > ff ff ff ff ff ff ff<br>> > [ 47.542607] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff<br>> > ff ff ff ff ff ff ff<br>> > <br>> > [ 47.932906] tuner 1-004b: chip found @ 0x96 (saa7133[0])<br>> > [ 47.981769] tda8290 1-004b: setting tuner address to 60<br>> > [ 48.084618] tuner 1-004b: type set to tda8290+75a<br>> > [ 48.132535] tda8290 1-004b: setting tuner address to 60<br>> > [ 48.236347] tuner 1-004b: type set to tda8290+75a<br>> > [ 48.239259] saa7133[0]: registered device video0 [v4l2]<br>> > [ 48.239278] saa7133[0]: registered device vbi0<br>> > [ 48.330034] saa7134 ALSA driver for DMA sound loaded<br>> > [ 48.330064] saa7133[0]/alsa: saa7133[0] at 0xfdcff000 irq 20<br>> > registered as card -2<br>> > [ 48.356488] DVB: registering new adapter (saa7133[0])<br>> > [ 48.356494] DVB: registering frontend 0 (Philips TDA10046H<br>> > DVB-T)...<br>> > [ 48.428950] tda1004x: setting up plls for 48MHz sampling clock<br>> > [ 48.712424] tda1004x: found firmware revision 20 -- ok<br>> > <br>> > <br>> > <br>> > ______________________________________________________________________<br>> <br><br /><hr />Bees, cows, tigers and more! <a href='http://livelife.ninemsn.com.au/article.aspx?id=567534' target='_new'>Windows Live Messenger treats you to 30 free emoticons. </a></body>
</html>