Re: [yocto] Sato image touchscreen calibration is borked

2014-11-17 Thread Burton, Ross
On 17 November 2014 07:25, Mike Looijmans wrote: > BTW, you can use tslib with xorg. This is what I have set up as I find >> ts_calibrate easier to work with. >> > > Interesting option, can you elaborate on that (in particular, in > combination with Yocto builds)? meta-oe has xf86-input-tslib.

Re: [yocto] Sato image touchscreen calibration is borked

2014-11-16 Thread Mike Looijmans
On 11/13/2014 06:58 PM, Michael Gloff wrote: On Thu, Nov 13, 2014 at 7:28 AM, Burton, Ross mailto:ross.bur...@intel.com>> wrote: Hi, On 13 November 2014 13:19, Mike Looijmans mailto:mike.looijm...@topic.nl>> wrote: I've been using "ts_calibrate" in the past, and that worked ju

Re: [yocto] Sato image touchscreen calibration is borked

2014-11-14 Thread Burton, Ross
On 14 November 2014 08:17, Michael Gloff wrote: > I am using the xf86-input-tslib X driver. I forgot about that piece of the > puzzle. > Genuinely surprised that still works, but good to know! Ross -- ___ yocto mailing list yocto@yoctoproject.org htt

Re: [yocto] Sato image touchscreen calibration is borked

2014-11-14 Thread Michael Gloff
On Thu, Nov 13, 2014 at 5:05 PM, Burton, Ross wrote: > > On 13 November 2014 17:58, Michael Gloff wrote: > >> BTW, you can use tslib with xorg. This is what I have set up as I find >> ts_calibrate easier to work with. > > > The only mention of e.g. ts_read() that I can see in the xserver source

Re: [yocto] Sato image touchscreen calibration is borked

2014-11-13 Thread Burton, Ross
On 13 November 2014 17:58, Michael Gloff wrote: > BTW, you can use tslib with xorg. This is what I have set up as I find > ts_calibrate easier to work with. The only mention of e.g. ts_read() that I can see in the xserver source is in the kdrive server. Is there some compatibility mode or some

Re: [yocto] Sato image touchscreen calibration is borked

2014-11-13 Thread Michael Gloff
On Thu, Nov 13, 2014 at 7:28 AM, Burton, Ross wrote: > Hi, > > On 13 November 2014 13:19, Mike Looijmans wrote: > >> I've been using "ts_calibrate" in the past, and that worked just fine on >> this board. >> > > Modern X servers don't use tslib, so this won't work since we stopped > using kdrive

Re: [yocto] Sato image touchscreen calibration is borked

2014-11-13 Thread Burton, Ross
On 13 November 2014 14:09, Mike Looijmans wrote: > So it seems related to the little I2C touchscreen controller, or some kind > of rotation. The coordinate system for the small touchscreen looks rotated > 180 degrees, looking at the numbers. xinput cannot handle that? My touchscreen is Y-invert

Re: [yocto] Sato image touchscreen calibration is borked

2014-11-13 Thread Mike Looijmans
On 11/13/2014 02:54 PM, Mike Looijmans wrote: On 11/13/2014 02:28 PM, Burton, Ross wrote: Hi, On 13 November 2014 13:19, Mike Looijmans mailto:mike.looijm...@topic.nl>> wrote: I've been using "ts_calibrate" in the past, and that worked just fine on this board. Modern X servers don't

Re: [yocto] Sato image touchscreen calibration is borked

2014-11-13 Thread Mike Looijmans
On 11/13/2014 02:28 PM, Burton, Ross wrote: Hi, On 13 November 2014 13:19, Mike Looijmans mailto:mike.looijm...@topic.nl>> wrote: I've been using "ts_calibrate" in the past, and that worked just fine on this board. Modern X servers don't use tslib, so this won't work since we stopped

Re: [yocto] Sato image touchscreen calibration is borked

2014-11-13 Thread Burton, Ross
Hi, On 13 November 2014 13:19, Mike Looijmans wrote: > I've been using "ts_calibrate" in the past, and that worked just fine on > this board. > Modern X servers don't use tslib, so this won't work since we stopped using kdrive about two years ago. DEBUG: Adding click 0 (X=1023, Y=599) > DEBUG:

[yocto] Sato image touchscreen calibration is borked

2014-11-13 Thread Mike Looijmans
On 11/13/2014 02:10 PM, Mike Looijmans wrote: Next challenge is to calibrate the touch screen... Hmm. That's a big disappointment. I've been using "ts_calibrate" in the past, and that worked just fine on this board. Sato uses an X application for this, and it's apparently borked or so. It