All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Lawrence Rust <lawrence@softsystem.co.uk>
Cc: Andy Walls <awalls@md.metrocast.net>,
	Jarod Wilson <jarod@redhat.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] ir-rc6-decoder: Support RC6-6A variable length data
Date: Wed, 23 Nov 2011 22:32:45 -0200	[thread overview]
Message-ID: <4ECD90AD.1020803@redhat.com> (raw)
In-Reply-To: <1320064772.1669.13.camel@gagarin>

Em 31-10-2011 10:39, Lawrence Rust escreveu:
> Hi,
> 
> Thanks for the comments and feedback that you gave concerning this
> patch.  In the light of these I have made some small changes.
> 
> In particular I would like to address Mauro's comments regarding
> changing the size of a scancode to accommodate 128 bits.  I've given
> this some thought and believe that leaving it at 32 bits is the best
> solution.  Changing it risks breaking all sorts of code with no tangible
> benefit since I've not found a RC that uses more than 32 bits.
> 
> The code now tracks frames with > 32 data bits, in order to cleanly
> detect the end of frame, but now reports an error and discards the data.
> 
> Hope this meets with your approval.  The following patch is against 3.0
> 

It seems Jarod didn't have time to test it. I took a long time here testing
every single IR I had, in order to see if I could have, by any chance, any
RC-6 IR lost... The net result is that I have dozens of NEC and RC-5 IR's, 
a few JVC, SONY and SANYO ones, but just one RC-6 IR. 

The one I have is RC6(0) 16 bits. So, I can only testify that this IR didn't
break by this patch.

Anyway, I won't hold this patch anymore. Let's put it at the devel tree and
see if people complain, or otherwise test it with different RC-6 lengths.

Regards,
Mauro

      reply	other threads:[~2011-11-24  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 12:39 [PATCH] ir-rc6-decoder: Support RC6-6A variable length data Lawrence Rust
2011-11-24  0:32 ` Mauro Carvalho Chehab [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=4ECD90AD.1020803@redhat.com \
    --to=mchehab@redhat.com \
    --cc=awalls@md.metrocast.net \
    --cc=jarod@redhat.com \
    --cc=lawrence@softsystem.co.uk \
    --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 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.