From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: 3.9.2 kernel - IR / em28xx_rc broken?
Date: Mon, 20 May 2013 14:47:47 +0200 [thread overview]
Message-ID: <519A1B73.6050602@googlemail.com> (raw)
In-Reply-To: <519A1939.6030907@googlemail.com>
Am 20.05.2013 14:38, schrieb Frank Schäfer:
> ...
> But there was a third change:
> 3.) the scancode passed to the RC core with rc_keypress() in case of
> RC_BIT_UNKNOWN changed from a 16 bit value to 32 bit value (e.g.: old:
> 00 00 ab cd => new: ab cd xx xx).
See
commit 105e3687ada4ebe6dfbda7abc3b16106f86a787d
Author: Mauro Carvalho Chehab <mchehab@redhat.com>
Date: Sat Dec 15 08:29:11 2012 -0300
[media] em28xx: add support for NEC proto variants on em2874 and upper
default_polling_getkey() (em2860/em2880) still returns the 16 bit scancode.
Whatever scancode is correct, it should be the same in both cases...
Mauro, can you take a look at this ?
Regards,
Frank
next prev parent reply other threads:[~2013-05-20 12:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 13:57 3.9.2 kernel - IR / em28xx_rc broken? Chris Rankin
2013-05-18 14:36 ` Frank Schäfer
2013-05-18 15:17 ` Chris Rankin
2013-05-18 16:58 ` Frank Schäfer
2013-05-18 21:02 ` Chris Rankin
2013-05-19 13:40 ` Frank Schäfer
2013-05-19 14:11 ` Chris Rankin
2013-05-19 17:26 ` Frank Schäfer
2013-05-19 19:59 ` Chris Rankin
2013-05-19 21:02 ` Frank Schäfer
2013-05-19 22:36 ` Chris Rankin
2013-05-19 23:04 ` Chris Rankin
2013-05-20 12:38 ` Frank Schäfer
2013-05-20 12:47 ` Frank Schäfer [this message]
2013-05-20 13:01 ` Chris Rankin
2013-05-20 13:43 ` Frank Schäfer
2013-05-20 14:51 ` Chris Rankin
2013-05-20 15:36 ` Frank Schäfer
2013-05-20 16:02 ` Chris Rankin
2013-06-13 10:39 ` Mauro Carvalho Chehab
2013-06-13 10:50 ` Mauro Carvalho Chehab
2013-05-20 0:45 ` Chris Rankin
2013-05-20 12:40 ` Frank Schäfer
2013-05-20 12:48 ` Chris Rankin
2013-05-18 21:11 ` Chris Rankin
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=519A1B73.6050602@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rankincj@yahoo.com \
/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.