MobileRead Forums - View Single Post

NiLuJe · 07-26-2010, 01:41 PM

Good to know (I'm not familiar with the uinput module)!

If the framework itself is the only thing handling input events in the end, that shouldn't be too hard to implement. (That's what we do with fonts/ss, we setup things before the framework). If it's handled earlier/by low-level stuff, we'd have to dig a little bit deeper.

(If the code is looking for the input event devices file specifically by name, we can always tweak the udev rules).

If something's grabbing the input devices in userland, lsof will tell what process is handling things.

07-26-2010, 01:41 PM	#7
NiLuJe BLAM! Posts: 13,506 Karma: 26047190 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Good to know (I'm not familiar with the uinput module)! If the framework itself is the only thing handling input events in the end, that shouldn't be too hard to implement. (That's what we do with fonts/ss, we setup things before the framework). If it's handled earlier/by low-level stuff, we'd have to dig a little bit deeper. (If the code is looking for the input event devices file specifically by name, we can always tweak the udev rules). If something's grabbing the input devices in userland, lsof will tell what process is handling things. Last edited by NiLuJe; 07-26-2010 at 01:44 PM.