Motion Sensor driver has some problems in boot from SD

Miles Hsieh miles_hsieh at
Tue Feb 26 12:14:04 CET 2008

Dear Andy & Willie:

I told you that motion sensor driver has some problems in one phone.
I list the testing result:

/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1 $ cat 
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="Neo1973 Buttons"
P: Phys=neo1973kbd/input0
S: Sysfs=/devices/platform/neo1973-button.0/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=23
B: KEY=200 0 800000 0 0 0
B: SW=4

I: Bus=0013 Vendor=dead Product=beef Version=0101
N: Name="s3c2410 TouchScreen"
P: Phys=
S: Sysfs=/devices/virtual/input/input1
U: Uniq=
H: Handlers=event1
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=1000003

I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="GTA02 PMU events"
S: Sysfs=/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/input/input2
U: Uniq=
H: Handlers=kbd event2
B: EV=400003
B: KEY=10 0 0 0 1000 0 0 0 100000 0 0 0

/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1 $ hexdump /dev/input/event2

==> When I use "hexdump /dev/input/event2", it has no response.

/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1 $ hexdump /dev/input/event3
hexdump: /dev/input/event3: No such device
hexdump: /dev/input/event3: Bad file descriptor

=> But /dev/input exist event2 & event3

/dev/input $ ls
event0        event2        event4        touchscreen0
event1        event3        mice

Best Regards,
---- Miles ----

More information about the openmoko-kernel mailing list