Hi Jon,
on 15 Feb 07 at 00:34, you wrote:
[...]
>> I'm only a bit concerned about scalability. It's easily possible to have
>> hundreds of remote control definitions in your lircd.conf. Creating a
>> device node for each of them will be very inefficient.
> I have about ten remotes and I thought t
Hi Jon,
on 14 Feb 07 at 09:44, you wrote:
[...]
> Adding uinput support would also let you get rid of all the X specific
> code since X knows how to read evdev.You just need to do is add a
> small section to your xorg.conf.
>
> Are your interested in adding this support?
Yes, I like the concept y
Hi Jon,
on 13 Feb 07 at 23:46, you wrote:
[...]
> evdev doesn't just handle keyboards.
Yes, sorry for simplifying it too much. I just opt for using uinput from
user-space so that configuration is consistent for all devices.
If some devices use the kernel input layer directly, you will have to
Hi!
Jon Smirl "[EMAIL PROTECTED]" wrote:
> LIRC folks, there is an on-going discussion about possible future
> designs for IR support in the kernel. What's your take on how to do
> this?
Pass all events to userspace and let lircd do the mapping/decoding.
In case of the atiusb device there are cu
