From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "David Härdeman" <david@hardeman.nu>
Cc: Jarod Wilson <jarod@wilsonet.com>,
Jarod Wilson <jarod@redhat.com>,
linux-media@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] Apple remote support
Date: Thu, 04 Nov 2010 15:43:33 -0400 [thread overview]
Message-ID: <4CD30CE5.5030003@redhat.com> (raw)
In-Reply-To: <20101104193823.GA9107@hardeman.nu>
Em 04-11-2010 15:38, David Härdeman escreveu:
> On Thu, Nov 04, 2010 at 11:54:25AM -0400, Jarod Wilson wrote:
>> Okay, so we seem to be in agreement for an approach to handling this.
>> I'll toss something together implementing that RSN... Though I talked
>> with Mauro about this a bit yesterday here at LPC, and we're thinking
>> maybe we slide this support back over into the nec decoder and make it
>> a slightly more generic "use full 32 bits" NEC variant we look for
>> and/or enable/disable somehow. I've got another remote here, for a
>> Motorola cable box, which is NEC-ish, but always fails decode w/a
>> checksum error ("got 0x00000000", iirc), which may also need to use
>> the full 32 bits somehow... Probably a very important protocol variant
>> to support, particularly once we have native transmit support, as its
>> used by plenty of cable boxes on the major carriers here in the US.
>
> I've always found the "checksum" tests in the NEC decoder to be unnecessary so I'm all for using a 32 bit scancode in all cases (and still using a module param to squash the ID byte of apple remotes, defaulting to "yes").
>
This means changing all existing NEC tables to have 32 bits, and add
the "redundant" information on all of them. It doesn't seem a good idea
to me to add a penalty for those NEC tables that follow the standard.
Mauro
next prev parent reply other threads:[~2010-11-04 19:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 3:11 [RFC PATCH 0/2] Apple remote support Jarod Wilson
2010-10-29 3:13 ` [RFC PATCH 1/2] ir-nec-decoder: decode Apple's NEC remote variant Jarod Wilson
2010-10-29 22:15 ` Andy Walls
2010-10-29 3:13 ` [RFC PATCH 2/2] IR: add Apple remote keymap Jarod Wilson
2010-10-29 3:15 ` [RFC PATCH 0/2] Apple remote support Jarod Wilson
2010-10-29 13:46 ` Mauro Carvalho Chehab
2010-10-29 15:11 ` Jarod Wilson
2010-10-29 19:17 ` David Härdeman
2010-10-29 19:27 ` Jarod Wilson
2010-10-29 19:59 ` David Härdeman
2010-10-29 20:09 ` Jarod Wilson
2010-10-30 23:36 ` David Härdeman
2010-10-31 2:32 ` Jarod Wilson
2010-11-01 21:56 ` David Härdeman
2010-11-02 20:42 ` Jarod Wilson
2010-11-04 12:16 ` David Härdeman
2010-11-04 15:54 ` Jarod Wilson
2010-11-04 19:38 ` David Härdeman
2010-11-04 19:43 ` Mauro Carvalho Chehab [this message]
2010-11-05 13:27 ` David Härdeman
2010-11-05 14:04 ` Christopher Harrington
2010-11-07 19:01 ` Jarod Wilson
2010-11-15 4:11 ` Jarod Wilson
2010-11-15 18:39 ` David Härdeman
2010-11-16 12:08 ` Mauro Carvalho Chehab
2010-11-16 23:26 ` David Härdeman
2010-11-18 16:33 ` Jarod Wilson
2010-11-18 20:43 ` David Härdeman
2010-11-18 20:49 ` Jarod Wilson
2010-11-18 20:59 ` Mauro Carvalho Chehab
2010-11-19 23:55 ` David Härdeman
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=4CD30CE5.5030003@redhat.com \
--to=mchehab@redhat.com \
--cc=david@hardeman.nu \
--cc=jarod@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).