Re: Trying to enable RC6 IR for PCTV T2 290e

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I'm not seeing anything when I use "ir-keytable -t /dev/input/...."
for my RC node in RC6 mode, although it does respond correctly in RC5
mode.

FWIW, I've realised that the 05a4:9881 IR dongle is actually
responding to all of its remote's keys. The problem is that USBHID
creates two /dev/input/eventXX nodes - one for a keyboard and the
other for a mouse. The keys which are "missing" when listening to the
keyboard device node are actually being reported from the mouse device
node! Is there any way to get a single device node to report *all* of
the keypresses, please?

Thanks,
Chris


On Sun, Nov 15, 2015 at 10:46 PM, Mauro Carvalho Chehab
<mchehab@xxxxxxxxxxxxxxx> wrote:
> Em Sun, 15 Nov 2015 22:18:48 +0000
> Chris Rankin <rankincj@xxxxxxxxxxxxxx> escreveu:
>
>> > How are you "switching back to RC5"?
>>
>> I use the command "ir-keytable -p rc-5" or "ir-keytable -p rc-6" to
>> switch between IR protocols, which does seem to invoke the
>> em2874_ir_change_protocol() function. I'm not sure that I have a
>> suitable RC6 keymap for this IR, and was expecting to have to create
>> it myself by logging the scancodes returned by the driver.
>
> Did you test with ir-keytable -t? If you don't load a keytable,
> you'll be able to only see the scancodes.
>
> Also, AFAIKT, the hardware decoder on em2874 only supports one
> variant of RC6 protocol.
>
>>
>> Cheers,
>> Chris
>>
>> On Sun, Nov 15, 2015 at 9:48 PM, Devin Heitmueller
>> <dheitmueller@xxxxxxxxxxxxxx> wrote:
>> >> I've dug a bit deeper and discovered that the reason the
>> >> em28xx_info(...) lines that I'd added to em2874_polling_getkey()
>> >> weren't appearing is because I'd loaded the wrong version of the
>> >> em28xx-rc module! (Doh!)
>> >
>> > Ok, good.
>> >
>> >> The polling function *is* being called regularly, but
>> >> em28xx_ir_handle_key() isn't noticing any keypresses. (However, it
>> >> does notice when I switch back to RC5).
>> >
>> > How are you "switching back to RC5"?  Are you actually loading in an
>> > RC6 versus RC5 keymap?  The reason I ask is because the onboard
>> > receiver has to be explicitly configured into one of the two modes,
>> > and IIRC this happens based on code type for the loaded keymap.  Hence
>> > if you have an RC5 keymap loaded, you'll never see the IR receiver
>> > reporting RC6 codes.
>> >
>> > And of course it's always possible you've hit a bug/regression.  I
>> > haven't touched that code in years and I know it's been through a
>> > couple of rounds of refactoring.
>> >
>> > Devin
>> >
>> > --
>> > Devin J. Heitmueller - Kernel Labs
>> > http://www.kernellabs.com
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux