Thank you for response,
Am Sonntag, 23. Februar 2003 18:29 schrieb Thomas Zander:
> I am far from knowledgable on XFree, but for a laptop a friend of mine
> wrote a calibration tool that had the same problems.
> The problem was 'solved' by writing the changes in XF86Config and
> restarting X.
I do the same, but it's unhandy. :-(
>
> An idea I heard here a week ago was to let the driver open a different
> file (a device or a special made file for the purpose) and check if it has
> been written to just like (for example) is done with the serial port.
> Its ugly; but if it works, you don't hear me complaining.
I have seen such a solution on a gunze driver. Calibartion data is writen to a
extra file. Over a ugly hack, by the control_proc function, the driver is
ordered to read the Cali.-data . This solution is named "Hmm... very dirty:
..." by the author self.
A little abstract of his code:
static int
xf86GunzeChangeControl(LocalDevicePtr local, xDeviceCtl *control)
{
xDeviceResolutionCtl *res;
...
if (res->num_valuators < 2) {
...
} else {
...
xf86GunzeReadCalib(priv);
}
}
This function is registered as control_proc in the driver.
The calibration tool write the cali.-data to the extra file and order the
driver over XChangeDeviceControl(display, device, control,
value->num_valuators=2 ) to read this.
Look at:
http://www.linux.it/~rubini/software/#gunzets
This solution need a customised toch driver. I will use the existing drivers
and calibrate with 'xDeviceTSCalibrationCtl'. I think the implementation of
the "struct xDeviceTSCalibrationCtl" in the existing drivers is not
sensless. Hope somebody have the right solution.
> When you find a good solution, please share it with us, I'm quite
> interrested.
I will do this.
regards
Stefan
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
