View Single Post
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#19
Drew up some keyboard layouts for the frontend. Turned out that the easiest way to get something that is nice to look at was to grab a screenshot of landscape mode message editor and tune it up with gimp.

I have to go back on my previous claim that the touchscreen device is implemented in twl4030_pwrbutton module.
Actually it is built-in in the kernel and what confused me was just the different loading order of different modules I experimented with gave same contradictory results. It was quite difficult to try to create code that works on the bare bones of the device when you have to tweak something, boot it and see how it works. (and at the same time try to be careful to keep the device is such a state that it WILL boot and not brick )

However, after a lot of this I thought about it a bit, and decided to try to get the unit boot into single user mode. The problem is that N9 has neither keyboard nor serial port, but what I did was launch sshd with some tweaky parameters to listen on the USB/ETH connection.
This works quite nicely, and even though it is not really traditional "single user mode" as I am able to reconnect multiple times, it is close enough, I can halt the boot before init and tweak on the console as much as I please

So, it turns out that these devices are built-in;

Code:
(none)-21-3_PR_001:~# 
(none)-21-3_PR_001:~# ls -l /dev/input
total 0
crw-------    1 root     root       13,  64 Jan  1  1970 event0
crw-------    1 root     root       13,  65 Jan  1  1970 event1
crw-------    1 root     root       13,  66 Jan  1  1970 event2
crw-------    1 root     root       13,  67 Jan  1  1970 event3
(none)-21-3_PR_001:~# 
(none)-21-3_PR_001:~# 
(none)-21-3_PR_001:~# dmesg | grep input
[    0.159332] input: ECI Accessory as /devices/virtual/input/input0
[    0.227447] input: dfl61-twl4030 Jack as /devices/platform/soc-audio.0/sound/card0/input1
[    0.233795] input: gpio-keys as /devices/platform/gpio-keys/input/input2
[    0.241821] input: Atmel mXT Touchscreen as /devices/platform/i2c_omap.2/i2c-2/2-004b/input/input3
(none)-21-3_PR_001:~#


There is still something that bugs me about the vibration device, though.
When the mobile is running full up OS then I can access it via character device 13,69 (as /dev/input/event5 or whatever) but when I am in preinit phase the damn device produces nothing.

I have loaded the "vibra_spi" up with and without the keypad driver, and still, there is no vibra effect when I tickle it.
However, when I am runnin OS, the device tickles nicely.
What is going on here, is there some other module it depends on that needs to be loaded with it to make it work?
 

The Following 2 Users Say Thank You to juiceme For This Useful Post: