Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure [LWN.net]

From:		Jon Smirl <jonsmirl-AT-gmail.com>
To:		Mauro Carvalho Chehab <mchehab-AT-redhat.com>
Subject:		Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure
Date:		Thu, 26 Nov 2009 11:03:25 -0500
Cc:		Gerd Hoffmann <kraxel-AT-redhat.com>, Devin Heitmueller <dheitmueller-AT-kernellabs.com>, Jarod Wilson <jarod-AT-wilsonet.com>, Krzysztof Halasa <khc-AT-pm.waw.pl>, Christoph Bartelmus <lirc-AT-bartelmus.de>, awalls-AT-radix.net, dmitry.torokhov-AT-gmail.com, j-AT-jannau.net, jarod-AT-redhat.com, linux-input-AT-vger.kernel.org, linux-kernel-AT-vger.kernel.org, linux-media-AT-vger.kernel.org, superm1-AT-ubuntu.com
Archive-link:		Article, Thread

BTW, we used to have device specific user space interfaces for mouse
and keyboard. These caused all sort of problems. A lot of work went
into unifying them under evdev.  It will be years until the old,
messed up interfaces can be totally removed.

I'm not in favor of repeating the problems with a device specific user
space interface for IR. I believe all new input devices should
implement the evdev framework.

-- 
Jon Smirl
jonsmirl@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

(Log in to post comments)