Hi!

quoted text
>  What should the IR API look like?  How are IR events mapped into
> keyboard events? Should they be mapped? Map them in the kernel or in
> user space? The maps are tiny, less than 1K per remote.  Sysfs can
> be used to load maps into the kernel driver. Make maps only for the
> common buttons and don't map unusual ones?

Map them in kernel, in analogy with normal keyboards.  
 
quoted text
> How should multiple remotes be handled? Split them out into
> individual input devices, or group them onto a single IR device? I
> can implement either.

Individual input devices, I'd say... so that app can only listen for
'its' remote.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/