[linux-dvb] Nova-t remote stopped working (budget_ci rc5_device not set?)
linux-dvb-list at krp.org.uk
Sat Jan 26 18:31:37 CET 2008
On Mon, 2008-01-07 at 22:05 +0000, Darren Salt wrote:
[rc5_device for Nova-T]
> -1 is autodetect, meaning whatever is correct for the remote control which is
> normally supplied with the DVB device. For your Nova-T, this should be
> causing 0x1F to be used.
> > 2) How do I work out the value of rc5_device for my remotes? I've found
> > mention of looking at the ir_debug output, but no instruction of how to
> > interpret it.
> It's described in the comments within msp430_ir_interrupt
> (media/dvb/ttpci/budget-ci.c). Look at the lower 5 bits of the bytes with bit
> 6 clear; it might help to report output from "lspci -nv" for the card.
Did you mean bit 7 lowest clear - bit 6 being the "RC5 toggle
bit" ( whatever that is) according to budget-ci.c ? 
I reserve the right to be completely confused ;)
If so, afaict, the black/grey remote is showing up as 0x1A, not 0x1F -
which would explain the symptoms.
Jan 26 17:03:18 yaffle kernel: budget_ci: received byte 0xcf
Jan 26 17:03:18 yaffle kernel: budget_ci: received byte 0x4f
Jan 26 17:03:18 yaffle kernel: budget_ci: received byte 0x3a
... that final code being 0b0011 1010, with lower 5 bits being device
number, which would be 0x1A.
# lspci -nv
02:04.0 0480: 1131:7146 (rev 01)
Flags: bus master, medium devsel, latency 32, IRQ 21
Memory at f600c000 (32-bit, non-prefetchable) [size=512]
I'm pretty sure this black/grey remote is the one that came with the
Nova-T. I have a small all-black remote lying around, but that gives:
Jan 26 17:09:05 yaffle kernel: budget_ci: received byte 0xc1
Jan 26 17:09:05 yaffle kernel: budget_ci: received byte 0x41
Jan 26 17:09:05 yaffle kernel: budget_ci: received byte 0x20
-> 0b0010 0000 -> device 0x00 ?!
 The msp430 chip can generate two different bytes, command and device
* type1: X1CCCCCC, C = command bits (0 - 63)
* type2: X0TDDDDD, D = device bits (0 - 31), T = RC5 toggle bit
* Each signal from the remote control can generate one or more command
* bytes and one or more device bytes. For the repeated bytes, the
* highest bit (X) is set. The first command byte is always generated
* before the first device byte. Other than that, no specific order
* seems to apply. To make life interesting, bytes can also be lost.
More information about the linux-dvb