From: Jon Smirl <jonsmirl@gmail.com>
To: "David Härdeman" <david@hardeman.nu>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Andy Walls <awalls@md.metrocast.net>,
linux-input@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [RFC3] Teach drivers/media/IR/ir-raw-event.c to use durations
Date: Sat, 10 Apr 2010 08:16:00 -0400 [thread overview]
Message-ID: <y2t9e4733911004100516wf10a8c94lfb83e6503776222a@mail.gmail.com> (raw)
In-Reply-To: <20100410064801.GA2667@hardeman.nu>
On Sat, Apr 10, 2010 at 2:48 AM, David Härdeman <david@hardeman.nu> wrote:
> On Fri, Apr 09, 2010 at 11:00:41AM -0300, Mauro Carvalho Chehab wrote:
>> struct {
>> unsigned mark : 1;
>> unsigned duration :31;
>> }
>>
>> There's no memory spend at all: it will use just one unsigned int and it is
>> clearly indicated what's mark and what's duration.
>
> If all three of you agree on this approach, I'll write a patch to convert
> ir-core to use it instead.
Fine with me.
>
> --
> David Härdeman
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2010-04-10 12:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 11:39 [RFC3] Teach drivers/media/IR/ir-raw-event.c to use durations David Härdeman
2010-04-08 12:01 ` Mauro Carvalho Chehab
2010-04-08 12:21 ` Mauro Carvalho Chehab
2010-04-08 12:21 ` Mauro Carvalho Chehab
2010-04-09 11:25 ` Andy Walls
2010-04-09 12:31 ` Jon Smirl
2010-04-09 14:00 ` Mauro Carvalho Chehab
2010-04-09 15:14 ` Jon Smirl
2010-04-09 15:14 ` Jon Smirl
2010-04-09 20:44 ` Found NEC IR specification in NEC uPD6122 datasheet (Re: [RFC3] Teach drivers/media/IR/ir-raw-event.c to use durations) Andy Walls
2010-04-10 6:48 ` [RFC3] Teach drivers/media/IR/ir-raw-event.c to use durations David Härdeman
2010-04-10 6:48 ` David Härdeman
2010-04-10 11:56 ` Andy Walls
2010-04-10 12:10 ` Mauro Carvalho Chehab
2010-04-10 12:34 ` Andy Walls
2010-04-10 12:16 ` Jon Smirl [this message]
2010-04-10 0: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=y2t9e4733911004100516wf10a8c94lfb83e6503776222a@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=awalls@md.metrocast.net \
--cc=david@hardeman.nu \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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.