From 7e8a760c60f838662782d974e7ba31879ff6da71 Mon Sep 17 00:00:00 2001 From: Gregory Nutt Date: Sat, 20 Sep 2014 15:01:50 -0600 Subject: [PATCH] Change all occurrences of NxConsole to NxTerm --- Documentation/NXGraphicsSubsystem.html | 38 +++++++++++++------------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/Documentation/NXGraphicsSubsystem.html b/Documentation/NXGraphicsSubsystem.html index 8fd35408cc..99b7134283 100644 --- a/Documentation/NXGraphicsSubsystem.html +++ b/Documentation/NXGraphicsSubsystem.html @@ -45,7 +45,7 @@ 1.3.3 NX Tool Kit (NXTK)
1.3.4 NX Fonts Support (NXFONTS)
1.3.5 NX Widgets (NxWidgets)
- 1.3.6 NX Console Driver (NxConsole) + 1.3.6 NX Terminal Driver (NxTerm)

@@ -191,7 +191,7 @@ B.4 NX Multi-User (Only) Configuration Settings
B.5 NXTK Configuration Settings
B.6 NXFONTS Configuration Settings
- B.7 NxConsole Configuration Settings + B.7 NxTerm Configuration Settings

@@ -403,12 +403,12 @@ NxWidgets is built on top of the core NuttX graphics subsystem, but is not a part of the core graphics subystems.

-

1.3.6 NX Console Driver (NxConsole)

+

1.3.6 NX Terminal Driver (NxTerm)

- NxConsole is a write-only character device (not shown) that is built on top of an NX window. + NxTerm is a write-only character device (not shown) that is built on top of an NX window. This character device can be used to provide stdout and stderr and, hence, can provide the output side of NuttX console. - NxConsole is only available when the multi-user NX implementation is selected (CONFIG_NX_MULTIUSER). + NxTerm is only available when the multi-user NX implementation is selected (CONFIG_NX_MULTIUSER).

@@ -3204,9 +3204,9 @@ int nxf_convert_32bpp(FAR uint32_t *dest, uint16_t height,
nuttx/../nxwidgets
The NxWidgets code is provided as a separate package located outside of the NuttX source tree (probably at this location). -
graphics/nxconsole -
The NxConsole driver is built on top of NX and works with either the single-user or multi-user NX version. - See include/nuttx/nx/nxconsole.h. +
graphics/nxterm +
The NxTerm driver is built on top of NX and works with either the single-user or multi-user NX version. + See include/nuttx/nx/nxterm.h.

1There is no nxsu sub-directory in nuttx/libnx. @@ -3370,32 +3370,32 @@ int nxf_convert_32bpp(FAR uint32_t *dest, uint16_t height, -

B.7 NxConsole Configuration Settings

+

B.7 NxTerm Configuration Settings

-

General NxConsole settings.

+

General NxTerm settings.

    CONFIG_NXTERM: -
    Enables building of the NxConsole driver. +
    Enables building of the NxTerm driver.
-

NxConsole output text/graphics options:

+

NxTerm output text/graphics options:

    CONFIG_NXTERM_BPP: -
    Currently, NxConsole supports only a single pixel depth. +
    Currently, NxTerm supports only a single pixel depth. This configuration setting must be provided to support that single pixel depth. Default: The smallest enabled pixel depth. (see CONFIG_NX_DISABLE_*BPP)
    CONFIG_NXTERM_CURSORCHAR:
    The bitmap code to use as the cursor. Default '_'
    CONFIG_NXTERM_MXCHARS: -
    NxConsole needs to remember every character written to the console so that it can redraw the window. +
    NxTerm needs to remember every character written to the console so that it can redraw the window. This setting determines the size of some internal memory allocations used to hold the character data. Default: 128.
    CONFIG_NXTERM_CACHESIZE:
    - NxConsole supports caching of rendered fonts. + NxTerm supports caching of rendered fonts. This font caching is required for two reasons: (1) First, it improves text performance, but more importantly (2) it preserves the font memory. @@ -3405,11 +3405,11 @@ int nxf_convert_32bpp(FAR uint32_t *dest, uint16_t height, Only that number of the most recently used glyphs will be retained. Default: 16.
    - NOTE: There can still be a race condition between the NxConsole driver and the + NOTE: There can still be a race condition between the NxTerm driver and the NX task. If you every see character corruption (especially when printing a lot of data or scrolling), then increasing the value of CONFIG_NXTERM_CACHESIZE is something that you should try. - Alternatively, you can reduce the size of CONFIG_MQ_MAXMSGSIZE which will force NxConsole task to pace the server task. + Alternatively, you can reduce the size of CONFIG_MQ_MAXMSGSIZE which will force NxTerm task to pace the server task. CONFIG_NXTERM_CACHESIZE should be larger than CONFIG_MQ_MAXMSGSIZE in any event.
    CONFIG_NXTERM_LINESEPARATION: @@ -3420,7 +3420,7 @@ int nxf_convert_32bpp(FAR uint32_t *dest, uint16_t height,
-

NxConsole input options:

+

NxTerm input options:

    CONFIG_NXTERM_NXKBDIN: @@ -3428,7 +3428,7 @@ int nxf_convert_32bpp(FAR uint32_t *dest, uint16_t height, By default, keyboard input is taken from stdin (/dev/console). If this option is set, then the interfacenxcon_kdbin() is enabled. That interface may be driven by window callback functions so that keyboard input only goes to the top window. -
    CONFIG__NXCONSOLE_KBDBUFSIZE: +
    CONFIG__NXTERM_KBDBUFSIZE:
    If CONFIG_NXTERM_NXKBDIN is enabled, then this value may be used to define the size of the per-window keyboard input buffer. Default: 16
    CONFIG_NXTERM_NPOLLWAITERS: