From ea0f852c450402b69855ba607ab95cd4f1a045e9 Mon Sep 17 00:00:00 2001 From: patacongo Date: Wed, 28 Sep 2011 17:41:58 +0000 Subject: [PATCH] Add a simulated touchscreen driver git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@3989 42af7a65-404d-4744-a932-0658087f49c3 --- Documentation/NXGraphicsSubsystem.html | 53 +++++++++++++++----------- 1 file changed, 31 insertions(+), 22 deletions(-) diff --git a/Documentation/NXGraphicsSubsystem.html b/Documentation/NXGraphicsSubsystem.html index 4198905742..6c3ccf7bba 100644 --- a/Documentation/NXGraphicsSubsystem.html +++ b/Documentation/NXGraphicsSubsystem.html @@ -12,7 +12,7 @@

NX Graphics Subsystem

-

Last Updated: August 24, 2011

+

Last Updated: September 28, 2011

@@ -3416,13 +3416,13 @@ static FAR const struct nx_fontpackage_s *g_fontpackages[] =

Building apps/examples/nx. NX testing was performed using apps/examples/nx with the Linux/Cygwin-based NuttX simulator. - Configuration files for building this test can be found in configs/sim/nx. + Configuration files for building this test can be found in configs/sim/nx + and configs/sim/nx11. There are two alternative configurations for building the simulation:

  1. - The default configuration using the configuration file at - configs/sim/nx/defconfig. + The configuration using the configuration file at configs/sim/nx/defconfig. This default configuration exercises the NX logic a 8 BPP but provides no visual feedback. In this configuration, a very simple, simulated framebuffer driver is used that is based upon a simple region of memory posing as video memory. @@ -3437,18 +3437,17 @@ make

  2. - A preferred configuration extends the test with a simulated framebuffer driver + The preferred configuration is at configs/sim/nx11/defconfig. + This configuration extends the test with a simulated framebuffer driver that uses an X window as a framebuffer. - This configuration uses the configuration file at configs/sim/nx/defconfig-x11. This is a superior test configuration because the X window appears at your desktop and you can see the NX output. This preferred configuration can be built as follows: 

       cd <NuttX-Directory>/tools
-./configure sim/nx
+./configure sim/nx11
 cd  <NuttX-Directory>
-cp <NuttX-Directory>/configs/sim/nx/defconfig-x11 .config
 make
 ./nuttx
    @@ -3456,29 +3455,40 @@ make Update: The sim target has suffered some bit-rot over the years and so the following caveats need to be added:
      -
    • - The X target does not build under recent Cygwin configurations. -
      • -
    • - The X target does not build under current Ubuntu distributions; - it fails to locate the X header files. -
      • -
    • +

    • + The X target builds under recent Cygwin configurations, but does not execute. + (It fails inside of XOpenDisplay(). +

      • +

    • + The X target does not build under current (9.09) Ubuntu distributions. + I needed to make the following changes: +

      +
        +cd /usr/lib/ +sudo ln -s libXext.so.6.4.0 libXext.so +
      +

      + The build will also fail to locate the X header files unless you install an X11 development package. +

      • +

    • The sim target itself is broken under 64-bit Linux. This is because the sim target is based upon some assembly language setjmp/longjmp logic that only works on 32-bit systems. -

      NOTE: There is a workaround in this case: +

      +

      + NOTE: There is a workaround in this case: You can build for 32-bit execution on a 64-bit machine by adding -m3 to the CFLAGS and -m32 -m elf_i386 to the LDFLAGS. See the patch file 0001-Quick-hacks-to-build-sim-nsh-ostest-on-x86_64-as-32-.patch that can be found in NuttX files. -

      +

      • +

    • + Refer to the readme file in sim configuration + README.txt file for additional information. +

-

- Why isn't this configuration the default? Because not all systems the use NX support X. -

Test Coverage. At present, apps/examples/nxt only exercises a subset of NX; @@ -3985,7 +3995,6 @@ make nxf_convert_32bpp() - Use defconfig-x11 when building. YES