Trying to enable RC6 IR for PCTV T2 290e

[Chris Rankin]

Hi,

My Hauppauge RC5 remote control finally broke, and the PCTV T2 290e's
native RC5 remote control isn't suitable for VDR, and so I bought a
cheap RC6 remote as a replacement. The unit I chose was the Ortek
VRC-1100 Vista MCE Remote Control, USB ID 05a4:9881. I've been able to
switch the PCTV device into RC6 mode using "ir-keytable -p rc-6",
which does seem to execute the correct case of
em2874_ir_change_protocol(). However, when I press any buttons on my
new remote, I still don't see em2874_polling_getkey() being called,
which makes me wonder if the RC6 support is truly enabled.

Has anyone managed to use this device's RC6 functionality, please? I
can test patches for this driver (againt Linux 4.2.6).

FWIW, I did manage to configure VDR to use the MCE remote's native USB
dongle, although I needed to tweak my X server's configuration first:

Section "InputClass"
Identifier "VDR IR dongle"
MatchUSBID "05a4:9881"
Option"Ignore" "on"
EndSection

and even then, VDR *still* didn't recognise all of the keys.

Cheers,
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

[Devin Heitmueller]

On Sun, Nov 15, 2015 at 3:49 PM, Chris Rankin  wrote:
> Hi,
>
> My Hauppauge RC5 remote control finally broke, and the PCTV T2 290e's
> native RC5 remote control isn't suitable for VDR, and so I bought a
> cheap RC6 remote as a replacement. The unit I chose was the Ortek
> VRC-1100 Vista MCE Remote Control, USB ID 05a4:9881. I've been able to
> switch the PCTV device into RC6 mode using "ir-keytable -p rc-6",
> which does seem to execute the correct case of
> em2874_ir_change_protocol(). However, when I press any buttons on my
> new remote, I still don't see em2874_polling_getkey() being called,
> which makes me wonder if the RC6 support is truly enabled.

It's been a few years since I looked at that code, and when I
orginally wrote it I don't think I bothered with the RC6 support.
That said, it's not interrupt driven and the em2874_polling_getkey()
should fire every 100ms regardless of whether the hardware receives an
IR event (the polling code queries a status register and if it sees a
new event it reads the RC code received and announces it to the input
subsystem).

I would probably look through the code and see why the polling routine
isn't setup to run.  There is probably logic in there that causes the
polling to never get enabled if a keymap isn't associated with the
board profile in em28xx-cards.c

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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

[Chris Rankin]

Hi,

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!)

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).

Cheers,
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

[Chris Rankin]

> 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.

Cheers,
Chris

On Sun, Nov 15, 2015 at 9:48 PM, Devin Heitmueller
 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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

[Mauro Carvalho Chehab]

Em Sun, 15 Nov 2015 22:18:48 +
Chris Rankin  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
>  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 majord...@vger.kernel.org
> 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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

[Chris Rankin]

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
 wrote:
> Em Sun, 15 Nov 2015 22:18:48 +
> Chris Rankin  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
>>  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 majord...@vger.kernel.org
>> 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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

[Devin Heitmueller]

> 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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html