Re: Inject IR codes into LIRC? \ Can lirc read from a socket?

[Canavan, P. S \(UK - London\) <pca...@de...>]

>Just to get my understanding correct. You are injecting IR signals into =

>LIRC by having the LIRC daemon connect to your software via UDP as if =
it=20
>was connecting to another LIRC daemon. By imitating an LIRC daemon you=20
>can inject IR signals programmatically?

  I looked at using the LIRC protocol directly into the daemon, but it =
would require the "remote" to be always connected. Since I want to rig =
up an IP-based remote with the Nokia N800 as the handset, that wasn't =
sensible. Rather, I get LIRC to use the UDP driver, which expects raw =
remote data to come in at a specific port. This permits the remote to =
appear and disappear without LIRC even knowing, since everything is =
connectionless; either a given UDP packet arrives or it doesn't.

  I've been thinking of tidying the code up and going GPL on =
SourceForge, since there are now Java environments running on the N800, =
my C++ is fledgling (and I'm now too OOP to admit defeat and go back to =
C), and the Nokia dev environment has proved to be a pain already. =
What's your target; would GPL scupper you?

  As I said, I'm away from home at the moment, but I can drop you the =
code at the weekend when I get back home.


Philip.
=20
IMPORTANT NOTICE
If you have received this e-mail in error or wish to read our e-mail =
disclaimer statement and monitoring policy, please refer to the =
statement below or contact the sender.
This communication is from Deloitte MCS Limited whose registered office =
is at Hill House, 1 Little New Street, London EC4A 3TR, United Kingdom.  =
Registered in England No 3311052. =20
This communication and any attachments contain information which is =
confidential and may also be privileged.  It is for the exclusive use of =
the intended recipient(s).  If you are not the intended recipient(s) =
please note that any form of disclosure, distribution, copying or use of =
this communication or the information in it or in any attachments is =
strictly prohibited and may be unlawful.  If you have received this =
communication in error, please return it with the title "received in =
error" to IT....@de... then delete the email and =
destroy any copies of it.
E-mail communications cannot be guaranteed to be secure or error free, =
as information could be intercepted, corrupted, amended, lost, =
destroyed, arrive late or incomplete, or contain viruses.  We do not =
accept liability for any such matters or their consequences.  Anyone who =
communicates with us by e-mail is taken to accept the risks in doing so.
When addressed to our clients, any opinions or advice contained in this =
e-mail and any attachments are subject to the terms and conditions =
expressed in the governing Deloitte MCS Limited client engagement =
letter.
Opinions, conclusions and other information in this e-mail and any =
attachments which do not relate to the official business of the firm are =
neither given nor endorsed by it.