All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helmut Auer <vdr@helmutauer.de>
To: Jarod Wilson <jarod@wilsonet.com>
Cc: linux-media@vger.kernel.org
Subject: Re: v4l-dvb - Is it still usable for a distribution ?
Date: Mon, 07 Jun 2010 23:25:03 +0200	[thread overview]
Message-ID: <4C0D63AF.7090203@helmutauer.de> (raw)
In-Reply-To: <AANLkTinisZ5DtH1Izn6WZS8isrF_G3oFZuppoHuwhlUj@mail.gmail.com>

Hi
> ...
>>> Another problem (after fixing the compile issues) is the IR Part of v4l-dvb which includes an Imon module.
>>> This module doesn't provide any lirc devices, so how can this oe be used as an IR device ?
>>
>> You don't need lirc to use imon, since it now provides a standard input/event interface. So, the driver
>> currently can be used with lirc event interface, or alone.
> 
> See http://wilsonet.com/jarod/imon_stuff/imon-devinput-lirc/ for the
> config I use w/my own imon hardware.
> 
Tanks for the hint !

>>> Til now I am using lirc_imon which fit all my needs.
>>
>> Lirc-dev patches are currently being discussed. There are just a few adjustments on it, in order to get it
>> finally merged. The kernel-userspace interface will likely need a few changes, so you'll likely need to update
>> lirc after the merge. Better to follow the IR threads at linux-media ML, in order to be in-tune with the changes.
> 
> I've considered adding lirc_dev support back to the imon driver when
> we get it merged, but it really doesn't make a whole lot of sense,
> given that the imon devices do all IR decoding in hardware. As long as
> the keymap is complete, there's no benefit to wiring up lirc_dev vs.
> just using lircd's devinput access method for imon devices.
> 
You're right, also inputlircd can do the job.

Is your imon driver fully compatible with the lirc_imon in the display part ?

It would be very helpful to add a parameter for disabling the IR Part, I have many users which
are using only the display part.

-- 
Helmut Auer, helmut@helmutauer.de

  reply	other threads:[~2010-06-07 21:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 11:27 v4l-dvb - Is it still usable for a distribution ? vdr
2010-06-07 13:16 ` Mauro Carvalho Chehab
2010-06-07 13:49   ` Jarod Wilson
2010-06-07 21:25     ` Helmut Auer [this message]
2010-06-08  3:40       ` Jarod Wilson
2010-06-08  4:25         ` Helmut Auer
2010-06-08  8:56         ` vdr
2010-06-08 14:50           ` Mauro Carvalho Chehab
2010-06-07 21:33   ` Helmut Auer
2010-06-07 22:08     ` 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=4C0D63AF.7090203@helmutauer.de \
    --to=vdr@helmutauer.de \
    --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 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.