[linux-dvb] AF9015_REMOTE_MSI_DIGIVOX_MINI_II_V3 works, but keys get stuck

[linux-dvb] AF9015_REMOTE_MSI_DIGIVOX_MINI_II_V3 works, but keys get stuck

[Andrej Podzimek]

Hello, 

based on this enum in v4l/af9015.h

	enum af9015_remote {
		AF9015_REMOTE_NONE                    = 0,
		AF9015_REMOTE_A_LINK_DTU_M,
		AF9015_REMOTE_MSI_DIGIVOX_MINI_II_V3,
		AF9015_REMOTE_MYGICTV_U718,
		AF9015_REMOTE_DIGITTRADE_DVB_T,
	};

I added this line to /etc/modprobe.conf

	options dvb-usb-af9015 remote=2

After reloading the module, the remote control (almost) worked. Unfortunately, keys got stuck somehow, just as if I were holding a key on the keyboard. Another key press changed the event being repeated, but there seemed to be *no* key release events at all.

Pressing the channel up/down keys seemed to stop that key event flood, but both of my keyboards (one on the laptop and an external one) stopped working. Again, this may have been due to the absence of a key release event. (This time the key events were not that obvious, since channel up/down does not produce an alphanumeric key code.)

I use kernel 2.6.27.10, revision af9015-57423d241699 and (presumably) MSI Digivox Mini II V3.

Either I misunderstood / misconfigured something, or this could be a bug. I'm not familiar with this source code and don't have time to explore it in detail. However, feel free to ask for debugging output and other data you may need.

Regards,

Andrej Podzimek

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] AF9015_REMOTE_MSI_DIGIVOX_MINI_II_V3 works, but keys get stuck

[Antti Palosaari]

Andrej Podzimek wrote:
> After reloading the module, the remote control (almost) worked. Unfortunately, keys got stuck somehow, just as if I were holding a key on the keyboard. Another key press changed the event being repeated, but there seemed to be *no* key release events at all.
> 
> Pressing the channel up/down keys seemed to stop that key event flood, but both of my keyboards (one on the laptop and an external one) stopped working. Again, this may have been due to the absence of a key release event. (This time the key events were not that obvious, since channel up/down does not produce an alphanumeric key code.)
> 
> I use kernel 2.6.27.10, revision af9015-57423d241699 and (presumably) MSI Digivox Mini II V3.
> 
> Either I misunderstood / misconfigured something, or this could be a bug. I'm not familiar with this source code and don't have time to explore it in detail. However, feel free to ask for debugging output and other data you may need.

This seems to be hw bug. For more information:

http://www.linuxtv.org/pipermail/linux-dvb/2008-November/030292.html

regards
Antti

Re: AF9015_REMOTE_MSI_DIGIVOX_MINI_II_V3 works, but keys get stuck

[Andrej Podzimek]

>> After reloading the module, the remote control (almost) worked. Unfortunately, keys got stuck somehow, just as if I were holding a key on the keyboard. Another key press changed the event being repeated, but there seemed to be *no* key release events at all.
>>
>> Pressing the channel up/down keys seemed to stop that key event flood, but both of my keyboards (one on the laptop and an external one) stopped working. Again, this may have been due to the absence of a key release event. (This time the key events were not that obvious, since channel up/down does not produce an alphanumeric key code.)
>>
>> I use kernel 2.6.27.10, revision af9015-57423d241699 and (presumably) MSI Digivox Mini II V3.
>>
>> Either I misunderstood / misconfigured something, or this could be a bug. I'm not familiar with this source code and don't have time to explore it in detail. However, feel free to ask for debugging output and other data you may need.
> 
> This seems to be hw bug. For more information:
> 
> http://www.linuxtv.org/pipermail/linux-dvb/2008-November/030292.html

Hello,

Those quirks worked perfectly fine before I switched to kernel 2.6.28. (I use 2.6.28.6 at the moment.) Now I have the same problem again. Is there a new workaround? Tried the driver included in the kernel and the mercurial tree. Keys remain „down“ in both cases.

Regards,

Andrej Podzimek