OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Angstrom Simpad Test Images
mr_nice
post Apr 8 2007, 05:18 AM
Post #1





Group: Members
Posts: 156
Joined: 21-September 05
Member No.: 8,161



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
Go to the top of the page
 
+Quote Post
miip
post Apr 12 2007, 03:25 PM
Post #2





Group: Members
Posts: 6
Joined: 21-August 05
Member No.: 7,914



Hi mr_nice,

your image works amazingly well. Great work! smile.gif

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...
Go to the top of the page
 
+Quote Post
mr_nice
post Apr 13 2007, 08:02 AM
Post #3





Group: Members
Posts: 156
Joined: 21-September 05
Member No.: 8,161



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...

*


Hi,
thanks for testing.
The evbug.c stuff is normal and even good smile.gif. 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
Go to the top of the page
 
+Quote Post
miip
post Apr 13 2007, 10:49 AM
Post #4





Group: Members
Posts: 6
Joined: 21-August 05
Member No.: 7,914



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. smile.gif

But what about the strange calibration behavior? Is this kernel related or is it a angstrom bug?
Go to the top of the page
 
+Quote Post
tduthel
post Apr 14 2007, 01:42 AM
Post #5





Group: Members
Posts: 16
Joined: 5-September 05
Member No.: 8,037



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
Go to the top of the page
 
+Quote Post
mr_nice
post Apr 14 2007, 03:15 AM
Post #6





Group: Members
Posts: 156
Joined: 21-September 05
Member No.: 8,161



Hm, I also had this behavior on my pad. I will try to figgure out the reason.
regards
nice
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 27th August 2014 - 09:17 PM