[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Microwindows, Touch Screen & calibration
From: S A McConnell ####@####.#### Date: 6 Sep 2000 18:33:32 -0000 Message-Id: <39B68F5F.7B5701F3@cotw.com> O.K. I have built Microwindows and have enabled the "IPAQ" TS code. I modified the ucb1200_ts code to work with my ARM hardware. All of that code is working. (I can manipulate the mine game.) Now I need to calibrate the touch screen. Does any code exist for doing that on the ARM platform? The ucb1200_ts code is suppose to have Microwin style calibration. In the past I have been pointed to tpcal. ftp://ftp.ltc.com/pub/linux/mips/ This code depends upon *.h files that do not exist in my configuration. $gcc tp.c tp.c:37: linux/tpanel.h: No such file or directory tp.c:457: ../kdrive/kdrive.h: No such file or directory Any pointers would be appreciated. Scott | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Microwindows, Touch Screen & calibration
From: "Greg Haerr" ####@####.#### Date: 7 Sep 2000 02:57:48 -0000 Message-Id: <004901c01877$e5710ca0$6817dbd0@censoft.com> : O.K. I have built Microwindows and have enabled the "IPAQ" TS code. I : modified the ucb1200_ts code to work with my ARM hardware. All of that : code is working. (I can manipulate the mine game.) Cool. BTW, I'm interested in keeping any enhancements/modifications to kernel touch panel drivers if you'd like to send them. ;-) : : Now I need to calibrate the touch screen. Does any code exist for doing : that on the ARM platform? The ucb1200_ts code is suppose to have : Microwin style calibration. There's a working touch panel calibrator for the linux-vr style touch screen driver in the Microwindows source that Brad LaRonde wrote. It's GPL, so it's in microwin/src/contrib/GPL/tpcal Check it out. I've checked this version against the latest 0.88 sources (patch1) Regards, Greg : : In the past I have been pointed to tpcal. : : ftp://ftp.ltc.com/pub/linux/mips/ : : This code depends upon *.h files that do not exist in my configuration. : $gcc tp.c : tp.c:37: linux/tpanel.h: No such file or directory : tp.c:457: ../kdrive/kdrive.h: No such file or directory : : Any pointers would be appreciated. : : Scott : : --------------------------------------------------------------------- : To unsubscribe, e-mail: ####@####.#### : For additional commands, e-mail: ####@####.#### : : | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Microwindows, Touch Screen & calibration
From: S A McConnell ####@####.#### Date: 7 Sep 2000 18:39:55 -0000 Message-Id: <39B7E254.603C1EF@cotw.com> Greg Haerr wrote: > There's a working touch panel calibrator for the linux-vr > style touch screen driver in the Microwindows source that > Brad LaRonde wrote. It's GPL, so it's in > microwin/src/contrib/GPL/tpcal Ok I have done that cross compiled it and stuffed it into my RAM Disk. When I run tpcal it hands back seven parameters. With the MIPS code those values were placed into /etc/pointercal. Which mou_tp.c would read and use to adjust the values being returned from the touch screen device. (calibration occured on the application side.) I notice that the ts_ioctl supports seven commands. So do those seven values represent (raw_max_x, raw_max_y, res_x, res_y, raw_min_x, raw_min_y, xyswp)? Not knowing what they are I do not know what to do with them. Nor can I tell if the values I am getting are reasonable. tpcal results: (-273605, -633, 174383829, -700, 278166, -4003337, 65536) Should I send them to ts_ioctl cmd's 3-12? Thanks, Scott | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Microwindows, Touch Screen & calibration
From: "Greg Haerr" ####@####.#### Date: 7 Sep 2000 19:49:45 -0000 Message-Id: <015501c01905$452f6a00$6817dbd0@censoft.com> : tpcal results: (-273605, -633, 174383829, -700, 278166, -4003337, 65536) : : : Should I send them to ts_ioctl cmd's 3-12? probably. the mou_tp.c code should tell you what it does with them, it opens up /etc/pointercal, doesn't it? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Microwindows, Touch Screen & calibration
From: brad ####@####.#### Date: 8 Sep 2000 18:09:06 -0000 Message-Id: <Pine.LNX.4.10.10009081409070.4388-100000@localhost.localdomain> tpcal produces transformation coefficients for mou_tp. mou_tp uses the coefficients to transform raw touch panel data to (x,y) screen data. This has nothing to do with ts_ioctls. Regards, Brad On Thu, 7 Sep 2000, S A McConnell wrote: > Greg Haerr wrote: > > > There's a working touch panel calibrator for the linux-vr > > style touch screen driver in the Microwindows source that > > Brad LaRonde wrote. It's GPL, so it's in > > microwin/src/contrib/GPL/tpcal > > Ok I have done that cross compiled it and stuffed it into my RAM Disk. > > When I run tpcal it hands back seven parameters. With the MIPS code > those values > were placed into /etc/pointercal. Which mou_tp.c would read and use to > adjust the > values being returned from the touch screen device. (calibration occured > on the application side.) > > I notice that the ts_ioctl supports seven commands. So do those seven > values represent (raw_max_x, raw_max_y, res_x, res_y, raw_min_x, > raw_min_y, xyswp)? > > Not knowing what they are I do not know what to do with them. Nor can I > tell if the values I am getting are reasonable. > tpcal results: (-273605, -633, 174383829, -700, 278166, -4003337, 65536) > > > Should I send them to ts_ioctl cmd's 3-12? > > Thanks, > Scott > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ####@####.#### > For additional commands, e-mail: ####@####.#### > > | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |