Hello,
the remote-plugins works well with my nova-t's remote control, but unfortunatly it reacts on my tv's remote-control as well. Switching AV on my tv seems to be the same as the power-button on the nova-t's remote control, thus powering my vdr off.
The only solution I can think off is disabling the key in the remote.conf for the power-button or using another button for the power-off event, which both seems not quite nice to me.
Do you know another solution?
Thanks, André
André Bischof wrote:
the remote-plugins works well with my nova-t's remote control, but unfortunatly it reacts on my tv's remote-control as well. Switching AV on my tv seems to be the same as the power-button on the nova-t's remote control, thus powering my vdr off.
Does your TV react on the nova-t remote too?
If yes, then you're doomed. If no, you're using the DVB remote driver in 'all devices' mode, which ignores the device id of the remote signals.
If you use av7110_loadkeys, use the -a flag to select the correct id, or, even better, dont use av7110_loadkeys and let the remote plugin handle that. The remote plugin will usually use the -a mode.
Cheers,
Udo
Udo Richter wrote:
André Bischof wrote:
the remote-plugins works well with my nova-t's remote control, but unfortunatly it reacts on my tv's remote-control as well. Switching AV on my tv seems to be the same as the power-button on the nova-t's remote control, thus powering my vdr off.
Does your TV react on the nova-t remote too?
If yes, then you're doomed. If no, you're using the DVB remote driver in 'all devices' mode, which ignores the device id of the remote signals.
If you use av7110_loadkeys, use the -a flag to select the correct id, or, even better, dont use av7110_loadkeys and let the remote plugin handle that. The remote plugin will usually use the -a mode.
Sorry, av7110_loadkeys cannot be used with budget cards. The budget drivers do not support keymap loading or address selection.
Oliver
Oliver Endriss schrieb: ...
Does your TV react on the nova-t remote too?
Until now I have not encountered this, it seems only to be the other way round.
If yes, then you're doomed. If no, you're using the DVB remote driver in 'all devices' mode, which ignores the device id of the remote signals.
If you use av7110_loadkeys, use the -a flag to select the correct id, or, even better, dont use av7110_loadkeys and let the remote plugin handle that. The remote plugin will usually use the -a mode.
Sorry, av7110_loadkeys cannot be used with budget cards. The budget drivers do not support keymap loading or address selection.
Well, I don't know anything about av7110_loadkeys, the only thing I know is that the adv717x module is loades (among others), but nothing like av7110.
Maybe you could tell me how and where to configure this, but maybe it is not necessary because Oliver told that this does not work with budget cards?
Is there another way to restrict the remote to the device ID of the correct remote control?
André
I demand that André Bischof may or may not have written...
Oliver Endriss schrieb: ...
Does your TV react on the nova-t remote too?
Until now I have not encountered this, it seems only to be the other way round.
<AOL>. My Nova-T (budget-ci) responds to some button presses on various Philips remote controls, but none of the other devices respond to the Nova-T remote control.
If yes, then you're doomed. If no, you're using the DVB remote driver in 'all devices' mode, which ignores the device id of the remote signals.
If you use av7110_loadkeys, use the -a flag to select the correct id, or, even better, dont use av7110_loadkeys and let the remote plugin handle that. The remote plugin will usually use the -a mode.
Sorry, av7110_loadkeys cannot be used with budget cards. The budget drivers do not support keymap loading or address selection.
Well, I don't know anything about av7110_loadkeys, the only thing I know is that the adv717x module is loades (among others), but nothing like av7110.
If you have a line looking like N: Name="Budget-CI dvb ir receiver saa7146 (0)" in /proc/bus/input/devices then your card is similar to mine, and you can patch budget-ci to support keymap loading.
I've just updated my patch for this to work with v4l-dvb CVS; along with the corresponding utils patch, it's been sent to linux-dvb.
[snip]
Is there another way to restrict the remote to the device ID of the correct remote control?
The driver (in my case, at least) is seeing the same range of values regardless of which remote control is being used.
Darren Salt schrieb: ...
If you have a line looking like N: Name="Budget-CI dvb ir receiver saa7146 (0)" in /proc/bus/input/devices then your card is similar to mine, and you can patch budget-ci to support keymap loading.
I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="Budget-CI dvb ir receiver saa7146 (0)" P: Phys= H: Handlers=kbd event4 B: EV=3 B: KEY=1b0c4004 31 0 0 0 0 18000 4180 4000801 9e1680 0 14000 50000ffc
Looks more then just similar! ;)
I've just updated my patch for this to work with v4l-dvb CVS; along with the corresponding utils patch, it's been sent to linux-dvb.
Would you mind sending it to me (PM) as well? And maybe you could provide some basic instructions WHAT I should patch and HOW, as I'm not familiar with patching - that would be great!
André
I demand that André Bischof may or may not have written...
Darren Salt schrieb: ...
If you have a line looking like N: Name="Budget-CI dvb ir receiver saa7146 (0)" in /proc/bus/input/devices then your card is similar to mine, and you can patch budget-ci to support keymap loading.
I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="Budget-CI dvb ir receiver saa7146 (0)"
[snip]
Looks more then just similar! ;)
So I see :-)
I've just updated my patch for this to work with v4l-dvb CVS; along with the corresponding utils patch, it's been sent to linux-dvb.
Would you mind sending it to me (PM) as well?
URL:http://www.youmustbejoking.demon.co.uk/progs/linux/dvb-budget-ci.patch.tar.gz
There are five patches (two are new); you'll need two of them.
And maybe you could provide some basic instructions WHAT I should patch and HOW, as I'm not familiar with patching - that would be great!
The README in the tarball should be adequate.
-
André Bischof -
Darren Salt -
Oliver Endriss -
Udo Richter