diff --git a/Documentation/NXGraphicsSubsystem.html b/Documentation/NXGraphicsSubsystem.html index 7d9c2d64e9..7aa8ab03cd 100644 --- a/Documentation/NXGraphicsSubsystem.html +++ b/Documentation/NXGraphicsSubsystem.html @@ -356,14 +356,14 @@
1NXMU and NXSU are interchangeable other than (1) certain start-up - and initializeation APIs (as described below), and (2) timing. With NXSU, NX APIs + and initialization APIs (as described below), and (2) timing. With NXSU, NX APIs execute immediately; with NXMU, NX APIs defer and serialize the operations and, hence, introduce different timing and potential race conditions that you would not experience with NXSU.
NXNULL? - At one time, I also envisoned a NULL front-end that did not support windowing + At one time, I also envisioned a NULL front-end that did not support windowing at all but, rather, simply provided the entire framebuffer or LCD memory as one dumb window. This has the advantage that the same NX APIs can be used on the one dumb window as for the other NX windows. @@ -765,7 +765,7 @@ int nxgl_splitline(FAR struct nxgl_vector_s *vector, FAR struct nxgl_trapezoid_s
Description: In the general case, a line with width can be represented as a parallelogram with a triangle at the top and bottom. - Triangles and parallelograms are both degenerate versions of a trapeziod. + Triangles and parallelograms are both degenerate versions of a trapezoid. This function breaks a wide line into triangles and trapezoids. This function also detects other degenerate cases:
@@ -777,7 +777,7 @@ int nxgl_splitline(FAR struct nxgl_vector_s *vector, FAR struct nxgl_trapezoid_s Ifx1 == x2
then the line is vertical and also better represented as a rectangle.
mq_notifiy()
:
nx_eventnotify()
again.
CONFIG_NX_MULTIUSER
as well.
CONFIG__NXCONSOLE_KBDBUFSIZE
:
CONFIG_NXCONSOLE_NXKBDIN
is enabled, then this value may be used to
- define the size of the per-window keyboar input buffer. Default: 16
+ define the size of the per-window keyboard input buffer. Default: 16
CONFIG_NXCONSOLE_NPOLLWAITERS
:
Use the bdf-converter program to convert the BDF font to the NuttX font format.
- This will result in a C header file containing defintions.
+ This will result in a C header file containing definitions.
That header file should be installed at, for example, graphics/nxfonts/nxfonts_myfont.h
.
Note the inefficiency when execv()
or execl()
is called in the normal, two-step process:
(1) first call vfork()
to create a new thread, then (2) call execv()
or execl()
to replace the new thread with a program from the file system.
- Since the new thread will be terminated by the execv()
or execl()
call, it really served no purpose other than to support Unix compatility.
+ Since the new thread will be terminated by the execv()
or execl()
call, it really served no purpose other than to support Unix compatibility.
The non-standard binfmt function exec()
needs to have (1) a symbol table that provides the list of symbols exported by the base code, and (2) the number of symbols in that table.
@@ -1000,7 +1000,7 @@ int posix_spawn_file_actions_destroy(FAR posix_spawn_file_actions_t *file_action
Description:
- The posix_spawn_file_actions_destroy()
function destroys the object referenced by file_actions
which was previously initializeed by posix_spawn_file_actions_init()
, returning any resources obtained at the time of initialization to the system for subsequent reuse.
+ The posix_spawn_file_actions_destroy()
function destroys the object referenced by file_actions
which was previously initialized by posix_spawn_file_actions_init()
, returning any resources obtained at the time of initialization to the system for subsequent reuse.
A posix_spawn_file_actions_t
may be reinitialized after having been destroyed, but must not be reused after destruction, unless it has been reinitialized.
@@ -1931,8 +1931,8 @@ interface of the same name.
Description:
- sched_rr_get_interval()
writes the timeslice interval
- for task identified by pid
into the timespec structure
+ sched_rr_get_interval()
writes the timeslice interval
+ for task identified by pid
into the timespec structure
pointed to by interval
. If pid is zero, the timeslice
for the calling process is written into 'interval. The
identified process should be running under the SCHED_RR
diff --git a/Kconfig b/Kconfig
index fb08f3289b..1bf91e2a58 100644
--- a/Kconfig
+++ b/Kconfig
@@ -94,7 +94,7 @@ config APPS_DIR
Identifies the directory that builds the
application to link with NuttX. Default: ../apps This symbol must be assigned
to the path to the application build directory *relative* to
- the NuttX top build direcory. If you had an application
+ the NuttX top build directory. If you had an application
directory and the NuttX directory each in separate directory
trees like this:
@@ -118,7 +118,7 @@ config APPS_DIR
2)clean. Do whatever is appropriate to clean the application
directories for a fresh build.
- 3)distclean. Clean everthing -- auto-generated files, symbolic
+ 3)distclean. Clean everything -- auto-generated files, symbolic
links etc. -- so that the directory contents are the same as
the contents in your configuration management system.
This is only done when you change the NuttX configuration.
@@ -145,7 +145,7 @@ config BUILD_2PASS
library (archive) (some modification to this Makefile would be required if
PASS1_TARGET generates an archive). Pass 1 1ncremental (relative) link
objects should be put into the processor-specific source directory (where other
- link objects will be created). If the pass1 obect is an archive, it could
+ link objects will be created). If the pass1 object is an archive, it could
go anywhere.
if BUILD_2PASS
@@ -277,7 +277,7 @@ config ARCH_FLOAT_H
---help---
The float.h header file defines the properties of your floating
point implementation. It would always be best to use your
- toolchain's float.h header file but if none is avaiable, a default
+ toolchain's float.h header file but if none is available, a default
float.h header file will provided if this option is selected. However
there is no assurance that the settings in this float.h are actually
correct for your platform!
@@ -329,7 +329,7 @@ config DEBUG_VERBOSE
bool "Enable Debug Verbose Output"
default n
---help---
- Enables verbose debug output (assuming debug featurses are enabled).
+ Enables verbose debug output (assuming debug features are enabled).
As a general rule, when DEBUG is enabled only errors will be
reported in the debug SYSLOG output. But if you also enable
DEBUG_VERBOSE, then very chatty (and often annoying) output will be
diff --git a/arch/Kconfig b/arch/Kconfig
index 6432834032..2a63c61d77 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -154,7 +154,7 @@ config ARCH_IRQPRIO
NOTE: The use of interrupt priorities implies that you also have
support for nested interrupts. Most architectures do not support
- nesting of interupts or, if they do, they only supported nested
+ nesting of interrupts or, if they do, they only supported nested
interrupts with certain configuration options. So this selection
should be used with caution.
@@ -212,7 +212,7 @@ config ARCH_CALIBRATION
---help---
Enables some built in instrumentation that causes a 100 second delay
during boot-up. This 100 second delay serves no purpose other than it
- allows you to calibratre BOARD_LOOPSPERMSEC. You simply use a stop
+ allows you to calibrate BOARD_LOOPSPERMSEC. You simply use a stop
watch to measure the actual delay then adjust BOARD_LOOPSPERMSEC until
the actual delay is 100 seconds.
@@ -387,7 +387,7 @@ config RAM_START
help
The physical start address of primary installed RAM. "Primary" RAM
refers to the RAM that you link program code into. If program code
- does not excecute out of RAM but from FLASH, then you may designate
+ does not execute out of RAM but from FLASH, then you may designate
any block of RAM as "primary."
config RAM_VSTART
@@ -397,7 +397,7 @@ config RAM_VSTART
help
The virtual start address of installed primary RAM. "Primary" RAM
refers to the RAM that you link program code into. If program code
- does not excecute out of RAM but from FLASH, then you may designate
+ does not execute out of RAM but from FLASH, then you may designate
any block of RAM as "primary."
config RAM_SIZE
@@ -406,7 +406,7 @@ config RAM_SIZE
help
The size in bytes of the installed primary RAM. "Primary" RAM
refers to the RAM that you link program code into. If program code
- does not excecute out of RAM but from FLASH, then you may designate
+ does not execute out of RAM but from FLASH, then you may designate
any block of RAM as "primary."
if BOOT_RUNFROMFLASH && ARCH_HAVE_MMU