Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-05-10 07:18:49 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Run codespell -w with the latest dictonary again

Browse Source 
Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
This commit is contained in:
Xiang Xiao
2020-02-23 16:50:23 +08:00
committed by Abdelatif Guettouche
parent 55a7dfc9a7
commit cde88cabcc
1532 changed files with 3117 additions and 3117 deletions
Download Patch File Download Diff File Expand all files Collapse all files
COPYING
+1 -1
View File
@@ -34,7 +34,7 @@ and 2011.
Copyright Line Continuation
---------------------------
Copy information which exceeds the usable line lengh may be broken and
Copy information which exceeds the usable line length may be broken and
continued on the following line, such as:
Copyright (C) 2007-2010, 2012, 2014-2015, 2017 Gregory Nutt. All
ChangeLog
+142 -142
View File
File diff suppressed because it is too large Load Diff
Documentation/NXGraphicsSubsystem.html
+10 -10
View File
@@ -304,7 +304,7 @@
NX supports any graphics device either of two device interfaces:
<ul>
<li>
Any device with random accesss video memory using the NuttX framebuffer driver interface
Any device with random access video memory using the NuttX framebuffer driver interface
(see <code>include/nuttx/video/fb.h</code>).
</li>
<li>
@@ -370,7 +370,7 @@
<p>
NX is the tiny NuttX windowing system for raw windows (i.e., simple regions of
graphics memory).
NX includes a small-footprint, multi-user implentation (NXMU as described below).
NX includes a small-footprint, multi-user implementation (NXMU as described below).
NX can be used without NxWidgets and without NXTOOLKIT for raw window displays.
</p>
@@ -642,7 +642,7 @@ void nxgl_rectunion(FAR struct nxgl_rect_s *dest,
</pre></ul>
<p>
<b>Description:</b>
Given two rectanges, <code>src1</code> and <code>src2</code>, return the larger rectangle that
Given two rectangles, <code>src1</code> and <code>src2</code>, return the larger rectangle that
contains both, <code>dest</code>.
</p>
@@ -1023,7 +1023,7 @@ int nxmu_start(int display, int plane);
In it is especially useful for setting up board operational and test configurations.
</p>
<p>
When called with the <code>cmd</code> of <code>BOARDIOC_NX_START</code>, then the <code>boardctl()</code> will call <code>nxmu_start</code> indirectly on behalf of the appication.
When called with the <code>cmd</code> of <code>BOARDIOC_NX_START</code>, then the <code>boardctl()</code> will call <code>nxmu_start</code> indirectly on behalf of the application.
In this case the <code>arg</code> parameter is ignored.
</p>
<p>
@@ -1872,7 +1872,7 @@ bool nx_ishidden(NXWINDOW hwnd);
<b>Input Parameters:</b>
<ul><dl>
<dt><code>hwnd</code>
<dd>The handle returned by <a href="#nxopenwindow"><code>nx_openwindow()</code></a> that indentifies the window to be queried.
<dd>The handle returned by <a href="#nxopenwindow"><code>nx_openwindow()</code></a> that identifies the window to be queried.
</dl></ul>
</p>
<p>
@@ -2278,7 +2278,7 @@ int nx_mousein(NXHANDLE handle, nxgl_coord_t x, nxgl_coord_t y, uint8_t buttons)
as well as mouse and keyboard inputs.
The client sub-window callbacks are registered when the framed window is
created with a call to <a href="#nxtkopenwindow"><code>nxtk_openwindow()</code></a>;
Separate toolbar sub-window callbakcs are reigistered when the toolbar
Separate toolbar sub-window callbacks are reigistered when the toolbar
is added using <a href="#nxtkopentoolbar"><code>nxtk_opentoolbar()</code></a>.
(NOTES: (1) only the client sub-window receives keyboard input and,
(2) border callbacks are not currently accessible by the user).
@@ -2685,7 +2685,7 @@ bool nxtk_ishidden(NXTKWINDOW hfwnd);
<b>Input Parameters:</b>
<ul><dl>
<dt><code>hfwnd</code>
<dd>The handle returned by <a href="#nxtkopenwindow"><code>nxtk_openwindow()</code></a> that indentifies the window to be queried.
<dd>The handle returned by <a href="#nxtkopenwindow"><code>nxtk_openwindow()</code></a> that identifies the window to be queried.
</dl></ul>
</p>
<p>
@@ -3600,7 +3600,7 @@ int nxcursor_setimage(NXHANDLE hnd, FAR const struct nx_cursorimage_s *image);
Set the cursor image.
</p>
<p>
The image is provided a a 2-bits-per-pixel image. The two bit incoding is as followings:
The image is provided a a 2-bits-per-pixel image. The two bit incoding is as following:
</p>
<ul>
00 - The transparent background.<br>
@@ -3768,7 +3768,7 @@ int nxcursor_setposition(NXHANDLE hnd, FAR const struct nxgl_point_s *pos);
<dd>Enables overall support for graphics library and NX
<dt><code>CONFIG_NX_RAMBACKED</code>
<dd>Enables RAM backed window support.
If this option is selected, then windows may be optionally created with a RAM frambuffer backing up the window content.
If this option is selected, then windows may be optionally created with a RAM framebuffer backing up the window content.
Rending into the window will result in rending into the backup framebuffer, then updating the physical display from the framebuffer.
<p>
The advantage of this option is that the application that manages window will no longer receive redraw() callbacks.
@@ -4019,7 +4019,7 @@ int nxcursor_setposition(NXHANDLE hnd, FAR const struct nxgl_point_s *pos);
<p>
<b>Font Installation Steps</b>,
Below are general instructions for creating and installing a new font in the NX graphic system.
The first two steps only appy if you are using the BDF font converter program.
The first two steps only apply if you are using the BDF font converter program.
</p>
<ol start="1">
<li>
Documentation/NuttShell.html
+2 -2
View File
@@ -178,7 +178,7 @@
<tr>
<td><br></td>
<td>
<a href="#cmddmesg">2.17 Dump Buffered SYSLOG Ouput (dmesg)</a>
<a href="#cmddmesg">2.17 Dump Buffered SYSLOG Output (dmesg)</a>
</td>
</tr>
<tr>
@@ -1674,7 +1674,7 @@ dirname &lt;path&gt
<table width ="100%">
<tr bgcolor="#e4e4e4">
<td>
<a name="cmddmesg"><h2>2.17 Dump Buffered SYSLOG Ouput (dmesg)</h2></a>
<a name="cmddmesg"><h2>2.17 Dump Buffered SYSLOG Output (dmesg)</h2></a>
</td>
</tr>
</table>
Documentation/NuttX.html
+11 -11
View File
@@ -554,7 +554,7 @@
<td><br></td>
<td>
<p>
<li>ROMFS filesystem support (XIP capabable).</li>
<li>ROMFS filesystem support (XIP capable).</li>
</p>
</td>
</tr>
@@ -2143,7 +2143,7 @@
<p>
<a name="moxart"><b>MoxaRT</b></a>
A port to the Moxa NP51x0 series of 2-port advanced RS-232/422/485 serial device servers was contributed by Anton D. Kachalov in NuttX-7.11.
This port includes a NuttShell (NSH) configuraion with support for the Faraday FTMAC100 Ethernet MAC Driver.
This port includes a NuttShell (NSH) configuration with support for the Faraday FTMAC100 Ethernet MAC Driver.
</p>
</td>
</tr>
@@ -2514,7 +2514,7 @@
<b>STATUS:</b>
The basic, minimal port is code complete and introduced in NuttX-7.15, but had not yet been tested at that time due to the inavailability of hardware.
This basic port was verified in the NuttX-7.16 release, however.
The port is still mininal and more device drivers are needed to make the port usable.
The port is still minimal and more device drivers are needed to make the port usable.
</p>
<p>
Basic support of NuttX running in SMP mode on the i.MX6Q was also accomplished in NuttX-7.16.
@@ -2560,7 +2560,7 @@
<td>
<p>
<a name="tms570ls31x"><b>TI/Hercules TMS570LS31xx</b>.</a>
Archicture support for the TMS570LS3137ZWT part was added in NuttX 7.25 by Ivan Ucherdzhiev.
Architecture support for the TMS570LS3137ZWT part was added in NuttX 7.25 by Ivan Ucherdzhiev.
Ivan also added support for the TI Hercules TMS570LS31x USB Kit.
</p>
<ul>
@@ -2918,7 +2918,7 @@ nsh>
<td>
<p>
<a name="tilms6965"><b>TI/Stellaris LM3S6965</b>.</a>
This port uses the Stellaris LM3S6965 Ethernet Evalution Kit with a GNU arm-nuttx-elf toolchain*
This port uses the Stellaris LM3S6965 Ethernet Evaluation Kit with a GNU arm-nuttx-elf toolchain*
under either Linux or Cygwin.
</p>
<ul>
@@ -2953,7 +2953,7 @@ nsh>
<td>
<p>
<a name="tilms8962"><b>TI/Stellaris LM3S8962</b>.</a>
This port uses the Stellaris EKC-LM3S8962 Ethernet+CAN Evalution Kit with a GNU arm-nuttx-elf toolchain*
This port uses the Stellaris EKC-LM3S8962 Ethernet+CAN Evaluation Kit with a GNU arm-nuttx-elf toolchain*
under either Linux or Cygwin.
Contributed by Larry Arnold.
</p>
@@ -4674,7 +4674,7 @@ nsh>
Other software that supports the OmnibusF4 family include Betaflight, iNAV, and many others.
PX4 recently added support as well, also based on NuttX.
No code from those resources is included in this port.
The OmnibusF4 specifcation mandates the InvenSense MPU6000 which is included in NuttX-7.29 along with a driver for the MAX7546 OSD.
The OmnibusF4 specification mandates the InvenSense MPU6000 which is included in NuttX-7.29 along with a driver for the MAX7546 OSD.
</p>
</td>
</tr>
@@ -6100,7 +6100,7 @@ Mem: 29232 5920 23312 23312
<li>
<p><b>NuttX-7.29</b>.
XBAR and OCOTP support was added in NuttX-7.28 by David Sidrane.
LCD Framebuffer suport was added by Johannes.
LCD Framebuffer support was added by Johannes.
</p>
</li>
<li>
@@ -6417,7 +6417,7 @@ Mem: 29232 5920 23312 23312
<p>
<b>QEMU/Bifferboard i486</b>.
This port uses the <a href="http://wiki.qemu.org/Main_Page">QEMU</a> i486 and the native
Linux, Cywgin, MinGW the GCC toolchain under Linux or Cygwin.
Linux, Cygwin, MinGW the GCC toolchain under Linux or Cygwin.
</p>
<ul>
<p>
@@ -7229,7 +7229,7 @@ avr, m68k, m68hc11, m68hc12, m9s12, blackfin, m32c, h8, and SuperH ports.</block
</li>
<li>
<b>MinGW-GCC</b>.
MinGW-GCC is used to compiler the C tools in the <code>nuttx/tools</code> directory that are neede by the build.
MinGW-GCC is used to compiler the C tools in the <code>nuttx/tools</code> directory that are needed by the build.
MinGW-GCC can be downloaded from http://www.mingw.org/.
If you are using GNUWin32, then it is recommended that you not install the optional MSYS components as there may be conflicts.
</li>
@@ -7304,7 +7304,7 @@ if [ -x "$WINELOADER" ]; then exec "$WINELOADER" "$appname" "$@"; fi
</p>
<p>
MSYS, however, cannot be used with the native Windows NuttX build because it will invoke the MSYS bash shell instead of the <code>CMD.exe</code> shell.
Use GNUWin32 in the native Windows build envionment.
Use GNUWin32 in the native Windows build environment.
</p>
</td>
</tr>
Documentation/NuttXBinfmt.html
+1 -1
View File
@@ -484,7 +484,7 @@ struct symtab_s
</li>
<li>
Fixed size arrays.
There is no explicit provisional for dyanamically adding or removing entries from the symbol table (realloc might be used for that purpose if needed).
There is no explicit provisional for dynamically adding or removing entries from the symbol table (realloc might be used for that purpose if needed).
The intention is to support only fixed size arrays completely defined at compilation or link time.
</li>
</ol>
Documentation/NuttXCCodingStandard.html
+5 -5
View File
@@ -506,7 +506,7 @@
<p>
<b>Indentation</b>
Comments should, typically, be placed before the code section to which they apply.
The comment identation should be the same as the follow identation rules as the following code (if applicable).
The comment indentation should be the same as the follow indentation rules as the following code (if applicable).
</p>
<p>
@@ -803,7 +803,7 @@ void some_function(void)
</li>
<li>
<b>Compound Statements</b>.
Within this document, an opening left brace followed by a sequence of statments, and ending with a closing right brace is referred to as a <i>compound statement</i>.
Within this document, an opening left brace followed by a sequence of statements, and ending with a closing right brace is referred to as a <i>compound statement</i>.
</li>
<li>
<b>Nested Compound Statements</b>.
@@ -984,7 +984,7 @@ int animals(int animal)
<p>
<b>Indentation Unit</b>.
Indentation is in units of two spaces; Each indentation level is twos spaces further to the right than the preceding identation levels.
Indentation is in units of two spaces; Each indentation level is twos spaces further to the right than the preceding indentation levels.
TAB characters may not be used for indentation.
</p>
<center><table width="60%" border=1>
@@ -1791,7 +1791,7 @@ enum xyz_state_e
</li>
<li>
<b>Prefix</b>.
Each related macro value should begin with an upper-case prefix that identifies the value as part of a set of values (and also to mimimize the likelihood of naming collisions).
Each related macro value should begin with an upper-case prefix that identifies the value as part of a set of values (and also to minimize the likelihood of naming collisions).
</li>
<li>
<b>Single space after <code>#define</code></b>.
@@ -2077,7 +2077,7 @@ ptr = (FAR struct somestruct_s *)value;
<li>
<b>First definition or statement in column 3</b>.
The first data definitions or statements in the function body are idented by two spaces.
Standards for statements are covered in the <a href="#statements">following paragaraph</a>
Standards for statements are covered in the <a href="#statements">following paragraph</a>
</li>
<li>
<b>Local variables first</b>.
Documentation/NuttXDemandPaging.html
+3 -3
View File
@@ -307,7 +307,7 @@
<p>
The page fill worker thread will maintain a static variable called <code>struct tcb_s *g_pftcb</code>.
If no fill is in progress, <code>g_pftcb</code> will be NULL.
Otherwise, it will point to the TCB of the task which is receiving the fill that is in progess.
Otherwise, it will point to the TCB of the task which is receiving the fill that is in progress.
</p>
<ul><small>
<b>NOTE</b>:
@@ -336,7 +336,7 @@
</li>
<li>
Call the architecture-specific function <code>up_fillpage()</code>.
Two versions of the up_fillpage function are supported -- a blocking and a non-blocking version based upon the configuratin setting <code>CONFIG_PAGING_BLOCKINGFILL</code>.
Two versions of the up_fillpage function are supported -- a blocking and a non-blocking version based upon the configuration setting <code>CONFIG_PAGING_BLOCKINGFILL</code>.
<ul>
<li>
If <code>CONFIG_PAGING_BLOCKINGFILL</code> is defined, then up_fillpage is blocking call.
@@ -472,7 +472,7 @@
Chip specific logic will map the virtual and physical address spaces into three general regions:
<ol>
<li>
A .text region containing &quot;<a href="#MemoryOrg">locked-in-memory</a>&quot; code that is always avaialable and will never cause a page fault.
A .text region containing &quot;<a href="#MemoryOrg">locked-in-memory</a>&quot; code that is always available and will never cause a page fault.
This locked memory is loaded at boot time and remains resident for all time.
This memory regions must include:
<ul>
Documentation/NuttxPortingGuide.html
+6 -6
View File
@@ -737,8 +737,8 @@
This port does not support interrupts or a real timer (and hence no
round robin scheduler) Otherwise, it is complete.
</li>
<p>NOTE: In principle, this user mode port should run in any POSIX environement.
This target will probably not run &quot;out-of-the-box&quot; in unverified POSIX environments due to the many host environemnt dependencies.
<p>NOTE: In principle, this user mode port should run in any POSIX environment.
This target will probably not run &quot;out-of-the-box&quot; in unverified POSIX environments due to the many host environment dependencies.
</p>
<li><code>arch/arm</code>:
@@ -2573,7 +2573,7 @@ config ARCH_SIM
bool "Simulation"
select ARCH_HAVE_TICKLESS
---help---
Linux/Cywgin user-mode simulation.
Linux/Cygwin user-mode simulation.
</pre></ul>
<p>
When the simulation platform is selected, <code>ARCH_HAVE_TICKLESS</code> is automatically selected, informing the configuration system that <i>Tickless OS</i> options can be selected.
@@ -4055,7 +4055,7 @@ void nxsched_timer_expiration(void);
</p>
<li>
<p><b>Cancellation Points</b>:
Many of the application OS interfaces are <i>cancellation points</i>, i.e., when the task is operating in <i>defferred cancellation</i> state, it cannot be deleted or cancelled until it calls an application OS interface that is a cancellation point.
Many of the application OS interfaces are <i>cancellation points</i>, i.e., when the task is operating in <i>deferred cancellation</i> state, it cannot be deleted or cancelled until it calls an application OS interface that is a cancellation point.
</p>
<p>
The POSIX specification is very specific about this, specific both in identifying which application OS interfaces are cancellation points and specific in the fact that it is prohibited for any OS operation other than those listed in the specification to generate cancellation points.
@@ -6716,7 +6716,7 @@ int syslog_initialize(void);
<ol>
<li>
<p><b>Low-Level Serial Output</b>.
If you are using a SYSLOG console channel (<code>CONFIG_SYSLOG_CONSOLE</code>) and if the underlying architecture supports the low-level <code>up_putc()</code> interface(<code>CONFIG_ARCH_LOWPUTC</code>), then the SYLOG logic will direct the output to <code>up_putc()</code> which is capable of generating the serial output within the context of an interrupt handler.
If you are using a SYSLOG console channel (<code>CONFIG_SYSLOG_CONSOLE</code>) and if the underlying architecture supports the low-level <code>up_putc()</code> interface(<code>CONFIG_ARCH_LOWPUTC</code>), then the SYSLOG logic will direct the output to <code>up_putc()</code> which is capable of generating the serial output within the context of an interrupt handler.
</p>
<p>
There are a few issues in doing this however:
@@ -6752,7 +6752,7 @@ int syslog_initialize(void);
</li>
<li>
<p>
Later, when the next normal syslog output is generated, it will first empty the content of the interrupt buffer to the SYSLOG device in the proper context. It will then be followed by the normal syslog output. In this case, the interrupt level SYSLOG output will interrupt the normal output stream and the interrupt level SYSLOG output will be inserted into the correct position in the SYSLOG output when the next normal SYLOG output is generated.
Later, when the next normal syslog output is generated, it will first empty the content of the interrupt buffer to the SYSLOG device in the proper context. It will then be followed by the normal syslog output. In this case, the interrupt level SYSLOG output will interrupt the normal output stream and the interrupt level SYSLOG output will be inserted into the correct position in the SYSLOG output when the next normal SYSLOG output is generated.
</p>
</li>
</ul>
Documentation/NuttxUserGuide.html
+28 -28
View File
@@ -615,8 +615,8 @@ VxWorks provides the following similar interface:
<p>
<b>Description:</b>
The <code>task_setcancelstate()</code> function atomically
sets both the calling task's cancelability state to the indicated
state and returns the previous cancelability state at the location
sets both the calling task's cancellability state to the indicated
state and returns the previous cancellability state at the location
referenced by oldstate.
Legal values for state are TASK_CANCEL_ENABLE and TASK_CANCEL_DISABLE.
</p>
@@ -625,7 +625,7 @@ Any pending thread cancellation may occur at the time that the
cancellation state is set to TASK_CANCEL_ENABLE.
</p>
<p>
The cancelability state and type of any newly created tasks are TASK_CANCEL_ENABLE and TASK_CANCEL_DEFERRED respectively.
The cancellability state and type of any newly created tasks are TASK_CANCEL_ENABLE and TASK_CANCEL_DEFERRED respectively.
<p>
<b>Input Parameters:</b>
</p>
@@ -664,11 +664,11 @@ No thread could be found corresponding to that specified by the given thread ID.
</pre>
<p>
<b>Description:</b>
The <code>task_setcanceltype()</code> function atomically both sets the calling task's cancelability type to the indicated type and returns the previous cancelability type at the location referenced by <code>oldtype</code>.
The <code>task_setcanceltype()</code> function atomically both sets the calling task's cancellability type to the indicated type and returns the previous cancellability type at the location referenced by <code>oldtype</code>.
Legal values for type are <code>TASK_CANCEL_DEFERRED</code> and <code>TASK_CANCEL_ASYNCHRONOUS</code>.
</p>
<p>
The cancelability state and type of any newly created tasks are <code>TASK_CANCEL_ENABLE</code> and <code>TASK_CANCEL_DEFERRED</code> respectively.
The cancellability state and type of any newly created tasks are <code>TASK_CANCEL_ENABLE</code> and <code>TASK_CANCEL_DEFERRED</code> respectively.
</p>
<p>
<b>Input Parameters:</b>
@@ -712,7 +712,7 @@ No thread could be found corresponding to that specified by the given thread ID.
</p>
<p>
The <code>task_testcancel()</code> function creates a <a href="http://www.nuttx.org/doku.php?id=wiki:nxinternal:cancellation-points">Cancellation Point</a> in the calling task.
The <code>task_testcancel()</code> function has no effect if cancelability is disabled.
The <code>task_testcancel()</code> function has no effect if cancellability is disabled.
</p>
<p>
<b>Input Parameters:</b> None
@@ -902,7 +902,7 @@ int exec(FAR const char *filename, FAR char * const *argv,
</p>
<p>
<b>POSIX Compatibility:</b>
This is a non-standard inteface unique to NuttX.
This is a non-standard interface unique to NuttX.
Motivation for inclusion of this non-standard interface in certain build modes is discussed above.
</p>
@@ -1005,7 +1005,7 @@ int execl(FAR const char *path, ...);
<p>
<b>Description:</b>
<code>execl()</code> is functionally equivalent to <a href="#execv">execv()</a>, differing only in the form of its input parameters.
See the decription of <a href="#execv">execv()</a> for additional information.
See the description of <a href="#execv">execv()</a> for additional information.
<p>
<p>
<b>Input Parameters:</b>
@@ -1019,7 +1019,7 @@ int execl(FAR const char *path, ...);
<li>
</li>
<code>...</code>:
A list of the string arguments to be recevied by the program.
A list of the string arguments to be received by the program.
Zero indicates the end of the list.
</li>
</ul>
@@ -2254,7 +2254,7 @@ priority of the calling task is returned.
<p>
<b><code>CONFIG_SCHED_CHILD_STATUS</code></b>
If this option is selected, then the exit status of the child task will be retained after the child task exits.
This option should be selected if you require knowledge of a child process' exit status.
This option should be selected if you require knowledge of a child process's exit status.
Without this setting, <code>wait()</code>, <code>waitpid()</code> or <code>waitid()</code> may fail.
For example, if you do:
</p>
@@ -2752,7 +2752,7 @@ on this thread of execution.
<b>Assumptions/Limitations:</b>
<p>
<b>POSIX Compatibility:</b> Comparable to the ISO C interface of the same name.
Limitiations in the current implementation:
Limitations in the current implementation:
</p>
<ol>
<li>Only a single <code>atexit</code> function can be registered unless <code>CONFIG_SCHED_ATEXIT_MAX</code> defines a larger number.</li>
@@ -3014,7 +3014,7 @@ interface of the same name.
This is because the interrupt handler does not have the option of waiting for the message queue to become non-full.
</li>
<li>
It doesn't allocate new memory (because you cannot allocate memory from an interrup handler).
It doesn't allocate new memory (because you cannot allocate memory from an interrupt handler).
Instead, there are are pool of pre-allocated message structures that may be used just for sending messages from interrupt handlers.
The number of such pre-allocated messages is a configuration parameter.
</li>
@@ -5260,8 +5260,8 @@ Differences from the POSIX implementation include:
The sigset() function will modify signal dispositions.
The <code>signo</code> argument specifies the signal.
The <code>disp</code> argument specifies the signal's disposition, which may be <code>SIG_DFL</code>, <code>SIG_IGN</code>, or the address of a signal handler.
If <code>disp</code> is the address of a signal handler, the system will add <code>signo</code> to the calling process' signal mask before executing the signal handler; when the signal handler returns, the system will restore the calling process' signal mask to its state prior to the delivery of the signal.
<code>signo</code> will be removed from the calling process' signal mask.
If <code>disp</code> is the address of a signal handler, the system will add <code>signo</code> to the calling process's signal mask before executing the signal handler; when the signal handler returns, the system will restore the calling process's signal mask to its state prior to the delivery of the signal.
<code>signo</code> will be removed from the calling process's signal mask.
</p>
<p>
NOTE: The value <code>SIG_HOLD</code> for <code>disp</code> is not currently supported.
@@ -5341,7 +5341,7 @@ interface of the same name.
</pre>
<p>
<b>Description:</b> The sighold() function will add <code>signo</code> to the calling process' signal mask
<b>Description:</b> The sighold() function will add <code>signo</code> to the calling process's signal mask
</p>
<p>
<b>Input Parameters:</b>
@@ -5365,7 +5365,7 @@ interface of the same name.
</pre>
<p>
<b>Description:</b> The sighold() function will remove <code>signo</code> from the calling process' signal mask
<b>Description:</b> The sighold() function will remove <code>signo</code> from the calling process's signal mask
</p>
<p>
<b>Input Parameters:</b>
@@ -5474,8 +5474,8 @@ is required in the present implementation (even if the signal is ignored).
</pre>
<p>
<b>Description:</b> The <code>sigpause()</code>) function will remove <code>signo</code>) from the calling process' signal mask and suspend the calling process until a signal is received.
The <code>sigpause()</code>) function will restore the process' signal mask to its original state before returning.
<b>Description:</b> The <code>sigpause()</code>) function will remove <code>signo</code>) from the calling process's signal mask and suspend the calling process until a signal is received.
The <code>sigpause()</code>) function will restore the process's signal mask to its original state before returning.
<p>
<b>Input Parameters:</b>
<ul>
@@ -6329,14 +6329,14 @@ interface of the same name.
<b>Description:</b>
<p>The <code>pthread_cancel()</code> function will request that thread be canceled.
The target thread's cancelability state, enabled, or disabled, determines when the cancellation takes effect: When the cancellation is acted on, thread will be terminated.
When cancelability is disabled, all cancellations are held pending in the target thread until the thread re-enables cancelability.</p>
The target thread's cancellability state, enabled, or disabled, determines when the cancellation takes effect: When the cancellation is acted on, thread will be terminated.
When cancellability is disabled, all cancellations are held pending in the target thread until the thread re-enables cancellability.</p>
<p>The target thread's cancelability state determines how the cancellation is acted on:
<p>The target thread's cancellability state determines how the cancellation is acted on:
Either asychronrously or deferred.
Asynchronous cancellations we be acted upon immediately (when enabled), interrupting the thread with its processing in an abritray state.</p>
<p>When cancelability is deferred, all cancellations are held pending in the target thread until the thread changes the cancelability type or a <a href="http://www.nuttx.org/doku.php?id=wiki:nxinternal:cancellation-points">Cancellation Point</a> function such as <a href="#pthreadtestcancel"><code>pthread_testcancel()</code></a> is entered.</p>
<p>When cancellability is deferred, all cancellations are held pending in the target thread until the thread changes the cancellability type or a <a href="http://www.nuttx.org/doku.php?id=wiki:nxinternal:cancellation-points">Cancellation Point</a> function such as <a href="#pthreadtestcancel"><code>pthread_testcancel()</code></a> is entered.</p>
<p>
<b>Input Parameters:</b>
@@ -6376,8 +6376,8 @@ These destructors are not currently supported.</li>
</p>
<p>
The <code>pthread_setcancelstate()</code> function atomically
sets both the calling thread's cancelability state to the indicated
state and returns the previous cancelability state at the location
sets both the calling thread's cancellability state to the indicated
state and returns the previous cancellability state at the location
referenced by oldstate.
Legal values for state are PTHREAD_CANCEL_ENABLE and PTHREAD_CANCEL_DISABLE.
</p>
@@ -6421,11 +6421,11 @@ interface of the same name.
</pre>
<p>
<b>Description:</b>
The <code>pthread_setcanceltype()</code> function atomically both sets the calling thread's cancelability type to the indicated type and returns the previous cancelability type at the location referenced by <code>oldtype</code>.
The <code>pthread_setcanceltype()</code> function atomically both sets the calling thread's cancellability type to the indicated type and returns the previous cancellability type at the location referenced by <code>oldtype</code>.
Legal values for type are <code>PTHREAD_CANCEL_DEFERRED</code> and <code>PTHREAD_CANCEL_ASYNCHRONOUS</code>.
</p>
<p>
The cancelability state and type of any newly created threads are <code>PTHREAD_CANCEL_ENABLE</code> and <code>PTHREAD_CANCEL_DEFERRED respectively</code>.
The cancellability state and type of any newly created threads are <code>PTHREAD_CANCEL_ENABLE</code> and <code>PTHREAD_CANCEL_DEFERRED respectively</code>.
</p>
<p>
<b>Input Parameters:</b>
@@ -6464,7 +6464,7 @@ returned to indicate the error.
</p>
<p>
The <code>pthread_testcancel()</code> function creates a <a href="http://www.nuttx.org/doku.php?id=wiki:nxinternal:cancellation-points">Cancellation Point</a> in the calling thread.
The <code>pthread_testcancel()</code> function has no effect if cancelability is disabled.
The <code>pthread_testcancel()</code> function has no effect if cancellability is disabled.
</p>
<p>
<b>Input Parameters:</b> None
@@ -9771,7 +9771,7 @@ ssize_t recvfrom(int sockfd, void *buf, size_t len, int flags,
<b>Returned Value:</b>
On success, returns the number of characters sent.
If no data is available to be received and the peer has performed an orderly shutdown, recv() will return 0.
Othwerwise, on errors, -1 is returned, and <a href="#ErrnoAccess"><code>errno</code></a> is set appropriately:
Otherwise, on errors, -1 is returned, and <a href="#ErrnoAccess"><code>errno</code></a> is set appropriately:
</p>
<ul>
<li><code>EAGAIN</code>.
Kconfig
+3 -3
View File
@@ -64,7 +64,7 @@ config WINDOWS_NATIVE
depends on EXPERIMENTAL
---help---
Build natively in a CMD.exe environment with Windows style paths
(like C:\cgywin\home)
(like C:\cygwin\home)
The Windows native build is complete and available, but not often
used or verified. As a consequence, it cannot be assured to be
@@ -81,7 +81,7 @@ config WINDOWS_CYGWIN
config WINDOWS_UBUNTU
bool "Ubuntu under Windows 10"
---help---
Build natively in an Ubuntu shell under Windoes 10 environment with
Build natively in an Ubuntu shell under Windows 10 environment with
POSIX style paths (like /mnt/c/Program Files)
config WINDOWS_MSYS
@@ -89,7 +89,7 @@ config WINDOWS_MSYS
select TOOLCHAIN_WINDOWS
---help---
Build natively in a Cygwin environment with POSIX style paths (like
/cygdrive/c/cgywin/home)
/cygdrive/c/cygwin/home)
config WINDOWS_OTHER
bool "Windows POSIX-like environment"
README.txt
+1 -1
View File
@@ -232,7 +232,7 @@ Using MSYS
4. mklink /j programfiles86 "C:/Program\ Files\ \(x86\)"
They then show up as /programfiles and /programfiles86 with the MSYS2
sandbox. Thos paths can then be used with the PATH variable. I had
sandbox. Those paths can then be used with the PATH variable. I had
to do something similar for the path to the GNU Tools "ARM Embedded
Toolchain" which also has spaces in the path name.
ReleaseNotes
+103 -103
View File
File diff suppressed because it is too large Load Diff
TODO
+12 -12
View File
@@ -27,7 +27,7 @@ nuttx/:
(12) File system/Generic drivers (fs/, drivers/)
(10) Graphics Subsystem (graphics/)
(1) Build system / Toolchains
(3) Linux/Cywgin simulation (arch/sim)
(3) Linux/Cygwin simulation (arch/sim)
(5) ARM (arch/arm/)
apps/ and other Add-Ons:
@@ -473,7 +473,7 @@ o Task/Scheduler (sched/)
2. Then when either the ELF program task or the created task
in the same address environment exits, it would decrement
the reference count. When the last task exits, the reference
count would go to zero and the address environement could be
count would go to zero and the address environment could be
destroyed.
This is complex work and would take some effort and probably
@@ -571,7 +571,7 @@ o SMP
The returned CPU number is then used for various things,
typically as an array index. However, if pre-emption is
not disabled,then it is possible that a context switch
could occur and that logic could run on anothe CPU with
could occur and that logic could run on another CPU with
possible fatal consequences.
We need to evaluate all use of this_cpu() and assure that
@@ -579,7 +579,7 @@ o SMP
to execute on the same CPU.
Status: Open
Prioity: Medium. This is a logical problem but I have nevers seen
Prioity: Medium. This is a logical problem but I have never seen
an bugs caused by this. But I believe that failures are
possible.
@@ -640,7 +640,7 @@ o SMP
That is really not as much work as it sounds. It is
something that could be done in 2-3 days of work if you know
what you are doing. Getting the proper test setup and
verifying the cahnge would be the more difficult task.
verifying the change would be the more difficult task.
Status: Open
Priority: Unknown. Might be high, but first we would need to confirm
@@ -791,7 +791,7 @@ o Signals (sched/signal, arch/)
Priority: Low. Even if there are only 31 usable signals, that is still a lot.
Title: NO QUEUING of SIGNAL ACTIONS
Description: In the architecture specific implemenation of struct xcptcontext,
Description: In the architecture specific implementation of struct xcptcontext,
there are fields used by signal handling logic to pass the state
information needed to dispatch signal actions to the appropriate
handler.
@@ -807,7 +807,7 @@ o Signals (sched/signal, arch/)
very low.
Title: QUEUED SIGNAL ACTIONS ARE INAPPROPRIATELY DEFERRED
Descirption: The implement of nxsig_deliver() does the followin in a loop:
Description: The implement of nxsig_deliver() does the following in a loop:
- It takes the next next queued signal action from a list
- Calls the architecture-specific up_sigdeliver() to perform
the signal action (through some sleight of hand in
@@ -819,7 +819,7 @@ o Signals (sched/signal, arch/)
uninterrupted thread instead of returning to nxsig_deliver().
The loop in nxsig_deliver() then will have the opportunity to
run until when that normal, uniterrupted thread is suspended.
run until when that normal, uninterrupted thread is suspended.
Then the loop will continue with the next queued signal
action.
@@ -2471,7 +2471,7 @@ o Graphics Subsystem (graphics/)
incomplete. In fact, many recent changes explicitly assume a
single color plane: Planar colors are specified by a array
of components; some recent logic uses only component [0],
ignoring the possible existence of other color componet frames.
ignoring the possible existence of other color component frames.
Completely removing planar color support is one reasonable
options; it is not likely that NuttX will encounter planar
@@ -2528,7 +2528,7 @@ o Other drivers (drivers/)
Priority: Low, provided that the application can handle these characters
in the data stream.
o Linux/Cywgin simulation (arch/sim)
o Linux/Cygwin simulation (arch/sim)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Title: SIMULATOR HAS NO INTERRUPTS (NON-PREMPTIBLE)
@@ -2709,7 +2709,7 @@ o ARM (arch/arm/)
Title: USE COMMON VECTOR LOGIC IN ALL ARM ARCHITECTURES.
Description: Originally, each ARMv7-M MCU architecture had its own
private implementation for interrupt vectors and interrupt
handling logic. This was superceded by common interrupt
handling logic. This was superseded by common interrupt
vector logic but these private implementations were never
removed from older MCU architectures. This is turning into
a maintenance issue because any improvements to the common
@@ -2784,7 +2784,7 @@ o Other Applications & Tests (apps/examples/)
Title: EXAMPLES/PIPE ON CYGWIN
Description: The redirection test (part of examples/pipe) terminates
incorrectly on the Cywgin-based simulation platform (but works
incorrectly on the Cygwin-based simulation platform (but works
fine on the Linux-based simulation platform).
Status: Open
Priority: Low
arch/Kconfig
+2 -2
View File
@@ -77,7 +77,7 @@ config ARCH_SIM
select ONESHOT
select SERIAL_CONSOLE
---help---
Linux/Cywgin user-mode simulation.
Linux/Cygwin user-mode simulation.
config ARCH_X86
bool "x86"
@@ -462,7 +462,7 @@ config ARCH_KERNEL_STACKSIZE
int "Kernel stack size"
default 1568
---help---
The common size of each process' kernel stack
The common size of each process's kernel stack
endif # ARCH_KERNEL_STACK
arch/arm/Kconfig
+1 -1
View File
@@ -830,7 +830,7 @@ config ARM_LWL_CONSOLE
for openocd as the debugger is available in tools/ocdconsole.py.
Currently only available for STM32 architectures, but easily
added to other ARM architectures be addd up_low_console.c to the
added to other ARM architectures be add up_low_console.c to the
architecture Make.defs file.
if ARCH_CORTEXM0
arch/arm/include/cxd56xx/audio.h
+1 -1
View File
@@ -742,7 +742,7 @@ CXD56_AUDIO_ECODE cxd56_audio_free_dmahandle(FAR cxd56_audio_dma_t handle);
/* Set internal data path
*
* sig: Internal singal type
* sig: Internal signal type
* sel: Internal selector type
*
* CXD56_AUDIO_ECODE return code
arch/arm/include/cxd56xx/geofence.h
+2 -2
View File
@@ -212,7 +212,7 @@ struct cxd56_geofence_trans_s
uint8_t status;
};
/* Geofence output data structer. */
/* Geofence output data structure. */
struct cxd56_geofence_status_s
{
@@ -220,7 +220,7 @@ struct cxd56_geofence_status_s
uint8_t update;
/* The detail data od updated region ID */
/* The detail data of updated region ID */
struct cxd56_geofence_trans_s status[CXD56_GEOFENCE_REGION_CAPACITY];
};
arch/arm/include/cxd56xx/gnss.h
+3 -3
View File
@@ -374,7 +374,7 @@ extern "C"
#define CXD56_GNSS_IOCTL_AGPS_SET_FRAMETIME 32
/* Set tau_GPS(&tau;GPS: Differnece of system time between GPS and Glonass
/* Set tau_GPS(&tau;GPS: Difference of system time between GPS and Glonass
* system).
*
* param[in] arg
@@ -792,7 +792,7 @@ struct cxd56_gnss_test_result_s
float doppler; /* Doppler [Hz] */
};
/* signal setting for reading data asychronously
/* signal setting for reading data asynchronously
* The field 'enable' of struct #cxd56_gnss_signal_setting_s to be given as a
* parameter must be specified as 1 when setting and 0 when unsetting.
* Field 'gnsssig' specifies the value of 'Signal types from GNSS',
@@ -810,7 +810,7 @@ struct cxd56_gnss_signal_setting_s
FAR void *data; /* user data */
};
/* Information for use after being signaled to read data asychronously */
/* Information for use after being signaled to read data asynchronously */
struct cxd56_gnss_signal_info_s
{
arch/arm/include/cxd56xx/pm.h
+2 -2
View File
@@ -311,7 +311,7 @@ uint32_t up_pm_get_bootmask(void);
* Enable the boot cause of the specified bit.
*
* Parameter:
* mask - OR of Boot mask definied as PM_BOOT_XXX
* mask - OR of Boot mask defined as PM_BOOT_XXX
*
* Return:
* Updated boot mask
@@ -327,7 +327,7 @@ uint32_t up_pm_set_bootmask(uint32_t mask);
* Disable the boot cause of the specified bit.
*
* Parameter:
* mask - OR of Boot mask definied as PM_BOOT_XXX
* mask - OR of Boot mask defined as PM_BOOT_XXX
*
* Return:
* Updated boot mask
arch/arm/include/cxd56xx/scu.h
+1 -1
View File
@@ -392,7 +392,7 @@ struct scufifo_wm_s
{
int signo; /*< Signal number (0 - 31, except system reserved) */
/* Pointer to memomry to be timestamp stored */
/* Pointer to memory to be timestamp stored */
FAR struct scutimestamp_s *ts;
arch/arm/include/imx6/chip.h
+5 -5
View File
@@ -61,7 +61,7 @@
# undef IMX_HAVE_DDR32 /* 32-bit DDR3 */
# define IMX_HAVE_DDR32x2 1 /* Two channel 32-bit DDR3 */
# define IMX_HAVE_SATAII 1 /* Integrated SATA-II */
# undef IMX_HAVE_EPD /* No interated EPD controller */
# undef IMX_HAVE_EPD /* No integrated EPD controller */
#elif defined(CONFIG_ARCH_CHIP_IMX6_6DUAL)
# define IMX_OCRAM_SIZE (256*1024) /* Size of the On-Chip RAM (OCRAM) */
# define IMX_L2CACHE_SIZE (1024*1024) /* 1MB L2 Cache */
@@ -73,7 +73,7 @@
# undef IMX_HAVE_DDR32 /* 32-bit DDR3 */
# define IMX_HAVE_DDR32x2 1 /* Two channel 32-bit DDR3 */
# define IMX_HAVE_SATAII 1 /* Integrated SATA-II */
# undef IMX_HAVE_EPD /* No interated EPD controller */
# undef IMX_HAVE_EPD /* No integrated EPD controller */
#elif defined(CONFIG_ARCH_CHIP_IMX6_6DUALLITE)
# define IMX_OCRAM_SIZE (256*1024) /* Size of the On-Chip RAM (OCRAM) */
# define IMX_L2CACHE_SIZE (512*1024) /* 512KB L2 Cache */
@@ -85,7 +85,7 @@
# undef IMX_HAVE_DDR32 /* No 32-bit DDR3 */
# define IMX_HAVE_DDR32x2 1 /* Two channel 32-bit DDR3 */
# undef IMX_HAVE_SATAII /* No integrated SATA-II */
# define IMX_HAVE_EPD 1 /* Interated EPD controller */
# define IMX_HAVE_EPD 1 /* Integrated EPD controller */
#elif defined(CONFIG_ARCH_CHIP_IMX6_6SOLO)
# define IMX_OCRAM_SIZE (256*1024) /* Size of the On-Chip RAM (OCRAM) */
# define IMX_L2CACHE_SIZE (512*1024) /* 512KB L2 Cache */
@@ -97,7 +97,7 @@
# define IMX_HAVE_DDR32 1 /* 32-bit DDR3 */
# undef IMX_HAVE_DDR32x2 /* No two channel 32-bit DDR3 */
# undef IMX_HAVE_SATAII /* No integrated SATA-II */
# define IMX_HAVE_EPD 1 /* Interated EPD controller */
# define IMX_HAVE_EPD 1 /* Integrated EPD controller */
#elif defined(CONFIG_ARCH_CHIP_IMX6_6SOLOLITE)
# define IMX_OCRAM_SIZE (256*1024) /* Size of the On-Chip RAM (OCRAM) */
# define IMX_L2CACHE_SIZE (256*1024) /* 256KB L2 Cache */
@@ -109,7 +109,7 @@
# define IMX_HAVE_DDR32 1 /* 32-bit DDR3 */
# undef IMX_HAVE_DDR32x2 /* No two channel 32-bit DDR3 */
# undef IMX_HAVE_SATAII /* No integrated SATA-II */
# define IMX_HAVE_EPD 1 /* Interated EPD controller */
# define IMX_HAVE_EPD 1 /* Integrated EPD controller */
#else
# error Unspecified i.MX6 chip
#endif
arch/arm/include/kl/irq.h
+2 -2
View File
@@ -116,7 +116,7 @@
/* Note that the total number of IRQ numbers supported is equal to the number of
* valid interrupt vectors. This is wasteful in that certain tables are sized by
* this value. There are only 94 valid interrupts so, potentially the numver of
* this value. There are only 94 valid interrupts so, potentially the number of
* IRQs to could be reduced to 94. However, equating IRQ numbers with vector numbers
* also simplifies operations on NVIC registers and (at least in my state of mind
* now) seems to justify the waste.
@@ -161,7 +161,7 @@
/* Note that the total number of IRQ numbers supported is equal to the number of
* valid interrupt vectors. This is wasteful in that certain tables are sized by
* this value. There are only 94 valid interrupts so, potentially the numver of
* this value. There are only 94 valid interrupts so, potentially the number of
* IRQs to could be reduced to 94. However, equating IRQ numbers with vector numbers
* also simplifies operations on NVIC registers and (at least in my state of mind
* now) seems to justify the waste.
arch/arm/include/max326xx/chip.h
+9 -9
View File
@@ -76,9 +76,9 @@
/* Peripherals */
# define MAX326_NWDOG 0 /* No Watchog Timers */
# define MAX326_NWWDOG 2 /* Two Windowed Watchog Timers */
# define MAX326_NRWDOG 1 /* One Recovery Watchog Timer */
# define MAX326_NWDOG 0 /* No Watchdog Timers */
# define MAX326_NWWDOG 2 /* Two Windowed Watchdog Timers */
# define MAX326_NRWDOG 1 /* One Recovery Watchdog Timer */
# define MAX326_NWAKEUP 1 /* One Wakeup Timer */
# define MAX326_NRTC 1 /* One RTC */
# define MAX326_NCRC 1 /* One CRC16/32 */
@@ -115,9 +115,9 @@
/* Peripherals */
# define MAX326_NWDOG 0 /* No Watchog Timers */
# define MAX326_NWWDOG 2 /* Two Windowed Watchog Timers */
# define MAX326_NRWDOG 0 /* No Recovery Watchog Timer */
# define MAX326_NWDOG 0 /* No Watchdog Timers */
# define MAX326_NWWDOG 2 /* Two Windowed Watchdog Timers */
# define MAX326_NRWDOG 0 /* No Recovery Watchdog Timer */
# define MAX326_NWAKEUP 1 /* One Wakeup Timer */
# define MAX326_NRTC 1 /* One RTC */
# define MAX326_NCRC 1 /* One CRC16/32 */
@@ -164,9 +164,9 @@
/* Peripherals */
# define MAX326_NWDOG 1 /* One Watchog Timer */
# define MAX326_NWWDOG 0 /* No Windowed Watchog Timers */
# define MAX326_NRWDOG 0 /* No Recovery Watchog Timer */
# define MAX326_NWDOG 1 /* One Watchdog Timer */
# define MAX326_NWWDOG 0 /* No Windowed Watchdog Timers */
# define MAX326_NRWDOG 0 /* No Recovery Watchdog Timer */
# define MAX326_NWAKEUP 0 /* No Wakeup Timer */
# define MAX326_NRTC 1 /* One RTC */
# define MAX326_NCRC 0 /* No CRC16/32 */
arch/arm/include/stm32f0l0g0/stm32l0_irq.h
+1 -1
View File
@@ -96,7 +96,7 @@
#define STM32_IRQ_USART2 (STM32_IRQ_EXTINT + 28) /* 28: USART2 global interrupt */
#define STM32_IRQ_LPUART1 (STM32_IRQ_EXTINT + 29) /* 29: LPUART1 global interrupt */
#define STM32_IRQ_AES (STM32_IRQ_EXTINT + 29) /* 29: AES global interrupt */
#define STM32_IRQ_RNG (STM32_IRQ_EXTINT + 29) /* 29: RNG gloabl interrupt */
#define STM32_IRQ_RNG (STM32_IRQ_EXTINT + 29) /* 29: RNG global interrupt */
#define STM32_IRQ_LCD (STM32_IRQ_EXTINT + 30) /* 30: LCD global interrupt */
#define STM32_IRQ_USB (STM32_IRQ_EXTINT + 31) /* 31: USB global interrupt */
arch/arm/src/a1x/a1x_boot.c
+1 -1
View File
@@ -240,7 +240,7 @@ static void a1x_copyvectorblock(void)
uint32_t *dest;
/* If we are using re-mapped vectors in an area that has been marked
* read only, then temparily mark the mapping write-able (non-buffered).
* read only, then temporarily mark the mapping write-able (non-buffered).
*/
#ifdef CONFIG_PAGING
arch/arm/src/a1x/a1x_serial.c
+1 -1
View File
@@ -1430,7 +1430,7 @@ static bool up_txempty(struct uart_dev_s *dev)
}
/****************************************************************************
* Public Funtions
* Public Functions
****************************************************************************/
#ifdef USE_EARLYSERIALINIT
arch/arm/src/a1x/hardware/a10_memorymap.h
+1 -1
View File
@@ -296,7 +296,7 @@
/* A1X Virtual (mapped) Memory Map
*
* board_memorymap.h contains special mappings that are needed when a ROM
* memory map is used. It is included in this odd location becaue it depends
* memory map is used. It is included in this odd location because it depends
* on some the virtual address definitions provided above.
*/
arch/arm/src/a1x/hardware/a1x_intc.h
+1 -1
View File
@@ -164,7 +164,7 @@
#define INTC_NMICTRL_SRCTYPE_SHIFT (0) /* Bits 0-1: External NMI Interrupt Source Type */
#define INTC_NMICTRL_SRCTYPE_MASK (3 << INTC_NMICTRL_SRCTYPE_SHIFT)
# define INTC_NMICTRL_SRCTYPE_LOW (0 << INTC_NMICTRL_SRCTYPE_SHIFT) /* Low level sensitive */
# define INTC_NMICTRL_SRCTYPE_NEDGE (1 << INTC_NMICTRL_SRCTYPE_SHIFT) /* Negative edge trigged */
# define INTC_NMICTRL_SRCTYPE_NEDGE (1 << INTC_NMICTRL_SRCTYPE_SHIFT) /* Negative edge triggered */
/* Interrupt IRQ Pending 0-2 Status */
arch/arm/src/am335x/am335x_can.c
+1 -1
View File
@@ -592,7 +592,7 @@ static int can_remoterequest(FAR struct can_dev_s *dev, uint16_t id)
*
* Byte 0: Bits 0-7: Bits 3-10 of the 11-bit CAN identifier
* Byte 1: Bits 5-7: Bits 0-2 of the 11-bit CAN identifier
* Bit 4: Remote Tranmission Request (RTR)
* Bit 4: Remote Transmission Request (RTR)
* Bits 0-3: Data Length Code (DLC)
* Bytes 2-10: CAN data
*
arch/arm/src/arm/up_cache.S
+1 -1
View File
@@ -6,7 +6,7 @@
*
* Several of these cache operations come from Atmel sample code with
* modifications for better integration with NuttX. The Atmel sample code
* has a BSD compatibile license that requires this copyright notice:
* has a BSD compatible license that requires this copyright notice:
*
* Copyright (c) 2008, Atmel Corporation
*
arch/arm/src/arm/up_head.S
+1 -1
View File
@@ -588,7 +588,7 @@ __start:
strcc fp, [r0],#4
bcc .Lbssinit
/* If the .data section is in a separate, unitialized address space,
/* If the .data section is in a separate, uninitialized address space,
* then we will also need to copy the initial values of of the .data
* section from the .text region into that .data region. This would
* be the case if we are executing from FLASH and the .data section
arch/arm/src/arm/up_saveusercontext.S
+1 -1
View File
@@ -83,7 +83,7 @@ up_saveusercontext:
/* Make sure that the return value will be non-zero (the
* value of the other volatile registers don't matter --
* r1-r3, ip). This function is called through the
* noraml C calling conventions and the values of these
* normal C calling conventions and the values of these
* registers cannot be assumed at the point of setjmp
* return.
*/
arch/arm/src/arm/vfork.S
+1 -1
View File
@@ -77,7 +77,7 @@
* - Allocation of the child task's TCB.
* - Initialization of file descriptors and streams
* - Configuration of environment variables
* - Setup the intput parameters for the task.
* - Setup the input parameters for the task.
* - Initialization of the TCB (including call to up_initial_state()
* 4) up_vfork() provides any additional operating context. up_vfork must:
* - Allocate and initialize the stack
arch/arm/src/armv6-m/up_svcall.c
+1 -1
View File
@@ -178,7 +178,7 @@ int up_svcall(int irq, FAR void *context, FAR void *arg)
* R0 = SYS_save_context
* R1 = saveregs
*
* In this case, we simply need to copy the current regsters to the
* In this case, we simply need to copy the current registers to the
* save register space references in the saved R1 and return.
*/
arch/arm/src/armv6-m/up_unblocktask.c
+1 -1
View File
@@ -63,7 +63,7 @@
* Input Parameters:
* tcb: Refers to the tcb to be unblocked. This tcb is in one of the
* waiting tasks lists. It must be moved to the ready-to-run list and,
* if it is the highest priority ready to run taks, executed.
* if it is the highest priority ready to run task, executed.
*
****************************************************************************/
arch/arm/src/armv6-m/vfork.S
+1 -1
View File
@@ -78,7 +78,7 @@
* - Allocation of the child task's TCB.
* - Initialization of file descriptors and streams
* - Configuration of environment variables
* - Setup the intput parameters for the task.
* - Setup the input parameters for the task.
* - Initialization of the TCB (including call to up_initial_state()
* 4) up_vfork() provides any additional operating context. up_vfork must:
* - Allocate and initialize the stack
arch/arm/src/armv7-a/arm_addrenv.c
+1 -1
View File
@@ -284,7 +284,7 @@ int up_addrenv_create(size_t textsize, size_t datasize, size_t heapsize,
}
/* Allocate .bss/.data space pages. NOTE that a configurable offset is
* added to the allocted size. This is matched by the offset that is
* added to the allocated size. This is matched by the offset that is
* used when reporting the virtual data address in up_addrenv_vdata().
*/
arch/arm/src/armv7-a/arm_cpupause.c
+1 -1
View File
@@ -151,7 +151,7 @@ int up_cpu_paused(int cpu)
spin_unlock(&g_cpu_paused[cpu]);
/* Wait for the spinlock to be released. The requesting CPU will release
* the spinlcok when the CPU is resumed.
* the spinlock when the CPU is resumed.
*/
spin_lock(&g_cpu_wait[cpu]);
arch/arm/src/armv7-a/arm_cpustart.c
+1 -1
View File
@@ -143,7 +143,7 @@ int arm_start_handler(int irq, FAR void *context, FAR void *arg)
*
* Each CPU is provided the entry point to is IDLE task when started. A
* TCB for each CPU's IDLE task has been initialized and placed in the
* CPU's g_assignedtasks[cpu] list. Not stack has been alloced or
* CPU's g_assignedtasks[cpu] list. Not stack has been allocated or
* initialized.
*
* The OS initialization logic calls this function repeatedly until each
arch/arm/src/armv7-a/arm_l2cc_pl310.c
+1 -1
View File
@@ -179,7 +179,7 @@
/* Bit 26: Non-Secure Lockdown Enable
*
* Default: 0=Lockdown registers cannot be modified using non-secure acceses
* Default: 0=Lockdown registers cannot be modified using non-secure accesses
*/
#define L2CC_ACR_NSLEN_CONFIG (0) /* 0=Secure access only */
arch/arm/src/armv7-a/arm_vfork.S
+1 -1
View File
@@ -79,7 +79,7 @@
* - Allocation of the child task's TCB.
* - Initialization of file descriptors and streams
* - Configuration of environment variables
* - Setup the intput parameters for the task.
* - Setup the input parameters for the task.
* - Initialization of the TCB (including call to up_initial_state()
* 4) up_vfork() provides any additional operating context. up_vfork must:
* - Allocate and initialize the stack
arch/arm/src/armv7-a/cp15_cacheops.h
+5 -5
View File
@@ -158,7 +158,7 @@
#define CACHE_VA_MASK (0xfffffffe0) /* Bits 5-31: Virtual address */
/************************************************************************************
* Assemby Macros
* Assembly Macros
************************************************************************************/
/* cp15_cache Cache Operations
*
@@ -277,7 +277,7 @@
* Name: cp15_invalidate_icache_inner_sharable
*
* Description:
* Invalidate I cache predictor array inner sharable
* Invalidate I cache predictor array inner shareable
*
* Input Parameters:
* None
@@ -296,7 +296,7 @@
* Name: cp15_invalidate_btb_inner_sharable
*
* Description:
* Invalidate entire branch predictor array inner sharable
* Invalidate entire branch predictor array inner shareable
*
* Input Parameters:
* None
@@ -632,7 +632,7 @@ static inline void cp15_disable_icache(void)
* Name: cp15_invalidate_icache_inner_sharable
*
* Description:
* Invalidate I cache predictor array inner sharable
* Invalidate I cache predictor array inner shareable
*
* Input Parameters:
* None
@@ -658,7 +658,7 @@ static inline void cp15_invalidate_icache_inner_sharable(void)
* Name: cp15_invalidate_btb_inner_sharable
*
* Description:
* Invalidate entire branch predictor array inner sharable
* Invalidate entire branch predictor array inner shareable
*
* Input Parameters:
* None
arch/arm/src/armv7-a/mmu.h
+1 -1
View File
@@ -889,7 +889,7 @@ struct section_mapping_s
#endif
/************************************************************************************
* Assemby Macros
* Assembly Macros
************************************************************************************/
#ifdef __ASSEMBLY__
arch/arm/src/armv7-a/mpcore.h
+2 -2
View File
@@ -61,9 +61,9 @@
#define MPCORE_SCU_OFFSET 0x0000 /* 0x0000-0x00fc SCU registers */
#ifdef CONFIG_ARCH_CORTEXA7
#define MPCORE_ICC_OFFSET 0x2000 /* 0x0000-0x00FC Interrupt conroller interface */
#define MPCORE_ICC_OFFSET 0x2000 /* 0x0000-0x00FC Interrupt controller interface */
#else
#define MPCORE_ICC_OFFSET 0x0100 /* 0x0000-0x00FC Interrupt conroller interface */
#define MPCORE_ICC_OFFSET 0x0100 /* 0x0000-0x00FC Interrupt controller interface */
#endif
#define MPCORE_GTM_OFFSET 0x0200 /* 0x0200-0x02ff Global timer */
/* 0x0300-0x05ff Reserved */
arch/arm/src/armv7-a/sctlr.h
+1 -1
View File
@@ -261,7 +261,7 @@
/* TODO: To be provided */
/************************************************************************************
* Assemby Macros
* Assembly Macros
************************************************************************************/
#ifdef __ASSEMBLY__
arch/arm/src/armv7-m/Kconfig
+1 -1
View File
@@ -78,7 +78,7 @@ config ARMV7M_BASEPRI_WAR
This update is required to be serialized to the instruction stream
meaning that after this update completes, it takes effect
immediately and no exceptions of lower priority than the new boosted
priority can pre-empt execution. Because of this erratum, the
priority can preempt execution. Because of this erratum, the
priority boosting does not take place immediately, allowing the
instruction after the MSR to be interrupted by an exception of
lower priority than the new boosted priority. This effect is only
arch/arm/src/armv7-m/etm.h
+1 -1
View File
@@ -276,7 +276,7 @@
#define _ETM_ETMCCR_TRACESS_MASK 0x4000000UL /* Bit mask for ETM_TRACESS */
#define _ETM_ETMCCR_TRACESS_DEFAULT 0x00000001UL /* Mode DEFAULT for ETM_ETMCCR */
#define ETM_ETMCCR_TRACESS_DEFAULT (_ETM_ETMCCR_TRACESS_DEFAULT << 26) /* Shifted mode DEFAULT for ETM_ETMCCR */
#define ETM_ETMCCR_MMACCESS (0x1UL << 27) /* Coprocessor and Memeory Access */
#define ETM_ETMCCR_MMACCESS (0x1UL << 27) /* Coprocessor and Memory Access */
#define _ETM_ETMCCR_MMACCESS_SHIFT 27 /* Shift value for ETM_MMACCESS */
#define _ETM_ETMCCR_MMACCESS_MASK 0x8000000UL /* Bit mask for ETM_MMACCESS */
#define _ETM_ETMCCR_MMACCESS_DEFAULT 0x00000001UL /* Mode DEFAULT for ETM_ETMCCR */
arch/arm/src/armv7-m/gnu/up_setjmp.S
+1 -1
View File
@@ -120,7 +120,7 @@ setjmp:
* control back to the point where setjmp() was called and to restore ("rewind")
* the stack to its state at the time of the setjmp() call. When control is
* passed back to where setjmp() had been called, setjmp() will return with
* 'val', the second paramater passed to longjmp().
* 'val', the second parameter passed to longjmp().
*
* C Function Prototype:
* void longjmp(jmp_buf env, int val);
arch/arm/src/armv7-m/gnu/vfork.S
+1 -1
View File
@@ -79,7 +79,7 @@
* - Allocation of the child task's TCB.
* - Initialization of file descriptors and streams
* - Configuration of environment variables
* - Setup the intput parameters for the task.
* - Setup the input parameters for the task.
* - Initialization of the TCB (including call to up_initial_state()
* 4) up_vfork() provides any additional operating context. up_vfork must:
* - Allocate and initialize the stack

Some files were not shown because too many files have changed in this diff Show More