Thread (36 messages) 36 messages, 12 authors, 2009-11-30

Re: [RFC] What are the goals for the architecture of an in-kernel IR system?

From: Jon Smirl <hidden>
Date: 2009-11-28 17:37:40
Also in: linux-media, lkml

Possibly related (same subject, not in this thread)

On Sat, Nov 28, 2009 at 12:35 PM, Krzysztof Halasa [off-list ref] wrote:
Jon Smirl [off-list ref] writes:
quoted
There are two very basic things that we need to reach consensus on first.

1) Unification with mouse/keyboard in evdev - put IR on equal footing.
2) Specific tools (xmodmap, setkeycodes, etc or the LIRC ones) or
generic tools (ls, mkdir, echo) for configuration
I think we can do this gradually:
1. Merging the lirc drivers. The only stable thing needed is lirc
  interface.
Doing that locks in a user space API that needs to be supported
forever. We need to think this API through before locking it in.
2. Changing IR input layer interface ("media" drivers and adding to lirc
  drivers).
--
Krzysztof Halasa


-- 
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help