diff --git a/Documentation/applications/nsh/commands.rst b/Documentation/applications/nsh/commands.rst index 5b00e091d0..39d642a92c 100644 --- a/Documentation/applications/nsh/commands.rst +++ b/Documentation/applications/nsh/commands.rst @@ -736,7 +736,7 @@ at for the existing file or directory, . This implementation is simplified for use with NuttX in these ways: - Links may be created only within the NuttX top-level, `pseudo - file system `__. No + file system `__. No file system currently supported by NuttX provides symbolic links. - For the same reason, only soft links are implemented. @@ -875,7 +875,7 @@ of ```` except the final directory name must exist on a mounted file system; the final directory must not. **Limited to Mounted File Systems**. Recall that NuttX uses a -`pseudo file system `__ +`pseudo file system `__ for its root file system. The ``mkdir`` command can only be used to create directories in volumes set up with the ```mount`` <#cmdmount>`__ command; it cannot be used to create @@ -916,7 +916,7 @@ zero because the FAT32 root directory is a cluster chain. NSH provides this command to access the ```mkfatfs()`` `__ NuttX API. This block device must reside in the NuttX `pseudo file -system `__ and must have +system `__ and must have been created by some call to ``register_blockdriver()`` (see ``include/nuttx/fs/fs.h``). @@ -933,7 +933,7 @@ be needed to complete the ````. By convention, however, device drivers are place in the standard ``/dev`` directory. After it is created, the FIFO device may be used as any other device driver. NSH provides this command to access the -```mkfifo()`` `__ NuttX API. +```mkfifo()`` `__ NuttX API. **Example**:: @@ -1018,23 +1018,23 @@ way association, binding: supported value for ```` #. **Block Device.** The ```` argument is the full or relative path to a block driver inode in the `pseudo file - system `__. By + system `__. By convention, this is a name under the ``/dev`` sub-directory. This ```` must have been previously formatted with the same file system type as specified by ```` #. **Mount Point.** The mount point, ````, is the location in the `pseudo file - system `__ where the + system `__ where the mounted volume will appear. This mount point can only reside in the NuttX `pseudo file - system `__. By + system `__. By convention, this mount point is a subdirectory under ``/mnt``. The mount command will create whatever pseudo directories that may be needed to complete the full path but the full path must not already exist. After the volume has been mounted in the NuttX `pseudo file -system `__, it may be +system `__, it may be access in the same way as other objects in the file system. **Examples**: @@ -1207,7 +1207,7 @@ Remove a File (rm) **Synopsis**. Remove the specified ```` name from the mounted file system. Recall that NuttX uses a `pseudo file -system `__ for its root +system `__ for its root file system. The ``rm`` command can only be used to remove (unlink) files in volumes set up with the ```mount`` <#cmdmount>`__ command; it cannot be used to remove @@ -1234,7 +1234,7 @@ Remove a Directory (rmdir) **Synopsis**. Remove the specified ```` directory from the mounted file system. Recall that NuttX uses a `pseudo file -system `__ for its root +system `__ for its root file system. The ``rmdir`` command can only be used to remove directories from volumes set up with the ```mount`` <#cmdmount>`__ command; it cannot be used to remove directories from the *pseudo* diff --git a/Documentation/applications/nsh/config.rst b/Documentation/applications/nsh/config.rst index 6e48881e84..a2a277a445 100644 --- a/Documentation/applications/nsh/config.rst +++ b/Documentation/applications/nsh/config.rst @@ -10,7 +10,7 @@ The availability of the above commands depends upon features that may or may not be enabled in the NuttX configuration file. The following `table <#cmddependencies>`__ indicates the dependency of each command on NuttX configuration settings. General configuration settings are -discussed in the `NuttX Porting Guide. `__ +discussed in the `NuttX Porting Guide. `__ Configuration settings specific to NSH as discussed at the `bottom <#nshconfiguration>`__ of this document. diff --git a/Documentation/components/drivers/character/index.rst b/Documentation/components/drivers/character/index.rst index 7ebdfe0ea4..6983fbb0be 100644 --- a/Documentation/components/drivers/character/index.rst +++ b/Documentation/components/drivers/character/index.rst @@ -20,7 +20,7 @@ Character device drivers have these properties: - **User Access**. After it has been registered, the character driver can be accessed by user code using the standard `driver - operations `__ including + operations `__ including ``open()``, ``close()``, ``read()``, ``write()``, etc. - **Specialized Character Drivers**. Within the common character diff --git a/Documentation/components/drivers/special/syslog.rst b/Documentation/components/drivers/special/syslog.rst index a19f3e4b7f..7e27766bd1 100644 --- a/Documentation/components/drivers/special/syslog.rst +++ b/Documentation/components/drivers/special/syslog.rst @@ -467,7 +467,7 @@ debugging output in a circular buffer in RAM. It differs from a pipe in numerous details as needed to support logging. This driver is built when ``CONFIG_RAMLOG`` is defined in the -Nuttx configuration. +NuttX configuration. ``dmesg`` command ----------------- diff --git a/Documentation/components/nxflat.rst b/Documentation/components/nxflat.rst index 9a31823b28..f7547cb53b 100644 --- a/Documentation/components/nxflat.rst +++ b/Documentation/components/nxflat.rst @@ -42,7 +42,7 @@ NXFLAT is derived from `XFLAT `__. XFLAT is a toolchain add that provides full shared library and XIP executable support for processors that have no Memory Management Unit (MMU:sup:`1`). NXFLAT is greatly simplified for the deeply embedded -environment targeted by Nuttx: +environment targeted by NuttX: - NXFLAT does not support shared libraries, because - NXFLAT does not support *exportation* of symbol values from a module @@ -142,7 +142,7 @@ will need version 0.1.7 or later. Here are some general build instructions: -- You must have already configured Nuttx in ``/nuttx`` +- You must have already configured NuttX in ``/nuttx`` - Download the buildroot package ``buildroot-0.x.y`` into ```` - Unpack ``/buildroot-0.x.y.tar.gz`` using a command like ``tar zxf buildroot-0.x.y``. This will result in a new directory like ``/buildroot-0.x.y`` diff --git a/Documentation/guides/nfs.rst b/Documentation/guides/nfs.rst index 8c267f5915..fda1a842e4 100644 --- a/Documentation/guides/nfs.rst +++ b/Documentation/guides/nfs.rst @@ -26,7 +26,7 @@ Mount Interface A low-level, C-callable interface is provided to mount a file system. That interface is called ``mount()`` and is mentioned in the -```porting guide`` `__ and is +```porting guide`` `__ and is prototyped in the header file ``include/sys/mount.h``: .. c:function:: int mount(const char *source, const char *target, const char *filesystemtype, unsigned long mountflags, const void *data) diff --git a/Documentation/guides/simulator.rst b/Documentation/guides/simulator.rst index 1cbfbe47ae..a97ff5586c 100644 --- a/Documentation/guides/simulator.rst +++ b/Documentation/guides/simulator.rst @@ -134,7 +134,7 @@ Accessing the Network need to pick the one that's right for your system. Then, on Linux do this to set up the tap network interface and route that will let - the Apache Nuttx simulator access the network: + the Apache NuttX simulator access the network: .. code-block:: console diff --git a/Documentation/introduction/detailed_support.rst b/Documentation/introduction/detailed_support.rst index 0fd0c6a92c..4c49ff2f83 100644 --- a/Documentation/introduction/detailed_support.rst +++ b/Documentation/introduction/detailed_support.rst @@ -185,7 +185,7 @@ There are ports to two Microchip SAMA5D3 boards: - A full-loaded NuttShell (:ref:`NSH `) configuration that demonstrates all of the SAMA5D3x features. - The following support was added in Nuttx 6.30: + The following support was added in NuttX 6.30: - DMA support, and - PIO interrupts, @@ -973,7 +973,7 @@ Three configurations are available: the STM32F103 or STM32F107 part. #. A network-enabled NuttShell (NSH) configuration that will work only with the STM32F107 part. -#. The configuration that was used to verify the Nuttx `high-priority, +#. The configuration that was used to verify the NuttX `high-priority, nested interrupt feature `__. @@ -1173,7 +1173,7 @@ boards. Zilogic System's ARM development Kit, ZKIT-ARM-1769. This board is based on the NXP LPC1769. The initial release was included - NuttX-6.26. The Nuttx Buildroot toolchain is used by default. Verifed + NuttX-6.26. The NuttX Buildroot toolchain is used by default. Verifed configurations include the "Hello, World!" example application and a THTTPD demonstration. Refer to the NuttX board `README `__ @@ -2455,7 +2455,7 @@ Also refer to the NuttX board `README `__ file for further information about the current state of the port. -Nuttx-9.0 added basic support for Microchip SAME54 Xplained Pro board. +NuttX-9.0 added basic support for Microchip SAME54 Xplained Pro board. An ethernet driver was also added to the SAME5x familly. STMicro STM32 F72x/F73x @@ -3039,7 +3039,7 @@ Parallel-Ultra-Low-Power design. `Sipeed Maix bit <#k210>`__ -Initial support for the Sipeed Maix bit board was added in Nuttx-9.0. +Initial support for the Sipeed Maix bit board was added in NuttX-9.0. LiteX on ARTY A7 ---------------- diff --git a/Documentation/introduction/resources.rst b/Documentation/introduction/resources.rst index fad8152564..8fc4855ff9 100644 --- a/Documentation/introduction/resources.rst +++ b/Documentation/introduction/resources.rst @@ -9,7 +9,7 @@ Here's a list of Apache NuttX resources that you might find helpful: * Apache NuttX * `Apache NuttX website `_ - * `Apache NuttX online documentation `_ + * `Apache NuttX online documentation `_ * `Apache NuttX mailing list `_ – a very active mailing list, the place to get help with your application or any questions you have about NuttX. * `Apache NuttX YouTube channel `_ – Alan Carvalho de Assis's YouTube channel on NuttX. It's a source of a lot of great practical information. * `Apache NuttX Coding Standard `_ — How code should look when you submit new files or modify existing ones. diff --git a/Documentation/quickstart/organization.rst b/Documentation/quickstart/organization.rst index b03d5c2f1d..eaf3b9598f 100644 --- a/Documentation/quickstart/organization.rst +++ b/Documentation/quickstart/organization.rst @@ -316,7 +316,7 @@ contents of these configuration files. which is the path to the root directory of the build. This makefile fragment should include: - - ``$(TOPDIR)/.config`` : Nuttx configuration + - ``$(TOPDIR)/.config`` : NuttX configuration - ``$(TOPDIR)/tools/Config.mk`` : Common definitions Definitions in the ``Make.defs`` file probably depend on some diff --git a/Documentation/reference/user/02_task_scheduling.rst b/Documentation/reference/user/02_task_scheduling.rst index 6ccb7c4fbd..c24b2dcce4 100644 --- a/Documentation/reference/user/02_task_scheduling.rst +++ b/Documentation/reference/user/02_task_scheduling.rst @@ -6,7 +6,7 @@ priority have exclusive access to the CPU until they become blocked. At that time, the CPU is available to tasks of lower priority. Tasks of equal priority are scheduled FIFO. -Optionally, a Nuttx task or thread can be configured with round-robin or +Optionally, a NuttX task or thread can be configured with round-robin or *sporadic* scheduler. The round-robin is similar to priority scheduling *except* that tasks with equal priority and share CPU time via *time-slicing*. The time-slice interval is a constant determined by the diff --git a/Documentation/reference/user/09_env_vars.rst b/Documentation/reference/user/09_env_vars.rst index 9d7b65d548..5b824697b1 100644 --- a/Documentation/reference/user/09_env_vars.rst +++ b/Documentation/reference/user/09_env_vars.rst @@ -25,7 +25,7 @@ Programming Interfaces ====================== The following environment variable -programming interfaces are provided by Nuttx and are described in detail +programming interfaces are provided by NuttX and are described in detail in the following paragraphs. - :c:func:`getenv` diff --git a/Documentation/reference/user/10_filesystem.rst b/Documentation/reference/user/10_filesystem.rst index 40ccbb91c5..4d2762ef35 100644 --- a/Documentation/reference/user/10_filesystem.rst +++ b/Documentation/reference/user/10_filesystem.rst @@ -20,7 +20,7 @@ system). Any user supplied data or logic can be accessed via the pseudo-file system. Built in support is provided for character and block -`driver `__ *nodes* in the any +`driver `__ *nodes* in the any pseudo file system directory. (By convention, however, all driver nodes should be in the ``/dev`` pseudo file system directory). diff --git a/Documentation/reference/user/index.rst b/Documentation/reference/user/index.rst index b6f37744ee..4eb87e103c 100644 --- a/Documentation/reference/user/index.rst +++ b/Documentation/reference/user/index.rst @@ -13,11 +13,11 @@ limited to addressing only NuttX RTOS APIs that are available to the application developer. As such, this document does not focus on any technical details of the organization or implementation of NuttX. Those technical details are provided in the `NuttX Porting -Guide `__. +Guide `__. Information about configuring and building NuttX is also needed by the application developer. That information can also be found in the `NuttX -Porting Guide `__. +Porting Guide `__. .. toctree:: :maxdepth: 1 diff --git a/Kconfig b/Kconfig index c69636205e..6a83c31845 100644 --- a/Kconfig +++ b/Kconfig @@ -3,7 +3,7 @@ # see the file kconfig-language.txt in the NuttX tools repository. # -mainmenu "Nuttx/$ARCH Configuration" +mainmenu "NuttX/$ARCH Configuration" config APPSDIR string diff --git a/README.md b/README.md index c02b0562d9..d8316e8a44 100644 --- a/README.md +++ b/README.md @@ -56,7 +56,7 @@ available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()). Extensive documentation can be found on the project wiki: - + ## Incubation Status @@ -1756,7 +1756,7 @@ based toolchain in a Cygwin environment. The three biggest are: but you might easily find some new path problems. If so, check out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic links - are used in Nuttx (e.g., include/arch). The make system works around these + are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find that your changes had no effect. diff --git a/ReleaseNotes b/ReleaseNotes index 3b4c6abced..f308863585 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -539,7 +539,7 @@ include: New features were also added: * New OS APIs: chdir() and getcwd() -* The Nuttx shell (NSH) has been extended in many ways. +* The NuttX shell (NSH) has been extended in many ways. - New commands: mkfatfs, mkfifo, sleep, usleep, nice, sh, cd, and pwd - New memory inspection commands and heap usage commands - New capabilities: @@ -929,7 +929,7 @@ NuttX-0.4.6 This is the 38th release of NuttX. The release features support for the Micromint Eagle-100 development board. This board is based around, the Luminary LM3S6918 MCU. This is the first ARM Cortex-M3 -architecture supported by Nuttx. This initial, basic port includes +architecture supported by NuttX. This initial, basic port includes timer and serial console with configurations to execute the NuttX OS test and to run the NuttShell (NSH). Work is still underway on this port and current plans are to have I2C, SSI, MMC/SD, and @@ -1112,7 +1112,7 @@ NuttX-4.14 This is the 46th release of NuttX. The release extends the support for the STMicro STM32 microcontroller. Minimal support for the STM3210E-EVAL development board based around the STM32F103ZET6 MCU -was released in NuttX-0.4.12 and extended in Nuttx-0.4.13 to include +was released in NuttX-0.4.12 and extended in NuttX-0.4.13 to include initial USB support. This completes the STM32F103ZET6 and adds: New Generic RTOS Features: @@ -1233,7 +1233,7 @@ two new MCU architectures in various states of development: The extended port will also include support for SDIO-based SD cards and USB device (and possible LCD support). These extensions - may or may not happen by the Nuttx 5.2 release as my plate is + may or may not happen by the NuttX 5.2 release as my plate is kind of full now. * LPC3131 (http://ics.nxp.com/products/lpc3000/lpc313x.lpc314x.lpc315x/) @@ -1893,7 +1893,7 @@ functionality. These are provided as separate tarballs: The purpose of this separation is both to better organize and modularize the NuttX source tree, but also to provide better support -for incorporation of end-user applications with Nuttx. +for incorporation of end-user applications with NuttX. The incompatibility results from the changes to the board configuration logic needed to supported the separable application. The major @@ -7532,7 +7532,7 @@ Additional new features and extended functionality: - Add a mostly bogus wchar.h header file. This file is mostly bogus because none of the wide character operations are currently - supported in the Nuttx C library. The file does provide the wchar_t + supported in the NuttX C library. The file does provide the wchar_t types needed by some software, however. - Add isatty() function. From Alan Carvalho de Assis. - Add mktemp(), mkstemp(), tmpnam() and tempnam(). @@ -7944,7 +7944,7 @@ Additional new features and extended functionality: leave the terminal program and drop back to nsh. This might come in handy for people that have e.g. GSM modems, GPS receivers or other devices with text based serial communications attached to - their Nuttx systems. From Harald Welte + their NuttX systems. From Harald Welte - apps/interpreters/micropython: A port of Micro Python to NuttX. Contributed by Dave Marples @@ -9951,7 +9951,7 @@ Additional new features and extended functionality: accomplishes this by creating a temporary character driver to mediate the character oriented accesses to the block driver. - HOSTFS: Added a HOSTFS file system for use with the simulator. The - HOSTFS file system mounts in the simulated Nuttx context by provides + HOSTFS file system mounts in the simulated NuttX context by provides proxied access to the file system on the host PC. This is useful for providing file system content and nonvolatile storage of files in the simulation environment. From Ken Pettit. @@ -10105,7 +10105,7 @@ Additional new features and extended functionality: * Applications: apps/system: - apps/system/hexed: Port the hexed command line hexadeciamal editor - to Nuttx. See http://apps.venomdev.net/hexed/. + to NuttX. See http://apps.venomdev.net/hexed/. * Applications: apps/fsutils: @@ -12433,7 +12433,7 @@ Additional new features and extended functionality: * NXP Freescale Kinetis: - Kinetis: Added missing headers. Kinetis broke out SPI to - kinetis/kinetis_spi.h. Broke out DMA to use the modern Nuttx chip + kinetis/kinetis_spi.h. Broke out DMA to use the modern NuttX chip inclusion - still STUBS. Add Kinetis support for ARMV7-M Common Vector and FPU. Allow CONFIG_ARMV7M_CMNVECTOR, CONFIG_STACK_COLORATION, CONFIG_ARCH_FPU. Fix i2c driver offset @@ -17232,7 +17232,7 @@ detailed bugfix information): - ARP: Fix an error introduced when ICMP and ICMP6 socket support was added in NuttX-7.3. A gratuitous ARP (or solicitation) was being sent after receive of the ECHO replay (advertisement). - - ARP: Fix IGMP multicast address computation on Nuttx network stack. + - ARP: Fix IGMP multicast address computation on NuttX network stack. This change fixes the IGMP address computation to allow multicast UDP messages. The destination address was created with the incorrect bytes of the given IPv4 address. From Louis Mayencourt. @@ -18993,7 +18993,7 @@ Additional new features and extended functionality: - apps/examples/calib_udelay: Add tool for calibrating CONFIG_BOARD_LOOPSPERMSEC From Juha Niskanen. - apps/examples/dhtxx: Example for the DHTxx sensor. From Ouss4. - - apps/examples/dsptest: Add unit test for Nuttx DSP library From + - apps/examples/dsptest: Add unit test for NuttX DSP library From Mateusz Szafoni. - apps/examples/elf: CROMFS and ROMFS configuration currently only usable in FLAT build. Add configuration to use ELF objects on @@ -20391,7 +20391,7 @@ detailed bugfix information): * NXP i.MXRT Drivers: - - i.MXRT Ethernet: The board would not come up if I ran Nuttx from cold. + - i.MXRT Ethernet: The board would not come up if I ran NuttX from cold. I dumped the PHY registers to see what the differences were and the PHY was coming up in NANDTree mode. This is a mode for testing connectivity between the PHY and the MAC. Switching this mode off in @@ -22659,7 +22659,7 @@ detailed bugfix information): * NXP LPC17xx Drivers: - - LPC17xx CAN: The name can_txready clashes with Nuttx CAN core + - LPC17xx CAN: The name can_txready clashes with NuttX CAN core global function. LPC178x has only single LPC17_SYSCON_PCLKSEL with only single divisor. From Pavel Pisa. @@ -26654,7 +26654,7 @@ This is the first release of NuttX as Apache NuttX (Incubating) and represents o - Add support for the Digilent ARTY_A7 board to test the Litex port - Added initial support for Sipeed Maix Bit board with Kendryte K210 processor - New architectural support: ez80f92 - - Flat address x86_64 port of Nuttx + - Flat address x86_64 port of NuttX - Support to run NuttX on ESP32 QEMU - Initial support for Sipeed Maix Bit board with Kendryte K210 processor - Add initial support for Kendryte K210 processor in SMP mode diff --git a/TODO b/TODO index e03e408cfb..b28b6e8f28 100644 --- a/TODO +++ b/TODO @@ -550,7 +550,7 @@ o SMP can that occur? I think it can occur in the following situation: - The log below was reported is Nuttx running on two cores + The log below was reported is NuttX running on two cores Cortex-A7 architecture in SMP mode. You can notice see that when nxsched_add_readytorun() was called, the g_cpu_irqset is 3. diff --git a/arch/arm/include/lpc43xx/chip.h b/arch/arm/include/lpc43xx/chip.h index d8e4b32a36..7b98e50c2f 100644 --- a/arch/arm/include/lpc43xx/chip.h +++ b/arch/arm/include/lpc43xx/chip.h @@ -706,7 +706,7 @@ #define LPC43M0_SYSH_PRIORITY_MAX 0x00 /* Zero is maximum priority */ #define LPC43M0_SYSH_PRIORITY_STEP 0x40 /* Steps between priorities */ -/* Only the Cortex-M4 is supported by Nuttx */ +/* Only the Cortex-M4 is supported by NuttX */ #define NVIC_SYSH_PRIORITY_MIN LPC43M4_SYSH_PRIORITY_MIN #define NVIC_SYSH_PRIORITY_DEFAULT LPC43M4_SYSH_PRIORITY_DEFAULT diff --git a/arch/arm/src/arm/arm_head.S b/arch/arm/src/arm/arm_head.S index 5d6ec778b3..8972cdd195 100644 --- a/arch/arm/src/arm/arm_head.S +++ b/arch/arm/src/arm/arm_head.S @@ -541,7 +541,7 @@ __start: #ifdef CONFIG_IDENTITY_TEXTMAP ldr r4, .LCvpgtable /* r4=virtual page table */ #endif - ldr r3, .LCnuttxpaddr /* r3=Aligned Nuttx start address (physical) */ + ldr r3, .LCnuttxpaddr /* r3=Aligned NuttX start address (physical) */ /* Now setup the page tables for our normal mapped execution region. * We round NUTTX_START_VADDR down to the nearest megabyte boundary. diff --git a/arch/arm/src/armv7-a/arm_pghead.S b/arch/arm/src/armv7-a/arm_pghead.S index fd4411832e..e58504732e 100644 --- a/arch/arm/src/armv7-a/arm_pghead.S +++ b/arch/arm/src/armv7-a/arm_pghead.S @@ -632,7 +632,7 @@ __start: #ifdef CONFIG_BOOT_RUNFROMFLASH /* Get R3 = Value of RAM L1 page table entry */ - ldr r3, .LCprambase /* r3=Aligned Nuttx RAM address (physical) */ + ldr r3, .LCprambase /* r3=Aligned NuttX RAM address (physical) */ ldr r1, .LCramflags /* R1=.bss/.data section MMU flags */ add r3, r3, r1 /* r3=flags + base */ diff --git a/arch/arm/src/dm320/dm320_restart.S b/arch/arm/src/dm320/dm320_restart.S index a8366c721d..4eb19d9a06 100644 --- a/arch/arm/src/dm320/dm320_restart.S +++ b/arch/arm/src/dm320/dm320_restart.S @@ -116,7 +116,7 @@ up_phyrestart: #if 1 ldr pc, .LCbtldrentry /* Restart bootloader */ #else - b __start /* Restart Nuttx */ + b __start /* Restart NuttX */ #endif .type .LCphysrestart, %object diff --git a/arch/arm/src/sama5/sam_trng.c b/arch/arm/src/sama5/sam_trng.c index 901c93f714..cc9e37a7cf 100644 --- a/arch/arm/src/sama5/sam_trng.c +++ b/arch/arm/src/sama5/sam_trng.c @@ -4,7 +4,7 @@ * Copyright (C) 2013, 2016-2017 Gregory Nutt. All rights reserved. * Author: Gregory Nutt * - * Derives, in part, from Max Holtzberg's STM32 RNG Nuttx driver: + * Derives, in part, from Max Holtzberg's STM32 RNG NuttX driver: * * Copyright (C) 2012 Max Holtzberg. All rights reserved. * Author: Max Holtzberg diff --git a/arch/arm/src/samv7/sam_trng.c b/arch/arm/src/samv7/sam_trng.c index 2ebad4f822..5c46eaf8f4 100644 --- a/arch/arm/src/samv7/sam_trng.c +++ b/arch/arm/src/samv7/sam_trng.c @@ -4,8 +4,8 @@ * Copyright (C) 2015-2016 Gregory Nutt. All rights reserved. * Author: Gregory Nutt * - * Derives from the SAMA5D3 TRNG Nuttx driver which, in turn, derives, in - * part, from Max Holtzberg's STM32 RNG Nuttx driver: + * Derives from the SAMA5D3 TRNG NuttX driver which, in turn, derives, in + * part, from Max Holtzberg's STM32 RNG NuttX driver: * * Copyright (C) 2012 Max Holtzberg. All rights reserved. * Author: Max Holtzberg diff --git a/arch/arm/src/stm32/stm32_adc.c b/arch/arm/src/stm32/stm32_adc.c index 4dffd6637b..5669ccf6a4 100644 --- a/arch/arm/src/stm32/stm32_adc.c +++ b/arch/arm/src/stm32/stm32_adc.c @@ -71,7 +71,7 @@ /* The STM32 ADC lower-half driver functionality overview: * - one lower-half driver for all STM32 ADC IP cores, - * - general lower-half logic for the Nuttx upper-half ADC driver, + * - general lower-half logic for the NuttX upper-half ADC driver, * - lower-half ADC driver can be used not only with the upper-half ADC * driver, but also in the lower-half logic for special-case custom * drivers (eg. power-control, custom sensors), @@ -103,7 +103,7 @@ * - TIM triggering with/without DMA tranfer * - external triggering with/without DMA transfer * - * (tested with ADC example app from Nuttx apps repo). + * (tested with ADC example app from NuttX apps repo). */ /* At the moment there is no proper implementation for timers external diff --git a/arch/risc-v/src/gap8/gap8_head.S b/arch/risc-v/src/gap8/gap8_head.S index 0d2e73236b..cd5d9228ef 100644 --- a/arch/risc-v/src/gap8/gap8_head.S +++ b/arch/risc-v/src/gap8/gap8_head.S @@ -229,7 +229,7 @@ zero_loop_end: jal x1, gapuino_sysinit - /* Directly call Nuttx nx_start() */ + /* Directly call NuttX nx_start() */ jal x1, nx_start diff --git a/arch/risc-v/src/gap8/gap8_interrupt.c b/arch/risc-v/src/gap8/gap8_interrupt.c index e1e31cf27a..a4e8eaccbf 100644 --- a/arch/risc-v/src/gap8/gap8_interrupt.c +++ b/arch/risc-v/src/gap8/gap8_interrupt.c @@ -62,7 +62,7 @@ volatile uint32_t *g_current_regs; * Public Functions ****************************************************************************/ -/* Function exported to the Nuttx kernel */ +/* Function exported to the NuttX kernel */ void up_mdelay(unsigned int time) { diff --git a/arch/risc-v/src/gap8/gap8_uart.c b/arch/risc-v/src/gap8/gap8_uart.c index da6fa06fca..3926956e4a 100644 --- a/arch/risc-v/src/gap8/gap8_uart.c +++ b/arch/risc-v/src/gap8/gap8_uart.c @@ -37,7 +37,7 @@ /**************************************************************************** * This UART IP has no flow control. So ioctl is limited. * Note that here we don't use the uDMA to send multiple bytes, because - * Nuttx serial drivers don't have abstraction for puts(). + * NuttX serial drivers don't have abstraction for puts(). ****************************************************************************/ /**************************************************************************** @@ -211,7 +211,7 @@ static uart_dev_t g_uart0port = * * Description: * These are the UART interrupt handler. It is called on uDMA ISR. It - * should call uart_transmitchars or uart_receivechar to invoke the Nuttx + * should call uart_transmitchars or uart_receivechar to invoke the NuttX * kernel. * ****************************************************************************/ diff --git a/arch/sim/src/sim/up_head.c b/arch/sim/src/sim/up_head.c index 51e7e9848f..413ec83cca 100644 --- a/arch/sim/src/sim/up_head.c +++ b/arch/sim/src/sim/up_head.c @@ -91,7 +91,7 @@ int main(int argc, char **argv, char **envp) sim_cpu0_start(); #endif - /* Start the Nuttx emulation. This should not return. */ + /* Start the NuttX emulation. This should not return. */ nx_start(); } diff --git a/arch/xtensa/src/esp32/esp32_wifi_adapter.c b/arch/xtensa/src/esp32/esp32_wifi_adapter.c index f4c98593c2..c8fe5d55f1 100644 --- a/arch/xtensa/src/esp32/esp32_wifi_adapter.c +++ b/arch/xtensa/src/esp32/esp32_wifi_adapter.c @@ -431,7 +431,7 @@ ESP_EVENT_DEFINE_BASE(WIFI_EVENT); * Transform from nuttx error code to WiFi adapter error code * * Input Parameters: - * ret - Nuttx error code + * ret - NuttX error code * * Returned Value: * WiFi adapter error code @@ -741,7 +741,7 @@ static void IRAM_ATTR esp_wifi_int_restore(void *wifi_int_mux, uint32_t tmp) * Name: esp_task_yield_from_isr * * Description: - * Do nothing in Nuttx + * Do nothing in NuttX * * Input Parameters: * None diff --git a/boards/Kconfig b/boards/Kconfig index ef0913fc4b..2c39f78184 100644 --- a/boards/Kconfig +++ b/boards/Kconfig @@ -312,7 +312,7 @@ config ARCH_BOARD_GAPUINO depends on ARCH_CHIP_GAP8 select UART_SERIALDRIVER ---help--- - Nuttx port for gapuino, a GAP8 evaluation board. + NuttX port for gapuino, a GAP8 evaluation board. config ARCH_BOARD_HIFIVE1_REVB bool "HiFive1 Rev B board" @@ -2053,7 +2053,7 @@ config ARCH_BOARD_ZKITARM select ARCH_HAVE_LEDS ---help--- Zilogic System's ARM development Kit, ZKIT-ARM-1769. This board is based - on the NXP LPC1769. The Nuttx Buildroot toolchain is used by default. + on the NXP LPC1769. The NuttX Buildroot toolchain is used by default. config ARCH_BOARD_SPRESENSE bool "Sony Spresense Board" diff --git a/boards/README.txt b/boards/README.txt index e5255ad4aa..90d5c25b4d 100644 --- a/boards/README.txt +++ b/boards/README.txt @@ -115,7 +115,7 @@ Make.defs -- This makefile fragment provides architecture and is the path to the root directory of the build. This makefile fragment should include: - $(TOPDIR)/.config : Nuttx configuration + $(TOPDIR)/.config : NuttX configuration $(TOPDIR)/tools/Config.mk : Common definitions Definitions in the Make.defs file probably depend on some of the @@ -433,16 +433,16 @@ boards/hc/mcs92s12ne6/ne64badge not yet been fully tested. boards/arm/nrf52/nrf52-feather - Nuttx port to the Adafruit nRF52832 Feather board + NuttX port to the Adafruit nRF52832 Feather board boards/arm/nrf52/nrf52832-dk - Nuttx port to the Nordic nRF52832 Development Kit (PCA10040) + NuttX port to the Nordic nRF52832 Development Kit (PCA10040) boards/arm/nrf52/nrf52840-dk - Nuttx port to the Nordic nRF52840 Development Kit (PCA10056) + NuttX port to the Nordic nRF52840 Development Kit (PCA10056) boards/arm/nrf52/nrf52840-dongle - Nuttx port to the Nordic nRF52840 Dongle (PCA10059) + NuttX port to the Nordic nRF52840 Dongle (PCA10059) boards/arm/dm320/ntosd-dm320 This port uses the Neuros OSD v1.0 Dev Board with a GNU arm-nuttx-elf @@ -901,7 +901,7 @@ boards/arm/lpc214x/zp214xpa boards/arm/lpc17xx_40xx/zkit-arm-1769 Zilogic System's ARM development Kit, ZKIT-ARM-1769. This board is based - on the NXP LPC1769. The Nuttx Buildroot toolchain is used by default. + on the NXP LPC1769. The NuttX Buildroot toolchain is used by default. Configuring NuttX ^^^^^^^^^^^^^^^^^ diff --git a/boards/arm/am335x/beaglebone-black/README.txt b/boards/arm/am335x/beaglebone-black/README.txt index cee688421d..07145fe3a4 100644 --- a/boards/arm/am335x/beaglebone-black/README.txt +++ b/boards/arm/am335x/beaglebone-black/README.txt @@ -151,7 +151,7 @@ Booting NuttX from an SD card Hit any key to stop autoboot: 0 U-Boot# - 7. Load Nuttx into memory from the U-Boot prompt and run + 7. Load NuttX into memory from the U-Boot prompt and run U-Boot# load mmc 0 0x8a000000 nuttx.bin U-Boot# go 0x8a000000 diff --git a/boards/arm/c5471/c5471evm/README.txt b/boards/arm/c5471/c5471evm/README.txt index 6e4dd5f3fc..ab1a0f1f0f 100644 --- a/boards/arm/c5471/c5471evm/README.txt +++ b/boards/arm/c5471/c5471evm/README.txt @@ -11,7 +11,7 @@ Toolchain If you have no ARM toolchain, one can be downloaded from the NuttX Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). - 1. You must have already configured Nuttx in nuttx. + 1. You must have already configured NuttX in nuttx. tools/configure.sh c5471evm: diff --git a/boards/arm/dm320/ntosd-dm320/README.txt b/boards/arm/dm320/ntosd-dm320/README.txt index bbb65817cf..1ac832def9 100644 --- a/boards/arm/dm320/ntosd-dm320/README.txt +++ b/boards/arm/dm320/ntosd-dm320/README.txt @@ -114,7 +114,7 @@ NuttX buildroot Toolchain If you have no ARM toolchain, one can be downloaded from the NuttX Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). - 1. You must have already configured Nuttx in nuttx. + 1. You must have already configured NuttX in nuttx. tools/configure.sh ntosd-dm320: diff --git a/boards/arm/dm320/ntosd-dm320/doc/README.txt b/boards/arm/dm320/ntosd-dm320/doc/README.txt index 3e682ad8df..4761cb9d24 100644 --- a/boards/arm/dm320/ntosd-dm320/doc/README.txt +++ b/boards/arm/dm320/ntosd-dm320/doc/README.txt @@ -47,7 +47,7 @@ General instructions. make oldconfig make -6. Build Nuttx: +6. Build NuttX: cd nuttx make diff --git a/boards/arm/imxrt/imxrt1060-evk/README.txt b/boards/arm/imxrt/imxrt1060-evk/README.txt index 06ecda5820..2cf8494660 100644 --- a/boards/arm/imxrt/imxrt1060-evk/README.txt +++ b/boards/arm/imxrt/imxrt1060-evk/README.txt @@ -345,7 +345,7 @@ Configuration sub-directories examples/lvgldemo. This configuration needs the optional LCD model RK043FN02H-CT from NXP. The LCD panel comes with the integrated capacitive touchscreen sensor FT5336GQQ connected to the LPI2C1 bus, - address 0x38. Nuttx support such touchscreen device via the driver + address 0x38. NuttX support such touchscreen device via the driver ft5x06 (drivers/input/ft5x06.c). At the moment only the polling method is available, the board features an interrupt line connected to the touchscreen sensor IC. diff --git a/boards/arm/kinetis/freedom-k28f/include/board.h b/boards/arm/kinetis/freedom-k28f/include/board.h index f70c14bea0..61777d92d8 100644 --- a/boards/arm/kinetis/freedom-k28f/include/board.h +++ b/boards/arm/kinetis/freedom-k28f/include/board.h @@ -57,7 +57,7 @@ /* The Freedom K28F uses a 12MHz external Oscillator. * The Kinetis MCU startup from an internal digitally-controlled oscillator - * (DCO). Nuttx will enable the main external oscillator (EXTAL0/XTAL0). + * (DCO). NuttX will enable the main external oscillator (EXTAL0/XTAL0). * The external oscillator/resonator can range from 32.768 KHz up to 50 MHz. * The default external source for the MCG oscillator inputs is 12 MHz * oscillator diff --git a/boards/arm/kinetis/freedom-k64f/include/board.h b/boards/arm/kinetis/freedom-k64f/include/board.h index 5da263aa8d..745556381d 100644 --- a/boards/arm/kinetis/freedom-k64f/include/board.h +++ b/boards/arm/kinetis/freedom-k64f/include/board.h @@ -54,7 +54,7 @@ /* The Freedom K64F uses a 50MHz external clock from the Micrel Ethernet PHY. * The Kinetis MCU startup from an internal digitally-controlled oscillator - * (DCO). Nuttx will enable the main external oscillator (EXTAL0/XTAL0). + * (DCO). NuttX will enable the main external oscillator (EXTAL0/XTAL0). * The external oscillator/resonator can range from 32.768 KHz up to 50 MHz. * The default external source for the MCG oscillator inputs (EXTAL) is * 50 MHz clock source from Micrel Ethernet PHY. diff --git a/boards/arm/kinetis/freedom-k66f/include/board.h b/boards/arm/kinetis/freedom-k66f/include/board.h index 6587738320..297343a334 100644 --- a/boards/arm/kinetis/freedom-k66f/include/board.h +++ b/boards/arm/kinetis/freedom-k66f/include/board.h @@ -56,7 +56,7 @@ /* The Freedom K66F uses a 12Mhz external Oscillator. * The Kinetis MCU startup from an internal digitally-controlled oscillator - * (DCO). Nuttx will enable the main external oscillator (EXTAL0/XTAL0). + * (DCO). NuttX will enable the main external oscillator (EXTAL0/XTAL0). * The external oscillator/resonator can range from 32.768 KHz up to 50 MHz. * The default external source for the MCG oscillator inputs is 12 MHz * oscillator diff --git a/boards/arm/kl/freedom-kl25z/README.txt b/boards/arm/kl/freedom-kl25z/README.txt index 4a80d94138..cc89aace93 100644 --- a/boards/arm/kl/freedom-kl25z/README.txt +++ b/boards/arm/kl/freedom-kl25z/README.txt @@ -42,7 +42,7 @@ NuttX Buildroot Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh freedom-kl25z: diff --git a/boards/arm/kl/freedom-kl26z/README.txt b/boards/arm/kl/freedom-kl26z/README.txt index b30bcc64b4..92ebb292c0 100644 --- a/boards/arm/kl/freedom-kl26z/README.txt +++ b/boards/arm/kl/freedom-kl26z/README.txt @@ -42,7 +42,7 @@ NuttX Buildroot Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh freedom-kl26z: diff --git a/boards/arm/lpc17xx_40xx/olimex-lpc1766stk/configs/usbserial/defconfig b/boards/arm/lpc17xx_40xx/olimex-lpc1766stk/configs/usbserial/defconfig index 07fcb338ac..e216b04e7f 100644 --- a/boards/arm/lpc17xx_40xx/olimex-lpc1766stk/configs/usbserial/defconfig +++ b/boards/arm/lpc17xx_40xx/olimex-lpc1766stk/configs/usbserial/defconfig @@ -30,7 +30,6 @@ CONFIG_PL2303_EPBULKIN=5 CONFIG_PL2303_PRODUCTSTR="USBdev Serial" CONFIG_PL2303_RXBUFSIZE=512 CONFIG_PL2303_TXBUFSIZE=512 -CONFIG_PL2303_VENDORSTR="Nuttx" CONFIG_PREALLOC_TIMERS=4 CONFIG_RAM_SIZE=32768 CONFIG_RAM_START=0x10000000 diff --git a/boards/arm/lpc214x/mcu123-lpc214x/README.txt b/boards/arm/lpc214x/mcu123-lpc214x/README.txt index 82ad659317..84b89a08ae 100644 --- a/boards/arm/lpc214x/mcu123-lpc214x/README.txt +++ b/boards/arm/lpc214x/mcu123-lpc214x/README.txt @@ -57,7 +57,7 @@ NuttX buildroot Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh eagle100: diff --git a/boards/arm/lpc214x/mcu123-lpc214x/configs/usbserial/defconfig b/boards/arm/lpc214x/mcu123-lpc214x/configs/usbserial/defconfig index 92b7df423f..4ff1dd2a79 100644 --- a/boards/arm/lpc214x/mcu123-lpc214x/configs/usbserial/defconfig +++ b/boards/arm/lpc214x/mcu123-lpc214x/configs/usbserial/defconfig @@ -26,7 +26,6 @@ CONFIG_PL2303_EPBULKIN=5 CONFIG_PL2303_PRODUCTSTR="USBdev Serial" CONFIG_PL2303_RXBUFSIZE=512 CONFIG_PL2303_TXBUFSIZE=512 -CONFIG_PL2303_VENDORSTR="Nuttx" CONFIG_PREALLOC_TIMERS=4 CONFIG_RAM_SIZE=32768 CONFIG_RAM_START=0x40000000 diff --git a/boards/arm/lpc2378/olimex-lpc2378/README.txt b/boards/arm/lpc2378/olimex-lpc2378/README.txt index 9b28f1b3fb..eafdac7cd0 100644 --- a/boards/arm/lpc2378/olimex-lpc2378/README.txt +++ b/boards/arm/lpc2378/olimex-lpc2378/README.txt @@ -6,6 +6,6 @@ UEXT pin 3/4 -TXD2/RXD2- is UART2. The board I have has the revision '-' of LPC2378 even though I got the board more than 2 years after the chip revision was released :-( . -I can't get Nuttx to work if I fully enabled the MAM. +I can't get NuttX to work if I fully enabled the MAM. I used FTDI ft232 usb-serial with nsh piping as seen on the screenshot. diff --git a/boards/arm/lpc31xx/ea3131/README.txt b/boards/arm/lpc31xx/ea3131/README.txt index 7764c9d59f..52d91bfbfb 100644 --- a/boards/arm/lpc31xx/ea3131/README.txt +++ b/boards/arm/lpc31xx/ea3131/README.txt @@ -95,7 +95,7 @@ NuttX buildroot Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh ea3131: diff --git a/boards/arm/lpc31xx/ea3131/configs/usbserial/defconfig b/boards/arm/lpc31xx/ea3131/configs/usbserial/defconfig index 5a3e41c636..face713141 100644 --- a/boards/arm/lpc31xx/ea3131/configs/usbserial/defconfig +++ b/boards/arm/lpc31xx/ea3131/configs/usbserial/defconfig @@ -31,7 +31,6 @@ CONFIG_PL2303_EPINTIN=3 CONFIG_PL2303_PRODUCTSTR="USBdev Serial" CONFIG_PL2303_RXBUFSIZE=512 CONFIG_PL2303_TXBUFSIZE=512 -CONFIG_PL2303_VENDORSTR="Nuttx" CONFIG_PREALLOC_TIMERS=4 CONFIG_RAM_SIZE=196608 CONFIG_RAM_START=0x11028000 diff --git a/boards/arm/lpc31xx/ea3152/README.txt b/boards/arm/lpc31xx/ea3152/README.txt index 4c2f46c724..92309c25b3 100644 --- a/boards/arm/lpc31xx/ea3152/README.txt +++ b/boards/arm/lpc31xx/ea3152/README.txt @@ -94,7 +94,7 @@ NuttX buildroot Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh ea3152: diff --git a/boards/arm/lpc31xx/olimex-lpc-h3131/README.txt b/boards/arm/lpc31xx/olimex-lpc-h3131/README.txt index 4a3bca75dd..84cf551980 100644 --- a/boards/arm/lpc31xx/olimex-lpc-h3131/README.txt +++ b/boards/arm/lpc31xx/olimex-lpc-h3131/README.txt @@ -99,7 +99,7 @@ NuttX buildroot Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh olimex-lpc-h3131: diff --git a/boards/arm/nuc1xx/nutiny-nuc120/README.txt b/boards/arm/nuc1xx/nutiny-nuc120/README.txt index 14ca3e61d1..34414f4d48 100644 --- a/boards/arm/nuc1xx/nutiny-nuc120/README.txt +++ b/boards/arm/nuc1xx/nutiny-nuc120/README.txt @@ -43,7 +43,7 @@ NuttX Buildroot Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh nutiny-nuc120: diff --git a/boards/arm/s32k1xx/s32k146evb/README.txt b/boards/arm/s32k1xx/s32k146evb/README.txt index bbdfc28a1a..8a769ad14c 100644 --- a/boards/arm/s32k1xx/s32k146evb/README.txt +++ b/boards/arm/s32k1xx/s32k146evb/README.txt @@ -114,7 +114,7 @@ Thread-Aware Debugging with Eclipse Based on correspondence with Han Raaijmakers - OpenOCD-nuttx build on Linux (NXW00504) making use of S32DS for ARM 2018R1. Nuttx is built with debug symbols. + OpenOCD-nuttx build on Linux (NXW00504) making use of S32DS for ARM 2018R1. NuttX is built with debug symbols. Resulting debug window gives nuttx threads. The full stack details can be viewed. diff --git a/boards/arm/sama5/sama5d3-xplained/README.txt b/boards/arm/sama5/sama5d3-xplained/README.txt index e31a3b42fe..c4054d8a38 100644 --- a/boards/arm/sama5/sama5d3-xplained/README.txt +++ b/boards/arm/sama5/sama5d3-xplained/README.txt @@ -124,7 +124,7 @@ GNU Toolchain Options out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic - links are used in Nuttx (e.g., include/arch). The make system works + links are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find @@ -179,7 +179,7 @@ NuttX EABI "buildroot" Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh sama5d3-xplained: @@ -229,7 +229,7 @@ NXFLAT Toolchain This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh sama5d3-xplained: diff --git a/boards/arm/sama5/sama5d3x-ek/README.txt b/boards/arm/sama5/sama5d3x-ek/README.txt index 4622d9c8a5..70513778b3 100644 --- a/boards/arm/sama5/sama5d3x-ek/README.txt +++ b/boards/arm/sama5/sama5d3x-ek/README.txt @@ -177,7 +177,7 @@ NuttX EABI "buildroot" Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh sama5d3x-ek: @@ -227,7 +227,7 @@ NXFLAT Toolchain This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh sama5d3x-ek: diff --git a/boards/arm/sama5/sama5d3x-ek/configs/demo/defconfig b/boards/arm/sama5/sama5d3x-ek/configs/demo/defconfig index 924c95a75a..8f3134fd5a 100644 --- a/boards/arm/sama5/sama5d3x-ek/configs/demo/defconfig +++ b/boards/arm/sama5/sama5d3x-ek/configs/demo/defconfig @@ -94,5 +94,4 @@ CONFIG_USBHOST_MSC=y CONFIG_USBMSC=y CONFIG_USBMSC_EPBULKIN=2 CONFIG_USBMSC_EPBULKOUT=1 -CONFIG_USBMSC_VENDORSTR="Nuttx" CONFIG_USER_ENTRYPOINT="nsh_main" diff --git a/boards/arm/sama5/sama5d4-ek/README.txt b/boards/arm/sama5/sama5d4-ek/README.txt index 3f143a78f3..dbc15f80f1 100644 --- a/boards/arm/sama5/sama5d4-ek/README.txt +++ b/boards/arm/sama5/sama5d4-ek/README.txt @@ -171,7 +171,7 @@ NuttX EABI "buildroot" Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh sama5d4-ek: @@ -221,7 +221,7 @@ NXFLAT Toolchain This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh sama5d4-ek: diff --git a/boards/arm/samd2l2/samd20-xplained/README.txt b/boards/arm/samd2l2/samd20-xplained/README.txt index f694787cdf..64fc710d69 100644 --- a/boards/arm/samd2l2/samd20-xplained/README.txt +++ b/boards/arm/samd2l2/samd20-xplained/README.txt @@ -305,7 +305,7 @@ GNU Toolchain Options out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic - links are used in Nuttx (e.g., include/arch). The make system works + links are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find @@ -360,7 +360,7 @@ NuttX EABI "buildroot" Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh samd20-xplained: diff --git a/boards/arm/samd2l2/saml21-xplained/README.txt b/boards/arm/samd2l2/saml21-xplained/README.txt index f14f577abe..27f4ef9830 100644 --- a/boards/arm/samd2l2/saml21-xplained/README.txt +++ b/boards/arm/samd2l2/saml21-xplained/README.txt @@ -286,7 +286,7 @@ GNU Toolchain Options out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic - links are used in Nuttx (e.g., include/arch). The make system works + links are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find @@ -341,7 +341,7 @@ NuttX EABI "buildroot" Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh saml21-xplained: diff --git a/boards/arm/samv7/samv71-xult/README.txt b/boards/arm/samv7/samv71-xult/README.txt index 3b2fe89d44..a950cd5639 100644 --- a/boards/arm/samv7/samv71-xult/README.txt +++ b/boards/arm/samv7/samv71-xult/README.txt @@ -1052,7 +1052,7 @@ Testing has also been performed using the maXTouch Xplained Pro LCD * My understanding is that this configuration can be set on Linux * * using the mxp-app program which is available on GitHub. There is an * * (awkward) way to do this with NuttX too. In order to set the * - * maXTouch configuration with Nuttx you need to do these things: * + * maXTouch configuration with NuttX you need to do these things: * * * * - Copy the function atmxt_config() from the file * * boards/arm/samv7/samv71-xult/src/atmxt_config.c into the file * diff --git a/boards/arm/stm32/fire-stm32v2/README.txt b/boards/arm/stm32/fire-stm32v2/README.txt index 9dbdff8be5..5330f24de5 100644 --- a/boards/arm/stm32/fire-stm32v2/README.txt +++ b/boards/arm/stm32/fire-stm32v2/README.txt @@ -237,7 +237,7 @@ for more information. Using the script: cd boards/arm/stm32/fire-stm32v2/tools/oocd.sh $PWD -2) Load Nuttx +2) Load NuttX cd arm-none-eabi-gdb nuttx diff --git a/boards/arm/stm32/hymini-stm32v/README.txt b/boards/arm/stm32/hymini-stm32v/README.txt index 792f8e5839..57eb3e5d46 100644 --- a/boards/arm/stm32/hymini-stm32v/README.txt +++ b/boards/arm/stm32/hymini-stm32v/README.txt @@ -58,7 +58,7 @@ They are encoded as follows: LED_PANIC The system has crashed BLINK BLINK LED_IDLE STM32 is is sleep mode (Optional, not used) - * If Nuttx starts correctly, normal state is to have LED1 on and LED2 off. + * If NuttX starts correctly, normal state is to have LED1 on and LED2 off. ** LED1 is turned off during interrupt. *** LED2 is turned on during signal handler. diff --git a/boards/arm/stm32/hymini-stm32v/configs/usbserial/defconfig b/boards/arm/stm32/hymini-stm32v/configs/usbserial/defconfig index 18c9985826..f3ddf8d742 100644 --- a/boards/arm/stm32/hymini-stm32v/configs/usbserial/defconfig +++ b/boards/arm/stm32/hymini-stm32v/configs/usbserial/defconfig @@ -22,7 +22,6 @@ CONFIG_PL2303=y CONFIG_PL2303_PRODUCTSTR="USBdev Serial" CONFIG_PL2303_RXBUFSIZE=512 CONFIG_PL2303_TXBUFSIZE=512 -CONFIG_PL2303_VENDORSTR="Nuttx" CONFIG_PREALLOC_TIMERS=4 CONFIG_RAM_SIZE=49152 CONFIG_RAM_START=0x20000000 diff --git a/boards/arm/stm32/nucleo-f446re/README.txt b/boards/arm/stm32/nucleo-f446re/README.txt index d945428f41..3a0a7aaca3 100644 --- a/boards/arm/stm32/nucleo-f446re/README.txt +++ b/boards/arm/stm32/nucleo-f446re/README.txt @@ -162,7 +162,7 @@ NuttX EABI "buildroot" Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. $ tools/configure.sh nucleo-f446re:nsh $ make qconfig @@ -205,7 +205,7 @@ NXFLAT Toolchain This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh lpcxpresso-lpc1768: diff --git a/boards/arm/stm32/nucleo-f4x1re/README.txt b/boards/arm/stm32/nucleo-f4x1re/README.txt index 47fa7b26bd..30e514e547 100644 --- a/boards/arm/stm32/nucleo-f4x1re/README.txt +++ b/boards/arm/stm32/nucleo-f4x1re/README.txt @@ -185,7 +185,7 @@ NuttX EABI "buildroot" Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. $ tools/configure.sh nucleo-f4x1re:f401-nsh $ make qconfig @@ -230,7 +230,7 @@ NXFLAT Toolchain This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh lpcxpresso-lpc1768: diff --git a/boards/arm/stm32/stm3210e-eval/README.txt b/boards/arm/stm32/stm3210e-eval/README.txt index 5db561f725..0fece0d5f8 100644 --- a/boards/arm/stm32/stm3210e-eval/README.txt +++ b/boards/arm/stm32/stm3210e-eval/README.txt @@ -100,7 +100,7 @@ for more information. Using the script: cd boards/arm/stm32/stm3210e-eval/tools/oocd.sh $PWD -2) Load Nuttx +2) Load NuttX cd arm-none-eabi-gdb nuttx diff --git a/boards/arm/stm32/stm3210e-eval/configs/usbserial/defconfig b/boards/arm/stm32/stm3210e-eval/configs/usbserial/defconfig index a6df07e7b8..04b751e476 100644 --- a/boards/arm/stm32/stm3210e-eval/configs/usbserial/defconfig +++ b/boards/arm/stm32/stm3210e-eval/configs/usbserial/defconfig @@ -25,7 +25,6 @@ CONFIG_PL2303=y CONFIG_PL2303_PRODUCTSTR="USBdev Serial" CONFIG_PL2303_RXBUFSIZE=512 CONFIG_PL2303_TXBUFSIZE=512 -CONFIG_PL2303_VENDORSTR="Nuttx" CONFIG_PREALLOC_TIMERS=4 CONFIG_RAM_SIZE=65536 CONFIG_RAM_START=0x20000000 diff --git a/boards/arm/stm32/stm32f4discovery/README.txt b/boards/arm/stm32/stm32f4discovery/README.txt index 469b9b9851..0f1c63d324 100644 --- a/boards/arm/stm32/stm32f4discovery/README.txt +++ b/boards/arm/stm32/stm32f4discovery/README.txt @@ -1266,7 +1266,7 @@ Configuration Sub-directories 2. Example usage CS43L22 Audio driver - a. Power On or reset the STM32F4 Discovery board. We can see the Nuttx + a. Power On or reset the STM32F4 Discovery board. We can see the NuttX command line prompt: NuttShell (NSH) diff --git a/boards/arm/stm32/viewtool-stm32f107/README.txt b/boards/arm/stm32/viewtool-stm32f107/README.txt index 5e2be065ba..fca2f73e9f 100644 --- a/boards/arm/stm32/viewtool-stm32f107/README.txt +++ b/boards/arm/stm32/viewtool-stm32f107/README.txt @@ -795,7 +795,7 @@ Toolchains out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic - links are used in Nuttx (e.g., include/arch). The make system works + links are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find diff --git a/boards/arm/stm32f7/nucleo-144/README.txt b/boards/arm/stm32f7/nucleo-144/README.txt index 9fdc2fed3e..9447b2eb3e 100644 --- a/boards/arm/stm32f7/nucleo-144/README.txt +++ b/boards/arm/stm32f7/nucleo-144/README.txt @@ -217,7 +217,7 @@ Basic configuration & build steps $ make oldconfig - Select the features you want in the build. $ make menuconfig - - Builds Nuttx with the features you selected. + - Builds NuttX with the features you selected. $ make Hardware diff --git a/boards/arm/stm32l4/nucleo-l432kc/README.txt b/boards/arm/stm32l4/nucleo-l432kc/README.txt index 32452f8d03..05d01d0456 100644 --- a/boards/arm/stm32l4/nucleo-l432kc/README.txt +++ b/boards/arm/stm32l4/nucleo-l432kc/README.txt @@ -149,7 +149,7 @@ NuttX EABI "buildroot" Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. $ tools/configure.sh nucleo-l432kc:nsh $ make qconfig @@ -192,7 +192,7 @@ NXFLAT Toolchain This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh lpcxpresso-lpc1768: diff --git a/boards/arm/stm32l4/nucleo-l476rg/README.txt b/boards/arm/stm32l4/nucleo-l476rg/README.txt index 665bc53bde..92cd2fed48 100644 --- a/boards/arm/stm32l4/nucleo-l476rg/README.txt +++ b/boards/arm/stm32l4/nucleo-l476rg/README.txt @@ -162,7 +162,7 @@ NuttX EABI "buildroot" Toolchain Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. $ tools/configure.sh nucleo-l476rg:nsh $ make qconfig @@ -205,7 +205,7 @@ NXFLAT Toolchain This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh lpcxpresso-lpc1768: @@ -519,7 +519,7 @@ Other External Hardware/Devices nucleo-stm32l476rg Cortex-M4. This option will or can broaden the functionality in your project, solution or application. - In this Nuttx project we attach an MH-SD Card Module (SPI). + In this NuttX project we attach an MH-SD Card Module (SPI). [http://www.geeetech.com/wiki/index.php/Arduino_SD_card_Module] Other solutions should also work. diff --git a/boards/arm/str71x/olimex-strp711/README.txt b/boards/arm/str71x/olimex-strp711/README.txt index 5799c1861b..5d08582285 100644 --- a/boards/arm/str71x/olimex-strp711/README.txt +++ b/boards/arm/str71x/olimex-strp711/README.txt @@ -141,7 +141,7 @@ GNU Toolchain Options but you might easily find some new path problems. If so, check out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic links - are used in Nuttx (e.g., include/arch). The make system works around these + are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find that your changes had no effect. @@ -171,7 +171,7 @@ NuttX buildroot Toolchain If you have no ARM toolchain, one can be downloaded from the NuttX Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). - 1. You must have already configured Nuttx in nuttx. + 1. You must have already configured NuttX in nuttx. tools/configure.sh olimex-strp711: diff --git a/boards/arm/tiva/dk-tm4c129x/README.txt b/boards/arm/tiva/dk-tm4c129x/README.txt index c0306fbe70..5719e25e70 100644 --- a/boards/arm/tiva/dk-tm4c129x/README.txt +++ b/boards/arm/tiva/dk-tm4c129x/README.txt @@ -159,7 +159,7 @@ Buttons and LEDs logic. APIs are provided to support application control of the LED in that case (in include/board.h and src/tm4c_userleds.c). - If CONFIG_ARCH_LEDS is defined then the usage of the LEDs by Nuttx is + If CONFIG_ARCH_LEDS is defined then the usage of the LEDs by NuttX is defined in include/board.h and src/tm4c_autoleds.c. The LEDs are used to encode OS-related events as follows: diff --git a/boards/arm/tiva/tm4c123g-launchpad/README.txt b/boards/arm/tiva/tm4c123g-launchpad/README.txt index 37ee3a55ac..a0e1ab2d40 100644 --- a/boards/arm/tiva/tm4c123g-launchpad/README.txt +++ b/boards/arm/tiva/tm4c123g-launchpad/README.txt @@ -453,7 +453,7 @@ MCP2515 - SPI - CAN I like CANbus, and having an MCP2515 CAN Bus Module laying around gave me the idea to implement it on the TM4C123GXL (Launchpad). - Nuttx already had implemented it on the STM32. So a lot of work already + NuttX already had implemented it on the STM32. So a lot of work already has been done. It uses SPI and with this Launchpad we use SSI. Here is how I have the MCP2515 Module connected. But you can change diff --git a/boards/avr/at90usb/micropendous3/README.txt b/boards/avr/at90usb/micropendous3/README.txt index 614dd82e3b..5cc525a92e 100644 --- a/boards/avr/at90usb/micropendous3/README.txt +++ b/boards/avr/at90usb/micropendous3/README.txt @@ -262,7 +262,7 @@ Windows Native Toolchains out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic - links are used in Nuttx (e.g., include/arch). The make system works + links are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find @@ -285,7 +285,7 @@ NuttX buildroot Toolchain NuttX Bitbucket download site (https://bitbucket.org/nuttx/nuttx/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh micropendous3: diff --git a/boards/avr/at90usb/teensy-2.0/README.txt b/boards/avr/at90usb/teensy-2.0/README.txt index 3bab023491..55b4a0c7f8 100644 --- a/boards/avr/at90usb/teensy-2.0/README.txt +++ b/boards/avr/at90usb/teensy-2.0/README.txt @@ -271,7 +271,7 @@ Windows Native Toolchains out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic - links are used in Nuttx (e.g., include/arch). The make system works + links are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find @@ -294,7 +294,7 @@ NuttX buildroot Toolchain NuttX Bitbucket download site (https://bitbucket.org/nuttx/nuttx/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh Teensy++: diff --git a/boards/avr/atmega/amber/README.txt b/boards/avr/atmega/amber/README.txt index 13402498a6..3677cc68a1 100644 --- a/boards/avr/atmega/amber/README.txt +++ b/boards/avr/atmega/amber/README.txt @@ -249,7 +249,7 @@ Windows Native Toolchains out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic - links are used in Nuttx (e.g., include/arch). The make system works + links are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find @@ -272,7 +272,7 @@ NuttX buildroot Toolchain NuttX Bitbucket download site (https://bitbucket.org/nuttx/nuttx/downloads/). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh amber: diff --git a/boards/hc/m9s12/demo9s12ne64/README.txt b/boards/hc/m9s12/demo9s12ne64/README.txt index e40ab9c277..29b42cbc9b 100644 --- a/boards/hc/m9s12/demo9s12ne64/README.txt +++ b/boards/hc/m9s12/demo9s12ne64/README.txt @@ -119,7 +119,7 @@ NuttX Buildroot Toolchain This GNU toolchain builds and executes in the Linux or Cygwin environments. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh demo9s12nec64: diff --git a/boards/hc/m9s12/ne64badge/README.txt b/boards/hc/m9s12/ne64badge/README.txt index 88a0ba34ce..7fcc795f95 100644 --- a/boards/hc/m9s12/ne64badge/README.txt +++ b/boards/hc/m9s12/ne64badge/README.txt @@ -226,7 +226,7 @@ NuttX Buildroot Toolchain This GNU toolchain builds and executes in the Linux or Cygwin environments. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh ne64badge: diff --git a/boards/mips/pic32mx/mirtoo/README.txt b/boards/mips/pic32mx/mirtoo/README.txt index ef78ccd9e8..dce54b47e1 100644 --- a/boards/mips/pic32mx/mirtoo/README.txt +++ b/boards/mips/pic32mx/mirtoo/README.txt @@ -439,7 +439,7 @@ Toolchains but you might easily find some new path problems. If so, check out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic links - are used in Nuttx (e.g., include/arch). The make system works around these + are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find that your changes had no effect. diff --git a/boards/mips/pic32mx/pic32mx-starterkit/README.txt b/boards/mips/pic32mx/pic32mx-starterkit/README.txt index dca63b524a..4ed3b7464f 100644 --- a/boards/mips/pic32mx/pic32mx-starterkit/README.txt +++ b/boards/mips/pic32mx/pic32mx-starterkit/README.txt @@ -478,7 +478,7 @@ Toolchains but you might easily find some new path problems. If so, check out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic links - are used in Nuttx (e.g., include/arch). The make system works around these + are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find that your changes had no effect. @@ -579,7 +579,7 @@ Serial Console: MEB gotten any serial UART output to work from the MEB.]] A serial console is not required to use NuttX. However, all of the - Nuttx example code in the apps/examples assumes that you have a + NuttX example code in the apps/examples assumes that you have a serial console. The Ethernet Starter Kit(even with the MEB) does not have any RS-232 connector needed to drive the serial console. @@ -1075,13 +1075,13 @@ Where is one of the following: available. b. This example can support an FTP client. In order to build in FTP client - support simply add the following to the Nuttx configuration file: + support simply add the following to the NuttX configuration file: CONFIG_NETUTILS_FTPC=y CONFIG_EXAMPLES_FTPC=y c. This example can support an FTP server. In order to build in FTP server - support simply add the following to the Nuttx configuration file: + support simply add the following to the NuttX configuration file: CONFIG_NETUTILS_FTPD=y CONFIG_EXAMPLES_FTPD=y diff --git a/boards/mips/pic32mx/pic32mx7mmb/README.txt b/boards/mips/pic32mx/pic32mx7mmb/README.txt index 650ec778a2..2648dee5e7 100644 --- a/boards/mips/pic32mx/pic32mx7mmb/README.txt +++ b/boards/mips/pic32mx/pic32mx7mmb/README.txt @@ -250,7 +250,7 @@ Toolchains but you might easily find some new path problems. If so, check out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic links - are used in Nuttx (e.g., include/arch). The make system works around these + are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find that your changes had no effect. diff --git a/boards/mips/pic32mx/sure-pic32mx/README.txt b/boards/mips/pic32mx/sure-pic32mx/README.txt index 93b86b166d..e9718fb3b9 100644 --- a/boards/mips/pic32mx/sure-pic32mx/README.txt +++ b/boards/mips/pic32mx/sure-pic32mx/README.txt @@ -333,7 +333,7 @@ Toolchains but you might easily find some new path problems. If so, check out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic links - are used in Nuttx (e.g., include/arch). The make system works around these + are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find that your changes had no effect. diff --git a/boards/mips/pic32mx/ubw32/README.txt b/boards/mips/pic32mx/ubw32/README.txt index cbcceda52a..c736589597 100644 --- a/boards/mips/pic32mx/ubw32/README.txt +++ b/boards/mips/pic32mx/ubw32/README.txt @@ -272,7 +272,7 @@ Toolchains but you might easily find some new path problems. If so, check out 'cygpath -w' 2. Windows toolchains cannot follow Cygwin symbolic links. Many symbolic links - are used in Nuttx (e.g., include/arch). The make system works around these + are used in NuttX (e.g., include/arch). The make system works around these problems for the Windows tools by copying directories instead of linking them. But this can also cause some confusion for you: For example, you may edit a file in a "linked" directory and find that your changes had no effect. diff --git a/boards/misoc/lm32/misoc/README.txt b/boards/misoc/lm32/misoc/README.txt index 9b9ed13aa0..d1aa014393 100644 --- a/boards/misoc/lm32/misoc/README.txt +++ b/boards/misoc/lm32/misoc/README.txt @@ -18,7 +18,7 @@ Buildroot Toolchain Bitbucket GIT repository (https://bitbucket.org/nuttx/buildroot). This GNU toolchain builds and executes in the Linux or Cygwin environment. - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh misoc: make oldconfig context diff --git a/boards/renesas/sh1/us7032evb1/README.txt b/boards/renesas/sh1/us7032evb1/README.txt index 0634612882..f738a1cdb3 100644 --- a/boards/renesas/sh1/us7032evb1/README.txt +++ b/boards/renesas/sh1/us7032evb1/README.txt @@ -21,7 +21,7 @@ Toolchain If you have no SH toolchain, one can be downloaded from the NuttX Bitbucket download site (https://bitbucket.org/nuttx/buildroot/downloads/). - 1. You must have already configured Nuttx in nuttx. + 1. You must have already configured NuttX in nuttx. tools/configure.sh us7032evb1: diff --git a/boards/x86/qemu/qemu-i486/README.txt b/boards/x86/qemu/qemu-i486/README.txt index 8c203276ce..ef8fbbe6a6 100644 --- a/boards/x86/qemu/qemu-i486/README.txt +++ b/boards/x86/qemu/qemu-i486/README.txt @@ -116,7 +116,7 @@ Cygwin Buildroot Toolchain Buildroot Instructions ---------------------- - 1. You must have already configured Nuttx in /nuttx. + 1. You must have already configured NuttX in /nuttx. tools/configure.sh qemu-i486: diff --git a/boards/x86_64/intel64/qemu-intel64/README.txt b/boards/x86_64/intel64/qemu-intel64/README.txt index 4f5b3b440f..57bf019b3b 100644 --- a/boards/x86_64/intel64/qemu-intel64/README.txt +++ b/boards/x86_64/intel64/qemu-intel64/README.txt @@ -36,7 +36,7 @@ To create a bootable disk with grub2, create a directory named `iso` with grub c ##### grub.cfg -The grub.cfg should contain the boot entry of Nuttx. +The grub.cfg should contain the boot entry of NuttX. ``` set timeout=0 set default=0 @@ -107,7 +107,7 @@ Running Bochs ------------ First edit/check the .bochsrc - You can create one in the top-level Nuttx directory or bochs will use the one in your $HOME. + You can create one in the top-level NuttX directory or bochs will use the one in your $HOME. Remember to change the CPU model to one with mandatory features and enable the COM port. * Find and edit (You might adjust the IPS as you machine perform): diff --git a/drivers/sensors/README.txt b/drivers/sensors/README.txt index 9ab4258d8d..e3e2bf8aed 100644 --- a/drivers/sensors/README.txt +++ b/drivers/sensors/README.txt @@ -57,7 +57,7 @@ several permit the user to load firmware into them and perform as nanocontrollers. Other sensors have very sophisticated built-in digital filters that can be programmed with hundreds of parameters. -Currently most sensor drivers in the Nuttx drivers/sensors +Currently most sensor drivers in the NuttX drivers/sensors directory implement file_ops open(), close(), and read() functions. The open() function initializes the sensor and places it in a mode where it can transfer live data in a default configuration. The close() function @@ -241,34 +241,34 @@ Using the current implementation... 1) A sensor "data ready" or timer interrupt occurs. 2) Context is saved and and the driver's interrupt handler is scheduled to run. - 3) The Nuttx scheduler dispatches the driver's interrupt handler task. + 3) The NuttX scheduler dispatches the driver's interrupt handler task. 4) The driver's interrupt handler task posts to a semaphore that the driver's worker task is waiting on. - 5) Nuttx restores the context for the driver's worker task and starts it + 5) NuttX restores the context for the driver's worker task and starts it running. 6) The driver's worker task starts the i/o to collect the sample.) (This is where the 8 microseconds of real work gets performed.) And waits on a SPI data transfer complete semaphore. - 7) The Nuttx saves the context of the driver's worker task, and the + 7) The NuttX saves the context of the driver's worker task, and the scheduler dispatches some other task to run while we are waiting. Note that this is a good thing. This task is probably performing some other real work. We want this to happen during the data transfer. - 8) The completion of the data transfer causes an interrupt. Nuttx saves the + 8) The completion of the data transfer causes an interrupt. NuttX saves the current context and restores the driver's worker task's context. 9) The driver's worker task goes to sleep waiting on the semaphore for the next sensor "data ready" or timer interrupt. -10) The Nuttx saves the context of the driver's worker task, and the +10) The NuttX saves the context of the driver's worker task, and the scheduler dispatches some other task to run while we are waiting. Independently with the above... a) The sensor application program performs a file_ops read() to collect a sample. -b) The Nuttx high level driver receives control, performs a thin layer of +b) The NuttX high level driver receives control, performs a thin layer of housekeeping and calls the sensor driver's read function. c) The sensor driver's read function copies the most recent sample from the worker task's data area to the application's buffer and returns. -d) The Nuttx high level driver receives control, performs a thin layer of +d) The NuttX high level driver receives control, performs a thin layer of housekeeping and returns. e) The application processes the sample. @@ -305,11 +305,11 @@ Its goal is to change the sequence of events detailed above to... 1) A sensor "data ready" or timer interrupt occurs. 2) Context is saved and and the cluster driver's interrupt handler is scheduled to run. - 3) The Nuttx scheduler dispatches the cluster driver's interrupt handler + 3) The NuttX scheduler dispatches the cluster driver's interrupt handler task. 4) The cluster driver's interrupt handler task posts to a semaphore that the cluster driver's worker task is waiting on. - 5) Nuttx restores the context for the driver's worker task and starts it + 5) NuttX restores the context for the driver's worker task and starts it running. 6) The cluster driver's worker task starts the i/o to collect the sample. There are two choices here. Programed I/O (PIO) or DMA. If PIO is @@ -326,29 +326,29 @@ Its goal is to change the sequence of events detailed above to... more transfers we yield control and move to the next step. Note that the data is being transferred directly into the buffer provided by the application program; so no copy needs to be performed. - 7) The Nuttx saves the context of the cluster driver's worker task, and the + 7) The NuttX saves the context of the cluster driver's worker task, and the scheduler dispatches some other task to run while we are waiting. Again note that this is a good thing. This task is probably performing some other real work. We want this to happen during the data transfer. 8) The completion of the last of the previous data transfers causes an - interrupt. Nuttx saves the current context and restores the cluster + interrupt. NuttX saves the current context and restores the cluster driver's worker task's context. If there is more sensor data to collect, then goto Step 6. Otherwise it posts to a semaphore that will wake the application. 9) The driver's worker task goes to sleep waiting on the semaphore for the next sensor "data ready" or timer interrupt. -10) The Nuttx saves the context of the driver's worker task, and the +10) The NuttX saves the context of the driver's worker task, and the scheduler dispatches some other task to run while we are waiting. Independently with the above... a) The sensor application program performs a file_ops read() to collect a sample. -b) The Nuttx high level driver receives control, performs a thin layer of +b) The NuttX high level driver receives control, performs a thin layer of housekeeping and calls the sensor driver's read function. c) The sensor driver's read function copies the most recent sample from the worker task's data area to the application's buffer and returns. -d) The Nuttx high level driver receives control, performs a thin layer of +d) The NuttX high level driver receives control, performs a thin layer of housekeeping and returns. e) The application processes the sample. @@ -389,7 +389,7 @@ Sensor Cluster Interface description: configuration structure. The leaf driver registration function must store a handle (opaque pointer) to the instance of the leaf driver being registered in this field. Note that this should be the same handle that - the leaf driver supplies to Nuttx to register itself. The cluster driver + the leaf driver supplies to NuttX to register itself. The cluster driver will include this handle as a parameter in calls made to the leaf driver. struct sensor_cluster_operations_s @@ -408,7 +408,7 @@ struct sensor_cluster_operations_s CODE int (*driver_resume)(FAR void *instance_handle, int32_t arg); }; -Note that the sensor_cluster_operations_s strongly resembles the Nuttx fs.h +Note that the sensor_cluster_operations_s strongly resembles the NuttX fs.h file_operations structures. This permits the current file_operations functions to become thin wrappers around these functions. diff --git a/drivers/syslog/README.txt b/drivers/syslog/README.txt index 4342aea2a4..7a98d318f5 100644 --- a/drivers/syslog/README.txt +++ b/drivers/syslog/README.txt @@ -435,7 +435,7 @@ RAM Logging Device output in a circular buffer in RAM. It differs from a pipe in numerous details as needed to support logging. - This driver is built when CONFIG_RAMLOG is defined in the Nuttx + This driver is built when CONFIG_RAMLOG is defined in the NuttX configuration. dmesg diff --git a/fs/binfs/Make.defs b/fs/binfs/Make.defs index 372786b7a9..12d3374069 100644 --- a/fs/binfs/Make.defs +++ b/fs/binfs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/cromfs/Make.defs b/fs/cromfs/Make.defs index fe67ea61e5..0b574a8803 100644 --- a/fs/cromfs/Make.defs +++ b/fs/cromfs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/fat/Make.defs b/fs/fat/Make.defs index 87255763f8..d34d1c9491 100644 --- a/fs/fat/Make.defs +++ b/fs/fat/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/hostfs/Make.defs b/fs/hostfs/Make.defs index fd128b3378..40eba8ac33 100644 --- a/fs/hostfs/Make.defs +++ b/fs/hostfs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/mmap/Make.defs b/fs/mmap/Make.defs index f7d0a3c90c..b1098a30ab 100644 --- a/fs/mmap/Make.defs +++ b/fs/mmap/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/nfs/Make.defs b/fs/nfs/Make.defs index fee59bcb09..cbc0a2ba16 100644 --- a/fs/nfs/Make.defs +++ b/fs/nfs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/nxffs/Make.defs b/fs/nxffs/Make.defs index 45299472ea..0a4fb67c65 100644 --- a/fs/nxffs/Make.defs +++ b/fs/nxffs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/procfs/Make.defs b/fs/procfs/Make.defs index 56607afce0..0944e31bef 100644 --- a/fs/procfs/Make.defs +++ b/fs/procfs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/romfs/Make.defs b/fs/romfs/Make.defs index ba834d7906..83244bfc31 100644 --- a/fs/romfs/Make.defs +++ b/fs/romfs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/smartfs/Make.defs b/fs/smartfs/Make.defs index f05c0f215c..1e0dc3a03d 100644 --- a/fs/smartfs/Make.defs +++ b/fs/smartfs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/spiffs/Make.defs b/fs/spiffs/Make.defs index 87370976d0..1c08a96f71 100644 --- a/fs/spiffs/Make.defs +++ b/fs/spiffs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/tmpfs/Make.defs b/fs/tmpfs/Make.defs index 42d837f8f6..6cf87d6b51 100644 --- a/fs/tmpfs/Make.defs +++ b/fs/tmpfs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/fs/unionfs/Make.defs b/fs/unionfs/Make.defs index 3c0e0ee320..12d2b0ebb7 100644 --- a/fs/unionfs/Make.defs +++ b/fs/unionfs/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. # diff --git a/include/nuttx/fs/ioctl.h b/include/nuttx/fs/ioctl.h index 87a4ea5a93..3ff8c2aa03 100644 --- a/include/nuttx/fs/ioctl.h +++ b/include/nuttx/fs/ioctl.h @@ -314,7 +314,7 @@ #define _SNIOCVALID(c) (_IOC_TYPE(c)==_SNIOCBASE) #define _SNIOC(nr) _IOC(_SNIOCBASE,nr) -/* Nuttx Analog (DAC/ADC) ioctl commands (see nuttx/analog/ioctl.h **********/ +/* NuttX Analog (DAC/ADC) ioctl commands (see nuttx/analog/ioctl.h **********/ #define _ANIOCVALID(c) (_IOC_TYPE(c)==_ANIOCBASE) #define _ANIOC(nr) _IOC(_ANIOCBASE,nr) diff --git a/include/nuttx/sensors/adxl372.h b/include/nuttx/sensors/adxl372.h index 41b76462ba..0ff199f1c2 100644 --- a/include/nuttx/sensors/adxl372.h +++ b/include/nuttx/sensors/adxl372.h @@ -45,7 +45,7 @@ * * To use this driver via the file_operations interface, the board * initialization function should call this driver's registration function. - * The driver will register itself with Nuttx under the /dev path that is + * The driver will register itself with NuttX under the /dev path that is * provided by the config structure. Then user applications may access the * driver via the "file descriptor handle" returned by the file_operations * open() function. diff --git a/include/nuttx/sensors/lsm330.h b/include/nuttx/sensors/lsm330.h index efad364d68..b97c228e00 100644 --- a/include/nuttx/sensors/lsm330.h +++ b/include/nuttx/sensors/lsm330.h @@ -45,7 +45,7 @@ * * To use this driver via the file_operations interface, the board * initialization function should call this driver's registration function. - * The driver will register itself with Nuttx under the /dev path that is + * The driver will register itself with NuttX under the /dev path that is * provided by the config structure. Then user applications may access the * driver via the "file descriptor handle" returned by the file_operations * open() function. diff --git a/include/nuttx/syslog/ramlog.h b/include/nuttx/syslog/ramlog.h index a764eaef57..39a9e8c60f 100644 --- a/include/nuttx/syslog/ramlog.h +++ b/include/nuttx/syslog/ramlog.h @@ -43,7 +43,7 @@ * debugging output in a FIFO in RAM. It differs from a pipe in numerous * details as needed to support logging. * - * This driver is built when CONFIG_RAMLOG is defined in the Nuttx + * This driver is built when CONFIG_RAMLOG is defined in the NuttX * configuration. */ diff --git a/include/nuttx/usb/hid_parser.h b/include/nuttx/usb/hid_parser.h index d9a77e0595..dee924d776 100644 --- a/include/nuttx/usb/hid_parser.h +++ b/include/nuttx/usb/hid_parser.h @@ -49,7 +49,7 @@ * state table allows for more PUSH/POP report items to be nested, but * consumes more memory. By default this is set to 2 levels (allowing non- * nested PUSH items) but this can be overridden by defining - * CONFIG_HID_STATEDEPTH in the Nuttx config file. + * CONFIG_HID_STATEDEPTH in the NuttX config file. * * CONFIG_HID_USAGEDEPTH * Constant indicating the maximum stack depth of the usage table. A larger @@ -57,14 +57,14 @@ * REPORT COUNT entries of more than one, but requires more stack space. By * default this is set to 8 levels (allowing for a report item with a count * of 8) but this can be overridden by defining CONFIG_HID_USAGEDEPTH to - * in the Nuttx config file. + * in the NuttX config file. * * CONFIG_HID_MAXCOLLECTIONS * Constant indicating the maximum number of COLLECTION items (nested or * unnested) that can be processed in the report item descriptor. A large * value allows for more COLLECTION items to be processed, but consumes * more memory. By default this is set to 10 collections, but this can be - * overridden by defining CONFIG_HID_MAXCOLLECTIONS in the Nuttx config file. + * overridden by defining CONFIG_HID_MAXCOLLECTIONS in the NuttX config file. * * CONFIG_HID_MAXITEMS * Constant indicating the maximum number of report items (IN, OUT or @@ -72,7 +72,7 @@ * in the user HID Report Info structure. A large value allows * for more report items to be stored, but consumes more memory. By default * this is set to 20 items, but this can be overridden by defining - * CONFIG_HID_MAXITEMS in the Nuttx config file. + * CONFIG_HID_MAXITEMS in the NuttX config file. * * CONFIG_HID_MAXIDS * Constant indicating the maximum number of unique report IDs that can be @@ -80,7 +80,7 @@ * array in the user HID Report Info structure. A large value allows for * more report ID report sizes to be stored, but consumes more memory. By * default this is set to 10 items, but this can be overridden by defining - * CONFIG_HID_MAXIDS in the Nuttx config file. Note that IN, OUT and FEATURE + * CONFIG_HID_MAXIDS in the NuttX config file. Note that IN, OUT and FEATURE * items sharing the same report ID consume only one size item in the array. */ diff --git a/include/poll.h b/include/poll.h index fc0384fbae..334b4c6434 100644 --- a/include/poll.h +++ b/include/poll.h @@ -111,7 +111,7 @@ typedef unsigned int nfds_t; typedef uint8_t pollevent_t; -/* This is the Nuttx variant of the standard pollfd structure. The poll() +/* This is the NuttX variant of the standard pollfd structure. The poll() * interfaces receive a variable length array of such structures. * * REVISIT: In a multi-threaded environment, one use case might be to share diff --git a/include/sys/stat.h b/include/sys/stat.h index 891c341639..3cb314061c 100644 --- a/include/sys/stat.h +++ b/include/sys/stat.h @@ -34,7 +34,7 @@ * Pre-processor Definitions ****************************************************************************/ -/* mode_t bit settings (most of these do not apply to Nuttx). This assumes +/* mode_t bit settings (most of these do not apply to NuttX). This assumes * that the full size of a mode_t is 16-bits. (However, mode_t must be size * 'int' because it is promoted to size int when passed in varargs). * diff --git a/libs/libc/termios/lib_cfspeed.c b/libs/libc/termios/lib_cfspeed.c index b0e08f800c..df0f196a69 100644 --- a/libs/libc/termios/lib_cfspeed.c +++ b/libs/libc/termios/lib_cfspeed.c @@ -118,7 +118,7 @@ static int baud_mask(speed_t speed) * the input baud rate given to the hardware will be the same as the output * baud rate stored in the termios structure." * - * NOTE 2. In Nuttx, the speed_t is defined to be unsigned int and the baud + * NOTE 2. In NuttX, the speed_t is defined to be unsigned int and the baud * encodings of termios.h are baud value mask. And their corresponding * values are in array g_baud_table. However, if you do so, your code will * *NOT* be portable to other environments where speed_t is smaller and @@ -172,7 +172,7 @@ int cfsetspeed(FAR struct termios *termiosp, speed_t speed) * NOTE 1: NuttX does not control input/output baud independently. Both * must be the same. The POSIX standard interfaces, cfisetispeed() and * cfisetospeed() are defined to be cfgetspeed() in termios.h. - * NOTE 2. In Nuttx, the speed_t is defined to be uint32_t and the baud + * NOTE 2. In NuttX, the speed_t is defined to be uint32_t and the baud * encodings of termios.h are the actual baud values themselves. Therefore, * any baud value may be returned here... not just those enumerated in * termios.h diff --git a/libs/libc/termios/lib_isatty.c b/libs/libc/termios/lib_isatty.c index 93aebdc210..e1e7a7c279 100644 --- a/libs/libc/termios/lib_isatty.c +++ b/libs/libc/termios/lib_isatty.c @@ -54,7 +54,7 @@ * Return a non-zero (true) value if the file descriptor, fd, corresponds * to a TTYY. * - * NOTE: Nuttx, of course, does not have true TTYs in the sense that this + * NOTE: NuttX, of course, does not have true TTYs in the sense that this * function is intended. In this implementation, the function simply * returns true if the file descriptor is associated with a driver that * responds wo tcgetattr() without an error -- that it, the driver supports diff --git a/net/utils/net_ipv6_mask2pref.c b/net/utils/net_ipv6_mask2pref.c index 562fe40f12..ca1f6fdffe 100644 --- a/net/utils/net_ipv6_mask2pref.c +++ b/net/utils/net_ipv6_mask2pref.c @@ -135,7 +135,7 @@ static inline uint8_t net_msbits16(uint16_t hword) * Name: net_ipv6_mask2pref * * Description: - * Convert a 128-bit netmask to a prefix length. The Nuttx IPv6 + * Convert a 128-bit netmask to a prefix length. The NuttX IPv6 * networking uses 128-bit network masks internally. This function * converts the IPv6 netmask to a prefix length. * diff --git a/net/utils/utils.h b/net/utils/utils.h index 04bc387422..d07b5bb8d1 100644 --- a/net/utils/utils.h +++ b/net/utils/utils.h @@ -172,7 +172,7 @@ unsigned int net_timeval2dsec(FAR struct timeval *tv, * Name: net_ipv6_mask2pref * * Description: - * Convert a 128-bit netmask to a prefix length. The Nuttx IPv6 + * Convert a 128-bit netmask to a prefix length. The NuttX IPv6 * networking uses 128-bit network masks internally. This function * converts the IPv6 netmask to a prefix length. * diff --git a/tools/README.txt b/tools/README.txt index f92924af42..b338a8126a 100644 --- a/tools/README.txt +++ b/tools/README.txt @@ -54,7 +54,7 @@ configure.c, cfgparser.c, and cfgparser.h configure.sh is a bash script that is used to configure NuttX for a given target board in a environment that supports POSIX paths (Linux, Cygwin, - macOS, or similar). See boards/README.txt or Documentation/NuttxPortingGuide.html + macOS, or similar). See boards/README.txt or Documentation/NuttXPortingGuide.html for a description of how to configure NuttX with this script. configure.c, cfgparser.c, and cfgparser.h can be used to build a work-alike @@ -189,7 +189,7 @@ mkconfig.c, cfgdefine.c, and cfgdefine.h When you configure NuttX, you will copy a configuration file called .config in the top level NuttX directory (See boards/README.txt or - Documentation/NuttxPortingGuide.html). The first time you make NuttX, + Documentation/NuttXPortingGuide.html). The first time you make NuttX, the top-level makefile will build the mkconfig executable from mkconfig.c (using Makefile.host). The top-level Makefile will then execute the mkconfig program to convert the .config file in the top level directory @@ -251,7 +251,7 @@ mkversion.c, cfgdefine.c, and cfgdefine.h program is used during the initial NuttX build. When you build NuttX there should be a version file called .version in - the top level NuttX directory (See Documentation/NuttxPortingGuide.html). + the top level NuttX directory (See Documentation/NuttXPortingGuide.html). The first time you make NuttX, the top-level makefile will build the mkversion executable from mkversion.c (using Makefile.host). The top- level Makefile will then execute the mkversion program to convert the @@ -1047,13 +1047,13 @@ uncrustify.cfg This is a configuration script for the uncrustify code beautifier. Uncrustify does well with forcing braces into "if" statements and - indenting per the Nuttx C coding standard. It correctly does things + indenting per the NuttX C coding standard. It correctly does things like placing all braces on separate lines at the proper indentation level. It cannot handle certain requirements of the coding standard such as - FAR attributes in pointer declarations. - - The Nuttx standard function header block comments. + - The NuttX standard function header block comments. - Naming violations such as use of CamelCase variable names, lower case pre-processor definitions, etc. diff --git a/tools/configure.c b/tools/configure.c index f7618d8a63..2270c8ae30 100644 --- a/tools/configure.c +++ b/tools/configure.c @@ -1562,7 +1562,7 @@ int main(int argc, char **argv, char **envp) debug("main: Checking arguments\n"); parse_args(argc, argv); - debug("main: Checking Nuttx Directories\n"); + debug("main: Checking NuttX Directories\n"); find_topdir(); check_configdir(); check_configured(); diff --git a/video/videomode/Make.defs b/video/videomode/Make.defs index 24638b5ec9..ce0bdb9b49 100644 --- a/video/videomode/Make.defs +++ b/video/videomode/Make.defs @@ -14,7 +14,7 @@ # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with the # distribution. -# 3. Neither the name Nuttx nor the names of its contributors may be +# 3. Neither the name NuttX nor the names of its contributors may be # used to endorse or promote products derived from this software # without specific prior written permission. #