From: Buzz <bu...@os...> - 2006-02-10 14:29:56
|
> When I cat the device, it spits out some junk and then stops. > `tail -f` doesn't seem to work any better. Well, that's a good sign, it means the hardware is working. > However, once I figured out how to use irrecord, it does look > like I might be able to come up with something, assuming I > can actually make it all the way through (I think I was > moving too slowly and it kept exiting). Will try over my > lunch break since I really shouldn't be playing with this > when I'm supposed to be working. Good. If it's aborting/exiting on you, then you may find you can create a few partial lircd.conf files, and manually edit them together for a complete config file solution. > > Anyway, assuming this all works, is there anything special I > need to know to configure mouse events (the kb has an > integrated mouse)? Also, is there a way to have lirc send > some events as if it was a normal /dev/input type keyboard? Keyboard with integrated mouse? Interesting. Well, perhaps you can get the integrated mouse to be detected as "keystrokes" while doing irrecord (scroll up = keypress, scroll down = anotherkeypress, etc), and then have these "keystrokes" passed to "lircmd" (the lirc mouse daemon) to interpres these as X-windows mouse events? That's just a guess though. YMMV. Let us now how you go. Buzz. |