From: Antti Palosaari <crope@iki.fi>
To: Stefan Lippers-Hollmann <s.L-H@gmx.de>
Cc: linux-media@vger.kernel.org
Subject: Re: [GIT PULL FOR 2.6.37] new AF9015 devices
Date: Fri, 10 Sep 2010 13:12:24 +0300 [thread overview]
Message-ID: <4C8A0488.9020206@iki.fi> (raw)
In-Reply-To: <201009100254.07762.s.L-H@gmx.de>
On 09/10/2010 03:54 AM, Stefan Lippers-Hollmann wrote:
> Another test and some further debugging of the IR core usedby the af9015
> branch of this git tree led me to partial success. DVB-T functionality
> continues to be fine and I've now found the proper values for this remote,
> however once a key gets pressed, it is never released (unless another key
> gets pressed which is then struck or unless I ctrl-c it (only works on
> terminals). Likewise I'm not sure yet how to distinguish between the
> "Cinergy T Dual" and my "Cinergy T RC MKII":
> Given that keys, once pressed, remain to be stuck, using both lirc's
> dev/input and without any dæmon trying to catch keypresses, I have not
> reached a functional configuration.
That`s known issue. Chip configures USB HID polling interval wrongly and
due to that HID starts repeating usually. There is USB-ID mapped quirks
in HID driver to avoid that, but only for few ADF9015 IDs...
I know how to fix that totally. I have been waiting new IR core merge
before switch remote from broken HID + polling to memory read based one.
But maybe I can do it just now and convert it later to IR core.
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2010-09-10 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 21:12 [GIT PULL FOR 2.6.37] new AF9015 devices Antti Palosaari
2010-09-09 23:19 ` Stefan Lippers-Hollmann
2010-09-10 0:54 ` Stefan Lippers-Hollmann
2010-09-10 10:12 ` Antti Palosaari [this message]
2010-09-10 11:47 ` Stefan Lippers-Hollmann
2010-09-22 19:02 ` Mauro Carvalho Chehab
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=4C8A0488.9020206@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=s.L-H@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.