Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Mar 2007 11:51:04 -0400
From:      Joe Auty <joe@netmusician.org>
To:        Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no>,  freebsd-multimedia@freebsd.org
Subject:   Re: LIRC guide for FreeBSD
Message-ID:  <45FABCE8.20400@netmusician.org>
In-Reply-To: <20070315095424.GE11506@camelot.theinternet.com.au>
References:  <45F77267.9080403@netmusician.org>	<20070314054117.GB6688@wantadilla.lemis.com>	<7BADB2D8968E702424EAE969@ganymede.hub.org>	<45F88A52.7000809@netmusician.org>	<20070315080854.5232bb9b.torfinn.ingolfsen@broadpark.no> <20070315095424.GE11506@camelot.theinternet.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrew Milton wrote:
> +-------[ Torfinn Ingolfsen ]----------------------
> | On Wed, 14 Mar 2007 19:50:42 -0400
> | Joe Auty <joe@netmusician.org> wrote:
> |
> | > The piece I'm missing is getting LIRC listening on a device node so
> | > that it can communicate with my IR Blaster connected to my serial
> | > port.
> |
> | I *think* that the problem is related to the fact that IR Blasters are
> | using the serial port in a non-standard way.
> | Instead of using the Tx signal to transmit data, they are using the DTR
> | signal. This page seems to support that view:
> | http://www.lirc.org/transmitters.html
> |
> | Thus, you need a special driver for the serial port which allows it to
> | work in this way. It is probably a year or two since I looked at it,
> | but the problem then was that LIRC's "driver" for serial ports was
> | totally Linux-specific, not very clean code, and not easy to port over
> | to FreeBSD. So nobody did make a LIRC serial port driver for FreeBSD .
>
> You don't really "send" or "receive" data to and from IR devices.
>
> You don't really need a driver, you just need to be able to strobe the
control
> line at the right frequency, in the right burst lengths. You can do it
from userland
> if you need to.
>
> The serial drivers for LIRC simply monitor the relevant pin and decode the
> incoming data. You can do this in userland, without needing a lirc kernel
> module to watch the serial port.
>
> The reason they use the control lines instead of tx/rx is that you
don't need
> to be concerned with baud settings on the port.

Cool, so this is just a matter of software configuration then? Any
ideas how I can setup LIRC to do this?

- --
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
joe@netmusician.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF+rzoCgdfeCwsL5ERAg2hAJ4nlb50QgV1t+FQxaNwPVtmtXf/jwCgn5Uq
wmoTYwhLZjJ57Jtuqyen2sM=
=d+mX
-----END PGP SIGNATURE-----




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45FABCE8.20400>