From: Jon Smirl <jonsmirl@gmail.com>
To: "David Härdeman" <david@hardeman.nu>
Cc: Andy Walls <awalls@md.metrocast.net>,
Jarod Wilson <jarod@wilsonet.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
linux-input@vger.kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 00/15] ir-core: Several improvements to allow adding LIRC and decoder plugins
Date: Sat, 24 Apr 2010 17:59:46 -0400 [thread overview]
Message-ID: <v2z9e4733911004241459jd637bec0g5d76b24a611c3863@mail.gmail.com> (raw)
In-Reply-To: <20100424212353.GB11879@hardeman.nu>
On Sat, Apr 24, 2010 at 5:23 PM, David Härdeman <david@hardeman.nu> wrote:
> I don't care either way. Get the input maintainers to agree and I'll
> happily write patches that follow that approach (writing TX data to the
> input dev will also have to be supported).
>
> The only real problem I see is if we implement > 1 input device per
> rc/ir device (which I think we should do - each logical remote should
> have a separate keytable and input device).
I forgot about the many to 1 aspect of the receiver. You should have
started off with this point and I would have shut up, DRM does not
have many to 1 mappings. My radio receivers show up as network
devices. So I have multiple devices too.
I don't think we want a 'rc' device. The IR transceiver should be an
'ir' device. My radios are already 'net' devices. So my complaint
really is, I don't want an three devices - input, rc and net.
--
Jon Smirl
jonsmirl@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-24 21:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 17:56 [PATCH 00/15] ir-core: Several improvements to allow adding LIRC and decoder plugins Mauro Carvalho Chehab
2010-04-02 1:44 ` Jon Smirl
2010-04-02 10:20 ` David Härdeman
2010-04-05 20:49 ` Jarod Wilson
2010-04-07 9:32 ` David Härdeman
2010-04-23 17:40 ` Jarod Wilson
2010-04-23 18:06 ` Jon Smirl
2010-04-23 18:29 ` Mauro Carvalho Chehab
2010-04-23 22:20 ` Andy Walls
2010-04-24 5:22 ` David Härdeman
2010-04-24 12:35 ` Jon Smirl
2010-04-24 14:15 ` David Härdeman
2010-04-24 15:07 ` Jon Smirl
2010-04-24 21:23 ` David Härdeman
2010-04-24 21:59 ` Jon Smirl [this message]
2010-04-24 5:12 ` David Härdeman
2010-04-28 4:32 ` Jarod Wilson
2010-05-25 21:05 ` Jarod Wilson
2010-05-26 18:28 ` Jarod Wilson
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=v2z9e4733911004241459jd637bec0g5d76b24a611c3863@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=awalls@md.metrocast.net \
--cc=david@hardeman.nu \
--cc=jarod@wilsonet.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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 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).