From: Yann V. <ya...@do...> - 2004-12-26 21:35:30
|
Hello, first time poster here. I messed about a bit with lircd the other night, finding to my delight that there was some support for "serial" remotes. That would be those using IR to send the same line protocol you'd normally expect on serial lines like RS-232. I have a keyboard of this type. However, I quickly found that there was no parity support, and I didn't manage to get consistent results from it, so I checked more in the source (nothing seems documented) and after not really getting the structure just rewrote my own code for the job. I then set about adding the keyboard to the input layer, eventually writing a dirty little program to listen to lircd and inject things in the Linux input layer using uinput. The results are available at http://donkey.dyndns.org/~yann/lirc/ in three files: TuxScreen_Keyboard.gz lircd.conf data for the keyboard serial.diff.gz lircd patch modifying serial data type for parity support lirc_uinput_keybd.tar.gz user space program to convert lirc events to keyboard presses I didn't use the lirc_client library because it frankly had nothing to offer but a horrid config file format. The lircd config file parser is among the most fragile I've ever seen - it breaks on comments with whitespace before them, for instance. That the official "documentation" points to *another site* wasn't very helpful when I was netless either. Anyhow, I hope you find something of what I wrote useful. --=20 PGP fingerprint =3D 9242 DC15 2502 FEAB E15F 84C6 D538 EC09 5380 5746 |