Skip to contentSkip to conversation

Problem with calibration of AT91SAM9M10EKES

DISCUSSION Ulf Samuelsson 3 participants 5 messages Jan 26, 2011

lore
Share & tools
lore
#0 lore raw

Hi,
I have some calibration problem with my private branch (ulf/linux-2.6.30-2011-01-??) when building the at91sam9m10ekes board.

I am running /usr/bin/run-calibrate.sh,
but regardless of how I click, during calibration,
a tap afterwards always results in detection 3 mm above the tap.

There is a "pointercal" file generated.
It appears to me that this is ignored...
I can tap 1 cm above or below during calibration, and still the detected tap is 3 mm above the actual tap.

I tried this on two boards, with the same problem!

I looked at 89xTs_Calibrate
There is no /etc/init.d/devmand - What does this file do?

Anything else to think about?
I enclose /etc/X11/xorg.conf and /etc/ts.conf.

----------------------------------------------------
xorg.conf:

Section "ServerLayout"
Identifier "default"
InputDevice "atmel-tsadcc" "CorePointer"
EndSection

Section "InputDevice"
Identifier "atmel-tsadcc"
Driver "evdev"
Option "Device" "/dev/input/touchscreen0"
EndSection

Section "InputDevice"

    Driver        "mouse"
    Identifier    "Mouse[1]"
    Option        "Buttons"    "10"
    Option        "Device"    "/dev/input/mice"

EndSection

Section "InputDevice"

    Driver        "kbd"
    Identifier    "Keyboard[0]"
    Option        "Protocol" "Standard"

EndSection

----------------------------------------------------
ts.conf:
# Uncomment if you wish to use the linux input layer event interface module_raw input

# Uncomment if you're using a Sharp Zaurus SL-5500/SL-5000d

# module_raw collie

# Uncomment if you're using a Sharp Zaurus SL-C700/C750/C760/C860

# module_raw corgi

# Uncomment if you're using a device with a UCB1200/1300/1400 TS interface

# module_raw ucb1x00

# Uncomment if you're using an HP iPaq h3600 or similar

# module_raw h3600

# Uncomment if you're using a Hitachi Webpad

# module_raw mk712

# Uncomment if you're using an IBM Arctic II

# module_raw arctic2

module pthres pmin=1
module variance delta=30
module dejitter delta=100
module linear

Signature · 2 lines
Best Regards
Ulf Samuelsson
#1 lore raw

Dnia środa, 26 stycznia 2011 o 10:40:25 Ulf Samuelsson napisał(a):

Quoted 7 lines

I have some calibration problem with my private branch (ulf/linux-2.6.30-2011-01-??) when building the at91sam9m10ekes board.

I am running /usr/bin/run-calibrate.sh,
but regardless of how I click, during calibration,
a tap afterwards always results in detection 3 mm above the tap.

Quoted 7 lines

There is a "pointercal" file generated.
It appears to me that this is ignored...
I can tap 1 cm above or below during calibration, and still the detected tap is 3 mm above the actual tap.

Anything else to think about?
I enclose /etc/X11/xorg.conf and /etc/ts.conf.

You are using full X11 with evdev driver so tslib is not used at all. You have to use xinput-calibrator.

Regards,

Signature · 3 lines
JID:      [email protected]
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
#2 lore raw

2011-01-26 14:01, Marcin Juszkiewicz skrev:

Quoted 13 lines

Dnia środa, 26 stycznia 2011 o 10:40:25 Ulf Samuelsson napisał(a):

Quoted 11 lines

I have some calibration problem with my private branch (ulf/linux-2.6.30-2011-01-??) when building the at91sam9m10ekes board.

I am running /usr/bin/run-calibrate.sh,
but regardless of how I click, during calibration,
a tap afterwards always results in detection 3 mm above the tap.

There is a "pointercal" file generated.
It appears to me that this is ignored...
I can tap 1 cm above or below during calibration, and still the detected tap is 3 mm above the actual tap.

Quoted 6 lines
Quoted 2 lines

Anything else to think about?
I enclose /etc/X11/xorg.conf and /etc/ts.conf.

You are using full X11 with evdev driver so tslib is not used at all. You have to use xinput-calibrator.

Regards,

Hmm, I thought I was using xserver-kdrive!

(Have PREFERRED_PROVIDER_xserver = "xserver-kdrive" in the machine conf file)

Looking closer at the image (x11-at91sam9-image), it contains

XSERVER = "xserver-xorg \
           xf86-input-evdev \
           xf86-input-tslib \
           xf86-video-fbdev "

