| 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
| ||
|
Date: Sat, 28 Nov 2009 15:46:01 -0500 From: Jon Smirl <jonsmirl@...il.com> To: Stefan Richter <stefanr@...6.in-berlin.de> Cc: Christoph Bartelmus <lirc@...telmus.de>, khc@...waw.pl, awalls@...ix.net, dmitry.torokhov@...il.com, j@...nau.net, jarod@...hat.com, jarod@...sonet.com, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org, linux-media@...r.kernel.org, maximlevitsky@...il.com, mchehab@...hat.com, superm1@...ntu.com Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? On Sat, Nov 28, 2009 at 3:29 PM, Stefan Richter <stefanr@...6.in-berlin.de> wrote: > Jon Smirl wrote: >> On Sat, Nov 28, 2009 at 2:45 PM, Stefan Richter >> <stefanr@...6.in-berlin.de> wrote: >>> Jon Smirl wrote: >>>> Also, how do you create the devices for each remote? You would need to >>>> create these devices before being able to do EVIOCSKEYCODE to them. >>> The input subsystem creates devices on behalf of input drivers. (Kernel >>> drivers, that is. Userspace drivers are per se not affected.) >> >> We have one IR receiver device and multiple remotes. How does the >> input system know how many devices to create corresponding to how many >> remotes you have? > > If several remotes are to be used on the same receiver, then they > necessarily need to generate different scancodes, don't they? Otherwise > the input driver wouldn't be able to route their events to the > respective subdevice. But if they do generate different scancodes, > there is no need to create subdevices just for EVIOCSKEYCODE's sake. (It > might still be desirable to have subdevices for other reasons perhaps.) Multiple remotes will have duplicate buttons (1, 2 ,3, power, mute, etc) these should get mapped into the standard keycodes. You need to devices to key things straight. Push button 1 on Remote A. That should generate a KP_1 on the evdev interface for that remote. Push button 1 on Remote B. That should generate a KP_1 on the evdev interface for that remote. Scenario for this - a mutifunction remote that is controlling two different devices/apps. In one mode the 1 might be a channel number, in the other mode it might be a telephone number. The user may chose to make button 1 on both remote A/B map to KP_1 on a single interface. Scenario for this - I want to use two different remotes to control a single device. --------------------- I handled that in configds like this: /configfs - mount the basic configfs /configfs/remotes (created by loading IR support) mkdir /configfs/remotes/remote_A - this causes the input subdevice to be created, the name of it appears in the created directory. --- this entry really shouldn't be called "remote" it should be named "application" . Then you build map entries under it for the keycodes the app knows about. Nothing prevents you from adding entries that map both Remote_A_1 and Remote_B_1 to KP_1. -- it's not sufficient to support a single application. I might be running mythtv, a voip phone, home automation, etc all using a remote. By switching modes on a multifunction remote I can switch apps. mkdir /configfs/remotes/remote_A/... - now build the mapping entires. > -- > Stefan Richter > -=====-==--= =-== ===-- > http://arcgraph.de/sr/ > -- Jon Smirl jonsmirl@...il.com -- 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/
Powered by blists - more mailing lists