I've been lurking for a few months, but thought I'd chime in here...
I have a home automation Linux box in the basement, and I have several
different TVs, VCRs and stereos around the house. I'd like to have my
entire system setup so that I have (1) a single receiver in the
livingroom with multiple tranmitters for multiple devices (stereo, TV,
two different VCRs, DVD, etc); (2) a single receiver and single
transmitter in the basement (TV, VCR, etc); (3) a single receiver and
single tranmitter in the bedroom (TV, VCR, etc); (4) etc... What I'd
like is to have each room on a different serial port, so that I can
distinguish between the IR codes that are received from (and sent to)
the livingroom verses the basement verses the bedroom. This way I could
route audio sources to different rooms depending what codes are received
I get the impression that this is not possible with the current LIRC, or
am I wrong here?
Christoph Bartelmus wrote:
> Blars Blarson "blarson@..." wrote:
> >> If the answer to the above is no, then is it possible to use a second
> >> serial port for the second receiver?
> > This is not trivial with the current driver code. This realy should
> > be rewritten to allow multiple lirc_serial ports on one system.
> Do we really need this?
> We are currently thinking (Manuel actually has already started) about a
> clean-up of the LIRC kernel interface and one major design decision will
> be if we really need a major number or if a misc-minor will be sufficient
> for the kernel drivers. In the latter case you will always be restricted
> to at most one infrared receiver per system. Currently I'm not really
> conviced that for such kind of interface that the infrared remote control
> is, you will really need several receivers.
> Can anybody give good examples that will justify the need for several
> receivers per system.
> This sf.net email is sponsored by:
> Access Your PC Securely with GoToMyPC. Try Free Now