[linux-dvb] Nova-t remote stopped working (budget_ci rc5_device not set?)
linux at youmustbejoking.demon.co.uk
Sat Jan 26 19:07:04 CET 2008
I demand that Kevin Page may or may not have written...
> 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
> 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 ;)
No; the comments clearly indicate bits 6 and 5, though they're not referenced
> If so, afaict, the black/grey remote is showing up as 0x1A, not 0x1F -
> which would explain the symptoms.
Odd... the 34-key version should be showing up as 0x1F and the 45-key version
as 0x1E. (Or at least that's what happens with mine.)
> 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.
What's the code on the reverse of the battery compartment cover? This might
be useful information for the wiki...
> # lspci -nv
> 02:04.0 0480: 1131:7146 (rev 01)
> Subsystem: 13c2:1011
> Flags: bus master, medium devsel, latency 32, IRQ 21
> Memory at f600c000 (32-bit, non-prefetchable) [size=512]
I think that that's identical to mine...
> 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 ?!
It would appear so...
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Generate power using sun, wind, water, nuclear. FORGET COAL AND OIL.
How many weeks are there in a light year?
More information about the linux-dvb