[mythtv-users] Trying To Get Two IR Receivers Working

Karl Newman newmank1 at asme.org
Wed Oct 14 17:23:09 UTC 2015


On Wed, Oct 14, 2015 at 10:08 AM, Hika van den Hoven <hikavdh at gmail.com>
wrote:

> Hoi Kirk,
>
> Wednesday, October 14, 2015, 6:55:07 PM, you wrote:
>
>
>
> > On 10/14/2015 9:32 AM, Alec Leamas wrote:
> >> The devinput LIRC driver does exactly this - acts as a bridge between
> >> the kernel decoding and the LIRC application interface. You feed the
> >> event device as the --device option to devinput, starts lircd and then
> >> uses irw. This is what's described in [2]
>
> > Ah, I did not change the "device=" setting in lirc_options.conf. I think
> > I thought it was saying what the device line the driver *created* at
> > startup. My bad.
>
> >>
> >> You can use udev rules to handle that the event device is not fixed as
> >> Karl described. However, it's not really necessary, see [1]
> >>
> >>
>
> > That's right. You told me about that before. I got sidetracked onto
> > other things. This device has a nice unique name so that:
>
> > device = name='*Spinel*'
>
> > Should work. Is it case sensitive?
> > _______________________________________________
> Yes.
> You need something like:
>

Actually, no, Alec was pointing out that lirc has a nice device name
matching feature built in so you don't need udev rules. But Kirk, make sure
your device parameter has no spaces. In other words,
--device=name="*Spinel*"
If you're using hardware.conf, it would look like
REMOTE_DEVICE="name='*Spinel*'" (note the single quotes inside, which I
think should work)

Karl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20151014/309baf10/attachment.html>


More information about the mythtv-users mailing list