public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Lawrence Rust <lawrence@softsystem.co.uk>
To: Jarod Wilson <jarod@wilsonet.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] Fix cx88 remote control input
Date: Fri, 08 Apr 2011 17:22:27 +0200	[thread overview]
Message-ID: <1302276147.1749.46.camel@gagarin> (raw)
In-Reply-To: <AFEB19DA-4FD6-4472-9825-F13A112B0E2A@wilsonet.com>

On Fri, 2011-04-08 at 10:41 -0400, Jarod Wilson wrote:
> On Apr 8, 2011, at 8:50 AM, Lawrence Rust wrote:
> 
> > This patch restores remote control input for cx2388x based boards on
> > Linux kernels >= 2.6.38.
> > 
> > After upgrading from Linux 2.6.37 to 2.6.38 I found that the remote
> > control input of my Hauppauge Nova-S plus was no longer functioning.  
> > I posted a question on this newsgroup and Mauro Carvalho Chehab gave
> > some helpful pointers as to the likely cause.
> > 
> > Turns out that there are 2 problems:
> ...
> > 2. The RC5 decoder appends the system code to the scancode and passes
> > the combination to rc_keydown().  Unfortunately, the combined value is
> > then forwarded to input_event() which then fails to recognise a valid
> > scancode and hence no input events are generated.
> 
> Just to clarify on this one, you're missing a step. We get the scancode,
> and its passed to rc_keydown. rc_keydown then looks for a match in the
> loaded keytable, then passes the *keycode* that matches the scancode
> along to input_event. If you fix the keytable to contain system and
> command, everything should work just fine again. Throwing away data is
> a no-no though -- take a look at recent changes to ir-kdb-i2c, which
> actually just recently made it start *including* system. :)

Don't shoot the messenger.

I'm just reporting what I had to do to fix a clumsy hack by someone 6
months ago who didn't test their changes.  This patch _restores_ the
operation of a subsystem broken by those changes

Perhaps those responsible for commit
2997137be8eba5bf9c07a24d5fda1f4225f9ca7d:

    Signed-off-by: David Härdeman <david@hardeman.nu>
    Acked-by: Jarod Wilson <jarod@redhat.com>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

should fix the keytable.  In the meantime (next year) I'll be using this
patch.

-- 
Lawrence



  reply	other threads:[~2011-04-08 15:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 12:50 [PATCH] Fix cx88 remote control input Lawrence Rust
2011-04-08 14:32 ` Jarod Wilson
2011-04-08 14:41 ` Jarod Wilson
2011-04-08 15:22   ` Lawrence Rust [this message]
2011-04-08 16:21     ` Jarod Wilson
2011-04-08 16:50       ` Lawrence Rust
2011-04-08 18:18         ` Jarod Wilson
2011-04-08 17:07       ` Devin Heitmueller
2011-04-08 18:00         ` Jarod Wilson
2011-04-08 18:38           ` Devin Heitmueller
2011-04-08 19:27             ` Jarod Wilson
2011-04-08 20:50               ` Andy Walls
2011-04-10  1:39                 ` Jarod Wilson
2011-04-10 23:08                   ` HVR-1250/CX23885 IR Rx (Re: [PATCH] Fix cx88 remote control input) Andy Walls
2011-06-28  0:38                     ` HVR-1250/CX23885 IR Rx Jarod Wilson
2011-06-28 10:30                       ` Andy Walls
2011-06-28 21:39                         ` Jarod Wilson
2011-06-28 22:32                           ` Andy Walls
2011-06-29  2:17                             ` Jarod Wilson
2011-06-29  3:54                               ` Andy Walls
2011-05-02 18:50 ` [PATCH] Fix cx88 remote control input Mauro Carvalho Chehab
2011-05-03  7:25   ` Lawrence Rust
2011-05-03 17:19     ` Jarod Wilson
2011-05-04 20:16       ` Mauro Carvalho Chehab
2011-05-04 20:36         ` Greg KH
2011-05-05  2:25           ` Mauro Carvalho Chehab
2011-05-05 20:35             ` Greg KH
2011-05-05 21:08             ` Patch "[media] cx88: Fix HVR4000 IR keymap" has been added to the 2.6.38-stable tree gregkh

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=1302276147.1749.46.camel@gagarin \
    --to=lawrence@softsystem.co.uk \
    --cc=jarod@wilsonet.com \
    --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