All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jarod Wilson <jarod@redhat.com>
Cc: Jon Smirl <jonsmirl@gmail.com>,
	Maxim Levitsky <maximlevitsky@gmail.com>,
	Jarod Wilson <jarod@wilsonet.com>,
	linux-input <linux-input@vger.kernel.org>,
	linux-media@vger.kernel.org
Subject: Re: Can I expect in-kernel decoding to work out of box?
Date: Wed, 28 Jul 2010 15:40:44 -0300	[thread overview]
Message-ID: <4C5079AC.9030006@redhat.com> (raw)
In-Reply-To: <20100728180516.GG26480@redhat.com>

Em 28-07-2010 15:05, Jarod Wilson escreveu:
> On Wed, Jul 28, 2010 at 03:08:13PM -0300, Mauro Carvalho Chehab wrote:
>> Em 28-07-2010 14:04, Jon Smirl escreveu:
>>> On Wed, Jul 28, 2010 at 11:56 AM, Mauro Carvalho Chehab
>>> <mchehab@redhat.com> wrote:
>>>> Em 28-07-2010 11:41, Jon Smirl escreveu:
>>>>
>>>>> It's possible to build a Linux IR decoder engine that can be loaded
>>>>> with the old LIRC config files.
>>>>
>>>> I think it is a good idea to have a decoder that works with such files anyway.
>>>
>>> The recorder should use the Linux IR system to record the data. It
>>> would confusing to mix the systems. Users need to be really sure that
>>> the standard protocol decoders don't understand their protocol before
>>> resorting to this. Any one in this situation should post their
>>> recorded data so we can check for driver implementation errors.
>>>
>>> An example: if you use irrecord on Sony remotes lirc always records
>>> them in raw mode. The true problem here is that irrecord doesn't
>>> understand that Sony remotes mix different flavors of the Sony
>>> protocol on a single remote. This leads you to think that the Sony
>>> protocol engine is broken when it really isn't. It's the irrecord tool
>>> that is broken.  The kernel IR system will decode these remotes
>>> correctly without resorting to raw mode.
>>
>> A decoder like that should be a last-resort decoder, only in the
>> cases where there's no other option.
>>
>>>> There are some good reasons for that, as it would allow in-kernel support for
>>>> protocols that may have some patent restrictions on a few countries that allow
>>>> patents on software.
>>>
>>> Are there any IR protocols less than 20 (or 17) years old?
>>
>> Yes. This protocol is brand new:
>> 	https://www.smkusa.com/usa/technologies/qp/
>>
>> And several new devices are starting to accept it.
> 
> The US patent appears to have been filed in 1995 and granted in 1997, so
> "brand new" is relative. ;)

Yes, I saw the patent timestamps too ;) Yet, AFAIK, they're starting to use this protocol
on newer IR devices, so, we'll probably see some new devices using it.
> 
> http://www.freepatentsonline.com/5640160.html
> 
> We do have a few more years of being encumbered by it here in the US
> though. :(
> 

:(

Cheers,
Mauro.

  reply	other threads:[~2010-07-28 18:40 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 22:33 Can I expect in-kernel decoding to work out of box? Maxim Levitsky
2010-07-27 23:32 ` Maxim Levitsky
2010-07-28  1:29   ` Jon Smirl
2010-07-28  2:33     ` Jarod Wilson
2010-07-28  2:33       ` Jarod Wilson
2010-07-28  6:30       ` Maxim Levitsky
2010-07-28  6:59         ` Maxim Levitsky
2010-07-28 10:40         ` Jon Smirl
2010-07-28 10:40           ` Jon Smirl
2010-07-28 13:13           ` Mauro Carvalho Chehab
2010-07-28 13:46             ` Jon Smirl
2010-07-28 14:38               ` Andy Walls
2010-07-28 14:53                 ` Jon Smirl
2010-07-28 14:53                   ` Jon Smirl
2010-07-28 15:42                   ` Mauro Carvalho Chehab
2010-07-28 17:02                     ` Andy Walls
2010-07-28 17:35                       ` Jon Smirl
2010-07-28 18:18                         ` Andy Walls
2010-07-28 20:13                           ` Mauro Carvalho Chehab
2010-07-28 20:27                             ` Maxim Levitsky
2010-07-29  2:36                             ` Andy Walls
2010-07-29 11:58                               ` Jon Smirl
2010-07-28 18:29                       ` Mauro Carvalho Chehab
2010-07-28 14:24             ` Maxim Levitsky
2010-07-28 14:41               ` Jon Smirl
2010-07-28 15:18                 ` Jarod Wilson
2010-07-28 15:18                   ` Jarod Wilson
2010-07-28 15:56                 ` Mauro Carvalho Chehab
2010-07-28 17:04                   ` Jon Smirl
2010-07-28 17:21                     ` Andy Walls
2010-07-28 17:38                       ` Jon Smirl
2010-07-28 18:35                         ` Mauro Carvalho Chehab
2010-07-28 18:08                     ` Mauro Carvalho Chehab
2010-07-28 18:05                       ` Jarod Wilson
2010-07-28 18:40                         ` Mauro Carvalho Chehab [this message]
2010-07-28 21:01               ` Maxim Levitsky
2010-07-28 21:35                 ` 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=4C5079AC.9030006@redhat.com \
    --to=mchehab@redhat.com \
    --cc=jarod@redhat.com \
    --cc=jarod@wilsonet.com \
    --cc=jonsmirl@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=maximlevitsky@gmail.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.