On Friday 26 December 2008 21:38:14 Andy Green wrote:
> | for evdev and the calibration data?
>
> It's a good point, is there a way to associate the input event device
> that sends coordinates with the way that you set its calibration?
With tslib? Yes. in the ts.conf you define which input_raw which device to use
and then stack modules and its configuration on top.
> Now the arrangements in kernel that are specific to the touchscreen
> shipped give great data already, tslib seems needless. If I understood
> what Nelson is asking, it's just about removing tslib from inbetween the
> input subsystem data and XGlamo. Not -->
I'm glad that you respond here because I have a couple of issues with the
current version (as much as I understand it):
- XCalibrate Extension -> broken, so user recalibration is not working
- We require custom machine specific code/shell/script to find the
device and
set the calibration data (e.g. the ts could be on serial as well..) which is a
step back from a different ts.conf and pointercal... So you need a stable
general purpose interface to configure such things (enumerable as well...)
- Tools like ts_test, ts_print and ts_print_raw are not working. So far
they
have been valuable tools in bring up of touchscreens. But I'm willing to learn
new tools if they exist.
- Gosh I get old.... but why do we want to throw something away and
replace
it with something that is not yet ready? Is there a roadmap to address to the
above points and establish a stable kernel<->user config?
- Currently (from the sysfs interface) it looks like all this is
implemented
in one driver, with a userspace hat on I would like to wait until this is more
generalized, with my kernel hat and iPAQ history I would be surprised if a in
kernel calibration, linearisation will end in the kernel.
have fun
z.
_______________________________________________
devel mailing list
[email protected]
https://lists.openmoko.org/mailman/listinfo/devel
