Hi all,
there are now Angstrom testing images available at
http://www.angstrom-distribution.org/unstable/images/simpad/
They are based on kernel 2.6 which is under development. The apm bug is still not solved and some other things are not working [1]. So this image is for testing only and not for every day usage.
regards
mr nice
1 http://opensimpad.org/index.php/SIMpad_Kernel_2.6
Full Version: Angstrom Simpad Test Images
OESF Forums > Distros, Development, and Model Specific Forums > Model Specific Forums > SIMpad forum
Hi mr_nice,
your image works amazingly well. Great work!
But i have a problem when calibrating the touchscreen. The calibration stops after a few taps and starts over and over again. After 5 or 6 times the calibration was successful (well kinda, the touchscreen is off a few centimeters but useable).
During calibration i got the following over serial console:
your image works amazingly well. Great work!
But i have a problem when calibrating the touchscreen. The calibration stops after a few taps and starts over and over again. After 5 or 6 times the calibration was successful (well kinda, the touchscreen is off a few centimeters but useable).
During calibration i got the following over serial console:
CODE
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 0, Value: 660
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 1, Value: 595
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 24, Value: 499
evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 24, Value: 0
evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
and so on...
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 1, Value: 595
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 24, Value: 499
evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 24, Value: 0
evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
and so on...
QUOTE(miip @ Apr 12 2007, 03:25 PM)
CODE
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 0, Value: 660
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 1, Value: 595
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 24, Value: 499
evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 24, Value: 0
evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
and so on...
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 1, Value: 595
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 24, Value: 499
evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: <NULL>, Type: 3, Code: 24, Value: 0
evbug.c: Event. Dev: <NULL>, Type: 0, Code: 0, Value: 0
and so on...
Hi,
thanks for testing.
The evbug.c stuff is normal and even good
. Evbug is activated for testing and it shows what the touchscreen and button driver are doning (which events they are sending to the input dev). Later this will be disabled.regards
nice
Ah thanks for the info. I figured it out myself, the second time i bootet. The first time i logged in as root and the debug output was gone.
But what about the strange calibration behavior? Is this kernel related or is it a angstrom bug?
But what about the strange calibration behavior? Is this kernel related or is it a angstrom bug?
Hi,
I had a similar behaviour with the touchscreen calibration: The calibration allways crashed when I typed on the cross in the lower right corner. However after removig the CF card from the PCMCIA slot the calibration worked well. Might that be a general issue?
Greetings
Thomas
I had a similar behaviour with the touchscreen calibration: The calibration allways crashed when I typed on the cross in the lower right corner. However after removig the CF card from the PCMCIA slot the calibration worked well. Might that be a general issue?
Greetings
Thomas
Hm, I also had this behavior on my pad. I will try to figgure out the reason.
regards
nice
regards
nice
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.