JOKE: I thought this read 'Re: drop acid!' or 'Re: drop lsd' Whoops, not so funny anymore... Michael Uman On Thu, 2003-08-07 at 10:17, Gerd Knorr wrote: > Johannes Stezenbach <js@xxxxxxxxxxxxxx> writes: > > > The DVB driver for WinTV Nexus-S (and similar cards) did that for quite > > a while now. We use it in conjunction with DirectFB (which reads events > > directly from /dev/input/eventX). I don't know how well it works for X. > > > - driver: linux-2.6.0-test2/drivers/media/dvb/ttpci/av7110_ir.c > > > AFAIK lirc allows one to control/configure which events get to which app, and > > how the app should react. This functionality is not replaced by this > > patch. lircd can die, but the lirc client lib should just read from > > /dev/input/event* instead from /dev/lircd. > > Yes, with lirc_client lib reading from /dev/input/eventx instead of > talking to lircd the switchover should be transparent for the lirc > apps. Can multiple apps read from /dev/input/event<x>? Do they all > see all events? > > > Putting IR events in keyboard queue might be asking for trouble. > > Well, I had a look at the driver mentioned above. How do you avoid > that the keyboard events end up in the console keyboard queue? Seems > your driver does basically the same mine does. Can the linux console > and/or input layer configured somehow to accept keyboard events from > some input devices only? > > Gerd