so the xserver-kdrive is overridden.

This was copied from "xorg-image.bb" which I guess then have the same problem using full x-server and tslib.
"qt4-x11-base-image.bb" has this combination as well.

"xserver-common_1.33.bb" is built and contains:
+++++++++++++++++++++++++
RDEPENDS_${PN}_append_angstrom = " tslib-calibrate " RDEPENDS_${PN}_append_shr = " xinput-calibrator "
-----------------------------------------------------
and I am building "angstrom" I do not get "xinput-calibrator"

I added xinput-calibrate to the x11-at91sam9-image, but after the build, Removed "xf86-input-tslib", but the dependence on "tslib-calibrate" remains in "xserver-common_1.33.bb"
Maybe this needs to change as well.

I get the same startup calibration program ("run-calibrate.sh" calling ts_calibrate). with the same poor result.

There are no scripts calling "xinput-calibrator".
Shouldn't that happen at startup?

Can call it manually, and then suddenly I am much better off. Still it not perfect though.

Any clue to get xinput-calibrate to run at first boot?

Best Regards
Ulf Samuelsson

#3 lore raw
Quoted 14 lines · Ulf Samuelsson

2011-01-26 14:01, Marcin Juszkiewicz skrev:

Quoted 13 lines

Dnia środa, 26 stycznia 2011 o 10:40:25 Ulf Samuelsson napisał(a):

Quoted 11 lines

I have some calibration problem with my private branch (ulf/linux-2.6.30-2011-01-??) when building the at91sam9m10ekes board.

I am running /usr/bin/run-calibrate.sh,
but regardless of how I click, during calibration,
a tap afterwards always results in detection 3 mm above the tap.

There is a "pointercal" file generated.
It appears to me that this is ignored...
I can tap 1 cm above or below during calibration, and still the detected tap is 3 mm above the actual tap.

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

Anything else to think about?
I enclose /etc/X11/xorg.conf and /etc/ts.conf.

You are using full X11 with evdev driver so tslib is not used at all. You have to use xinput-calibrator.

Regards,

Any clue to get xinput-calibrate to run at first boot?

provide
recipes/xinput-calibrator/pointercal-xinput
data for your device and use recipes/xserver-common/files/89xTs_Calibrate.xinput_calibrator.patch like SHR does

intentionaly it prefers provideded data, because users too often messed initial calibration on first boot and then didn't know how to reset it and rerun xinpu-calibration successfully...

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#4 lore raw

2011-01-26 21:06, Martin Jansa skrev:

Quoted 19 lines · Ulf Samuelsson
Quoted 18 lines

2011-01-26 14:01, Marcin Juszkiewicz skrev:

Quoted 17 lines

Dnia s'roda, 26 stycznia 2011 o 10:40:25 Ulf Samuelsson napisa?(a):

Quoted 7 lines

I have some calibration problem with my private branch (ulf/linux-2.6.30-2011-01-??) when building the at91sam9m10ekes board.

I am running /usr/bin/run-calibrate.sh,
but regardless of how I click, during calibration,
a tap afterwards always results in detection 3 mm above the tap.

Quoted 6 lines

There is a "pointercal" file generated.
It appears to me that this is ignored...
I can tap 1 cm above or below during calibration, and still the detected tap is 3 mm above the actual tap. Anything else to think about?
I enclose /etc/X11/xorg.conf and /etc/ts.conf.

You are using full X11 with evdev driver so tslib is not used at all. You have to use xinput-calibrator.

Quoted 7 lines
Quoted 2 lines
Quoted 1 line

Regards,

Any clue to get xinput-calibrate to run at first boot?

provide
recipes/xinput-calibrator/pointercal-xinput
data for your device and use recipes/xserver-common/files/89xTs_Calibrate.xinput_calibrator.patch like SHR does

OK, then is the question how:
As I noted:
SRC_URI_append_angstrom = " file://xtscal-fix.patch " RDEPENDS_${PN}_append_angstrom = " tslib-calibrate " RDEPENDS_${PN}_append_shr = " xinput-calibrator "?

so Angstrom (which I am using) is using "tslib-calibrate" Is there any drawback in changing this to " xinput-calibrator "

Adding a SRC_URI_append_at91 seems a kludge.

Quoted 10 lines

intentionaly it prefers provideded data, because users too often messed initial calibration on first boot and then didn't know how to reset it and rerun xinpu-calibration successfully...

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Signature · 2 lines
Best Regards
Ulf Samuelsson