public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrej Podzimek <andrej@podzimek.org>
To: linux-media@vger.kernel.org
Subject: Re: AF9015_REMOTE_MSI_DIGIVOX_MINI_II_V3 works, but keys get stuck
Date: Wed, 18 Feb 2009 23:05:47 +0100	[thread overview]
Message-ID: <499C863B.5000507@podzimek.org> (raw)
In-Reply-To: <4973900C.6090406@iki.fi>

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

      reply	other threads:[~2009-02-18 22:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 19:30 [linux-dvb] AF9015_REMOTE_MSI_DIGIVOX_MINI_II_V3 works, but keys get stuck Andrej Podzimek
2009-01-18 20:24 ` Antti Palosaari
2009-02-18 22:05   ` Andrej Podzimek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=499C863B.5000507@podzimek.org \
    --to=andrej@podzimek.org \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox