nuttx/nuttx-mirror
1
2
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2025-01-13 10:58:49 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions

Correct mispellings of pseudo. Update some comments in signal.h.

Browse source
This commit is contained in:
Gregory Nutt 2018-09-05 11:56:14 -06:00
parent 9348f600ee
commit 33e3fb7a70
6 changed files with 38 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
ChangeLog
View file

@ -3379,7 +3379,7 @@
now functional.
* configs/fire-stm32v2: Add support or the fire-stm32v3 board as
well (untested because I do not have a v3 board).
* lib/stdio/lib_sscanf.c: Add %n psuedo-format (from Kate).
* lib/stdio/lib_sscanf.c: Add %n pseudo-format (from Kate).
* lib/stdio/lib_sscanf.c: There is an issue of handling input
when (1) no fieldwidth is provided and (2) there is no space
seperating the input values. No solutions is in place for this
@ -10578,7 +10578,7 @@
was calling stm32_pw_setvos() which accessed PWR_CR via an inactive APB
From Juha Niskaneni (2015-06-11).
* fs/mount: Add the ability to mount a file system on top of en existing
node in the psuedo-file system (2015-06-11).
node in the pseudo-file system (2015-06-11).
* arch/arm/src/sam34/sam_clockconfig.c: Add default loop optimization if
EEFC_FMR is available in the configuration (i.e., for SAM4S and 4E).
From Marco Aurélio da Cruz (2015-06-11).
@ -13661,7 +13661,7 @@
(2017-02-05).
* tools/noteinfo.c: A hack tool that I use to analyze some sched_note
output. Needs a home and may be useful to others (2017-02-05).
* Pseudo File System: Add support for soft links in the top-level psuedo
* Pseudo File System: Add support for soft links in the top-level pseudo
file system (2017-02-05).
* Updates to Kinetis SDHC driver. From Marc Rechté (2017-02-06).
* SDIO interface: Handle all possible DMA combinations in all SDIO drivers
@ -17781,7 +17781,7 @@
* fs/userfs: This commit converts the underlying IPC used by the
UserFS from Unix domain local sockets to UDP LocalHost loopback
sockets. The problem with the local sockets is that they do require
operations on the top level psuedo-file system inode tree. That tree
operations on the top level pseudo-file system inode tree. That tree
must be locked during certain traversals such as enumerate mountpoints
or enumerating directory entries.

6
ReleaseNotes
View file

@ -9283,7 +9283,7 @@ Additional new features and extended functionality:
* File Systems/Block Drivers/MTD:
- mount: Add the ability to mount a file system on top of en existing
node in the psuedo-file system.
node in the pseudo-file system.
- epoll(): Add a very simple epoll layer just around poll calls. To
satisfy build app requirements. From Anton D. Kachalov.
@ -13135,7 +13135,7 @@ Additional new features and extended functionality:
* File Systems/Block and MTD Drivers
- Pseudo File System: Add support for soft links in the top-level
psuedo file system.
pseudo file system.
- Soft links: Add an implementation of readlink().
- Add fstat() support. Implement fstat() method in binfs, romfs,
unionfs, tmpfs, nxffs, nfx, hostfs, procfs, and smartfs.
@ -15697,7 +15697,7 @@ Additional new features and extended functionality:
message queues. However, that lead to certain inescapable deadlock
conditions So the IPC was converted to UDP LocalHost loopback
sockets. The problem with the local sockets is that they do require
operations on the top level psuedo-file system inode tree. That
operations on the top level pseudo-file system inode tree. That
tree must be locked during certain traversals such as enumerate
mountpoints or enumerating directory entries. This conversion is
unfortunate in the sense that Unix local domain sockets are

2
TODO
View file

@ -1851,7 +1851,7 @@ o File system / Generic drivers (fs/, drivers/)
link, unlink, softlink, readlink - For symbolic links. Only
the ROMFS file system currently supports hard and soft links,
so this is not too important. The top-level, psuedo-file
so this is not too important. The top-level, pseudo-file
system supports soft links.
File locking

4
configs/sama5d4-ek/README.txt
View file

@ -4495,10 +4495,10 @@ Configurations
| | |- fd : File descriptors open in the group
| | `- status : Status of the group
| |- 1/ : Information about Task ID 1
| | `- ... : Same psuedo-directories as for Task ID 0
| | `- ... : Same pseudo-directories as for Task ID 0
| |- ... : ...
| |- n/ : Information about Task ID n
| | `- ... : Same psuedo-directories as for Task ID 0
| | `- ... : Same pseudo-directories as for Task ID 0
| |- uptime : Processor uptime
`- tmp/

2
fs/driver/fs_blockproxy.c
View file

@ -74,7 +74,7 @@ static sem_t g_devno_sem = SEM_INITIALIZER(1);
*
* Description:
* Create a unique temporary device name in the /dev/ directory of the
* psuedo-file system. We cannot use mktemp for this because it will
* pseudo-file system. We cannot use mktemp for this because it will
* attempt to open() the file.
*
* Input Parameters:

43
include/signal.h
View file

@ -68,39 +68,42 @@
#define SIGRTMIN MIN_SIGNO /* First real time signal */
#define SIGRTMAX MAX_SIGNO /* Last real time signal */
/* NuttX does not support standard signal actions. NuttX supports only what
/* NuttX does not support all standard signal actions. NuttX supports what
* are referred to as "real time" signals. The default action of all NuttX
* signals is to simply ignore the signal.
* signals is to simply ignore the signal. Certain signals can be
* configured to support there default actions as indicated by NOTEs to the
* following table.
*
* This is not POSIX compliant. Per OpenGroup.org: The following signals
* and default signal action s must be supported on all implementations:
* This is not POSIX compliant behavior! Per OpenGroup.org: The following
* signals and default signal action s must be supported on all
* implementations:
*
* ---------- ------- ----------------------------------------------------
* Signal Default Description
* Name Action
* ---------- ------- ----------------------------------------------------
* SIGABRT A Process abort signal
* SIGALRM T Alarm clock
* SIGALRM T (1) Alarm clock
* SIGBUS A Access to an undefined portion of a memory object
* SIGCHLD I Child process terminated, stopped
* (or continued XSI extension)
* SIGCONT C Continue executing, if stopped
* SIGCONT C (2) Continue executing, if stopped
* SIGFPE A Erroneous arithmetic operation
* SIGHUP T Hangup
* SIGILL A Illegal instruction
* SIGINT T Terminal interrupt signal
* SIGKILL T Kill (cannot be caught or ignored)
* SIGINT T (3) Terminal interrupt signal
* SIGKILL T (3) Kill (cannot be caught or ignored)
* SIGPIPE T Write on a pipe with no one to read it
* SIGQUIT A Terminal quit signal
* SIGSEGV A Invalid memory reference
* SIGSTOP S Stop executing (cannot be caught or ignored)
* SIGSTOP S (2) Stop executing (cannot be caught or ignored)
* SIGTERM T Termination signal
* SIGTSTP S Terminal stop signal
* SIGTSTP S (2) Terminal stop signal
* SIGTTIN S Background process attempting read
* SIGTTOU S Background process attempting write
* SIGUSR1 T User-defined signal 1
* SIGUSR2 T User-defined signal 2
* SIGPOLL T Poll-able event (XSI extension)
* SIGUSR1 T (4) User-defined signal 1
* SIGUSR2 T (5) User-defined signal 2
* SIGPOLL T (6) Poll-able event (XSI extension)
* SIGPROF T Profiling timer expired (XSI extension)
* SIGSYS A Bad system call (XSI extension)
* SIGTRAP A Trace/breakpoint trap (XSI extension)
@ -112,21 +115,29 @@
*
* Where default action codes are:
*
* T Abnormal termination of the process. The process is terminated with
* T Abnormal termination of the process. The process is terminated with
* all the consequences of _exit() except that the status made available
* to wait() and waitpid() indicates abnormal termination by the
* specified signal.
* A Abnormal termination of the process. Additionally with the XSI
* A Abnormal termination of the process. Additionally with the XSI
* extension, implementation-defined abnormal termination actions, such
* as creation of a core file, may occur.
* I Ignore the signal.
* S Stop the process.
* C Continue the process, if it is stopped; otherwise, ignore the signal.
*
* NOTES:
* (1) The default action can be enabled with CONFIG_SIG_SIGALRM_ACTION
* (2) The default action can be enabled with CONFIG_SIG_SIGSTOP_ACTION
* (3) The default action can be enabled with CONFIG_SIG_SIGKILL_ACTION
* (4) The default action can be enabled with CONFIG_SIG_SIGUSR1_ACTION
* (5) The default action can be enabled with CONFIG_SIG_SIGUSR2_ACTION
* (6) The default action can be enabled with CONFIG_SIG_SIGPOLL_ACTION
*/
/* A few of the real time signals are used within the OS. They have
* default values that can be overridden from the configuration file. The
* rest are all user signals.
* rest are all standard or user real-time signals.
*
* The signal number zero is wasted for the most part. It is a valid
* signal number, but has special meaning at many interfaces (e.g., Kill()).