nanogui: Thread: Problem with touch screen

Hi again, Aaron,

On Tue, 2009-04-14 at 10:43 -0700, Aaron J. Grier wrote:
> On Sun, Apr 12, 2009 at 09:39:32PM -0400, Robert S. Grimes wrote:
> > I know for sure that the Horizontal and Vertical resolutions are set
> > to 320 and 240 respectively, as is my LCD - this is the correct
> > configuration for my display.
> > 
> > Any ideas on what to check, or where to look?  I'm a bit stumped on
> > this, I'm afraid...
> 
> can you run the test in demos/test and see if it gives sane values for
> the pointer?  it might be a rotation issue.

I can't get this compile.  There was no makefile in that directory, so I
attempted to adapt the one in mwin, but I couldn't make it work.  Here
are the errors I see, and attached is my Makefile attempt.

make -C test
make[2]: Entering directory
`/home/rsg/ltib-cf_nommu-20081215/rpm/BUILD/microwindows-0.90/src/demos/test'
Updating dependencies
in /home/rsg/ltib-cf_nommu-20081215/rpm/BUILD/microwindows-0.90/src/demos/test ...
/bin/sh -ec '/usr/bin/gcc -B/usr/bin// -MM
-DMWPIXEL_FORMAT=MWPF_TRUECOLOR0888 -DHAVE_FILEIO -DHAVE_FNT_SUPPORT=1
-DFNT_FONT_DIR="\""fonts/bdf""\" -DHAVE_BMP_SUPPORT=1
-DHAVE_GIF_SUPPORT=1 -DHAVE_PNM_SUPPORT=1 -DHAVE_XPM_SUPPORT=1
-DHAVE_SHAREDMEM_SUPPORT=1 -DHAVETEXTMODE=0 -DERASEMOVE=1
-DUPDATEREGIONS=1 -DLINUX=1 -DUNIX=1 -DLINUX=1 -DUNIX=1 -m32  -I.
-I/home/rsg/ltib-cf_nommu-20081215/rpm/BUILD/microwindows-0.90/src/include test.c \
	| sed '\''s/\(\)\.o[ :]*/\1.o \.depend : $(TOP)\/config /g'\''
> .depend; \
	[ -s .depend ] || rm -f .depend'
make[2]: Leaving directory
`/home/rsg/ltib-cf_nommu-20081215/rpm/BUILD/microwindows-0.90/src/demos/test'
make[2]: Entering directory
`/home/rsg/ltib-cf_nommu-20081215/rpm/BUILD/microwindows-0.90/src/demos/test'
Compiling test.c ...
gcc -c   -DMWPIXEL_FORMAT=MWPF_TRUECOLOR0888 -DHAVE_FILEIO
-DHAVE_FNT_SUPPORT=1 -DFNT_FONT_DIR="\""fonts/bdf""\"
-DHAVE_BMP_SUPPORT=1 -DHAVE_GIF_SUPPORT=1 -DHAVE_PNM_SUPPORT=1
-DHAVE_XPM_SUPPORT=1 -DHAVE_SHAREDMEM_SUPPORT=1 -DHAVETEXTMODE=0
-DERASEMOVE=1 -DUPDATEREGIONS=1 -DLINUX=1 -DUNIX=1 -DLINUX=1 -DUNIX=1
-I.
-I/home/rsg/ltib-cf_nommu-20081215/rpm/BUILD/microwindows-0.90/src/include -Wall -Wpointer-arith  -o test.o test.c
test.c: In function 'main':
test.c:31: warning: implicit declaration of function 'GdOpenKeyboard'
test.c:32: warning: implicit declaration of function 'PRINT_ERROR'
test.c:36: warning: implicit declaration of function 'GdOpenMouse'
test.c:38: warning: implicit declaration of function 'GdCloseKeyboard'
test.c:43: warning: implicit declaration of function 'GsSelect'
test.c: In function 'GsTerminate':
test.c:51: warning: implicit declaration of function 'GdCloseMouse'
test.c: In function 'GsCheckMouseEvent':
test.c:125: error: 'COORD' undeclared (first use in this function)
test.c:125: error: (Each undeclared identifier is reported only once
test.c:125: error: for each function it appears in.)
test.c:125: error: expected ';' before 'rootx'
test.c:126: error: expected ';' before 'rooty'
test.c:127: error: 'BUTTON' undeclared (first use in this function)
test.c:127: error: expected ';' before 'newbuttons'
test.c:131: warning: implicit declaration of function 'GdReadMouse'
test.c:131: error: 'rootx' undeclared (first use in this function)
test.c:131: error: 'rooty' undeclared (first use in this function)
test.c:131: error: 'newbuttons' undeclared (first use in this function)
test.c: In function 'GsCheckKeyboardEvent':
test.c:150: error: 'MODIFIER' undeclared (first use in this function)
test.c:150: error: expected ';' before 'modifiers'
test.c:154: warning: implicit declaration of function 'GdReadKeyboard'
test.c:154: error: 'modifiers' undeclared (first use in this function)
make[2]: *** [test.o] Error 1
make[2]: Leaving directory
`/home/rsg/ltib-cf_nommu-20081215/rpm/BUILD/microwindows-0.90/src/demos/test'
make[1]: *** [subdir-test] Error 2
make[1]: Leaving directory
`/home/rsg/ltib-cf_nommu-20081215/rpm/BUILD/microwindows-0.90/src/demos'
make: [all] Error 2 (ignored)


> 
> as for the flickering display, I wonder if access to the LCD memory
> isn't being properly handled by the framebuffer driver.  could you write
> a small test that does memset() on the raw framebuffer to check?  is
> there an ioctl() available for synchronization to the LCD?
> 

Given that I can't make an existing program compile, I'm almost afraid
to try this at this time!  Can you suggest a good starting point?  And
how would you code the call to memset()?  FWIW - I was thinking of doing
this myself, but I have no idea how to access the framebuffer driver
directly.

I'm so frustrated with this right now!  I feel so close to understanding
this, but still feel completely lost!

Thanks,
-Bob