linux-kernel - Re: [RFC PATCH 0/4] V3 - Implementation of IR support using the input subsystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 9 Oct 2008 14:03:33 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Jon Smirl <jonsmirl@...il.com>
Cc:	linux-kernel@...r.kernel.org, lirc-list@...ts.sourceforge.net
Subject: Re: [RFC PATCH 0/4] V3 - Implementation of IR support using the
	input subsystem

Hi!

>  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.  
 
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/