From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: 3.9.2 kernel - IR / em28xx_rc broken?
Date: Mon, 20 May 2013 17:36:46 +0200 [thread overview]
Message-ID: <519A430E.4080006@googlemail.com> (raw)
In-Reply-To: <1369061513.11886.YahooMailNeo@web120305.mail.ne1.yahoo.com>
Am 20.05.2013 16:51, schrieb Chris Rankin:
> ----- Original Message -----
>
>> If I had to guess, I would say you should check your rc_maps.cfg / keytable. ;)
> This is unchanged between 3.8.x and 3.9.x, and so is correct by definition.
No, just because it didn't change it isn't automatically correct. ;)
Which protocol type does you keytable specify/select ?
It should be RC5. If it's none or unknown, it's just dump luck that
things are working (because the driver fortunately configures the device
for RC5 in case of RC_BIT_UNKNOWN).
> Kernel Upgrades Do Not Break Userspace.
Right.
That's why I would say the third (scancode) change is problematic.
Let's see what Mauro thinks about this.
Regards,
Frank
> Cheers,
> Chris
>
next prev parent reply other threads:[~2013-05-20 15:35 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
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 [this message]
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=519A430E.4080006@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.