[linux-dvb] DViCO Dual Digital 4 and remote

Michael Krufky mkrufky at linuxtv.org
Mon Jul 2 18:22:34 CEST 2007


Petey Leinonen wrote:
> --- Michael Krufky <mkrufky at linuxtv.org> wrote:
>
>   
>> David Findlay wrote:
>>     
>>>> If you could find a photo of it, that would help.  Worst case scenario, I
>>>> can send you a patch to enable the IR, and you may have to program the
>>>> remote keymap (We already have keymaps ready for 1, 2, and 3 -- only 4
>>>> needs programming, but I have that one here, and plan to take care of it
>>>> over the weekend)
>>>>         
>>> http://www.davsoft.com.au/remote1.jpg
>>> http://www.davsoft.com.au/remote2.jpg <- shows the ir receiver which looks 
>>> more like an IR led to me. 
>>>       
>> Perfect!  I took the right guess -- the remote shown above is the MCE remote.
>>  This patch should do the trick:
>>
>> http://linuxtv.org/~mkrufky/pending/xc/bluebird2-ir.patch
>>
>> Please provide some feedback -- let me know whether or not this works.
>>
>> Cheers,
>>
>> Mike
>>     
>
> Thanks for providing the pics David. I can confirm that is what my remote and
> receiver look like.
>
> Mike, thank you for the patch. I've applied it and I now have 2 new /dev/input/
> event entries, 3 & 4:
>
> [17179588.964000] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in
> warm state.
> [17179588.964000] dvb-usb: will pass the complete MPEG2 transport stream to the
> software demuxer.
> <wifi and video card stuff removed>
> [17179589.812000] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
> [17179589.844000] input: IR-receiver inside an USB DVB receiver as
> /class/input/input3
> [17179589.844000] dvb-usb: schedule remote query interval to 150 msecs.
> [17179589.844000] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully
> initialized and connected.
> [17179589.844000] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in
> warm state.
> [17179589.844000] dvb-usb: will pass the complete MPEG2 transport stream to the
> software demuxer.
> [17179589.876000] DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual
> Digital 4).
> [17179590.164000] DVB: registering frontend 1 (Zarlink ZL10353 DVB-T)...
> [17179590.164000] input: IR-receiver inside an USB DVB receiver as
> /class/input/input4
> [17179590.164000] dvb-usb: schedule remote query interval to 150 msecs.
> [17179590.164000] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully
> initialized and connected.
> [17179590.164000] usbcore: registered new driver dvb_usb_cxusb
>
> However when I try to use them nothing happens. I have tried "cat
> /dev/input/event3" and  "irrecord --driver=dev/input --device=/dev/input/event3
> bob.txt", but pressing buttons does nothing. The green led on the remote goes
> on when I press a button. With irrecord I get the following output after
> pressing RETURN and holding a button for a few seconds:
> Hold down an arbitrary button.
> irrecord: gap not found, can't continue
> irrecord: closing '/dev/input/event3'
>
> I also tried with event4.

Luke Tupper wrote:
> I am in the process of setting up a MythTV box with DViCo FusionHDTV
> Dual Digital 4 and got everything but the remote control working.
> After a lot of hunting around I found your recent posts on the
> Linux-Dvb mailing list with your patch for the remote. I noticed you
> wanted some feedback on the patch.
>
> Previously the remotes couldn't be seen at all. Now when I run cat
> /proc/bus/input/devices I see two USB Remote controls. Looking through
> the Ubuntu hardware manager both cards appear under each DVB device.
>
> However if I run sudo evtest /dev/input/event4 (event5) I don't get
> any response when pressing the remote. Also a brief test with the
> standard LIRC setup for DVICO remotes doesn't give any joy either.
>
> Finally a big thanks for all of your work in getting these devices to
> run under linux. I noticed it was one of your patches that makes the
> card work.

Luke & Petey,

OK, well.... based on the logs, it seems like those i2c reads from 0x6b
would be IR traffic...  Although it's possible that the windows driver
is just repeatedly querying the RTC, although that seems strange.

I double-checked on the ATSC NANO, (i have that device here) , and it
seems to use the same mechanism for IR that the original bluebird
firmware used....  So, we may as well try that way too, although I do
not see any usage of this command in the dd4 logs....   But, it's still
worth a try.

Please apply the attached patch on top of what you already have... Let
me know what happens.

Cheers,

Mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: try-this-ir.patch
Type: text/x-patch
Size: 530 bytes
Desc: not available
Url : http://www.linuxtv.org/pipermail/linux-dvb/attachments/20070702/e34880db/attachment.bin 


More information about the linux-dvb mailing list