public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Härdeman" <david@hardeman.nu>
To: Andy Walls <awalls@md.metrocast.net>
Cc: Jon Smirl <jonsmirl@gmail.com>, 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 07:22:54 +0200	[thread overview]
Message-ID: <20100424052254.GB3101@hardeman.nu> (raw)
In-Reply-To: <1272061228.3089.8.camel@palomino.walls.org>

On Fri, Apr 23, 2010 at 06:20:28PM -0400, Andy Walls wrote:
> Not that my commit rate has been > 0 LOC lately, but I'd like to see
> lirc_dev, just to get transmit worked out for the CX23888 chip and
> cx23885 driver.
> 
> I think this device will bring to light some assumptions LIRC currently
> makes about transmit that don't apply to the CX23888 (i.e. LIRC having
> to perform the pulse timing).  The cx23888-ir implementation has a kfifo
> for holding outgoing pulse data and the hardware itself has an 8 pulse
> measurement deep fifo.

I think we're eventually going to want to let rc-core create a chardev 
per rc device to allow for things like reading out scancodes (when 
creating keymaps for new and unknown remotes), raw timings (for 
debugging in-kernel decoders and writing new ones), possibly also 
ioctl's (for e.g. setting all RX parameters in one go or to 
create/destroy additional keymaps, though I'm sure some will want all of 
that to go through sysfs).

That same chardev could also be used to implement TX, once a suitable 
interface has been fleshed out. The end result might not look exactly 
like lirc...

-- 
David Härdeman

  reply	other threads:[~2010-04-24  5:22 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 [this message]
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
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=20100424052254.GB3101@hardeman.nu \
    --to=david@hardeman.nu \
    --cc=awalls@md.metrocast.net \
    --cc=jarod@wilsonet.com \
    --cc=jonsmirl@gmail.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