sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Change all 'Nuttx' to 'NuttX'

Browse Source 
Unify the naming convention

Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
This commit is contained in:
Xiang Xiao 2020-10-19 12:09:06 +08:00 committed by Brennan Ashton
parent d5c6bfe6cf
commit eb4121ce38
117 changed files with 195 additions and 201 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Documentation/applications/nsh/commands.rst
View File

@ -736,7 +736,7 @@ at <link> for the existing file or directory, <target>. This
implementation is simplified for use with NuttX in these ways:
- Links may be created only within the NuttX top-level, `pseudo
file system <NuttxUserGuide.html#FileSystemOverview>`__. No
file system <NuttXUserGuide.html#FileSystemOverview>`__. No
file system currently supported by NuttX provides symbolic
links.
- For the same reason, only soft links are implemented.
@ -875,7 +875,7 @@ of ``<path>`` 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 <NuttxUserGuide.html#FileSystemOverview>`__
`pseudo file system <NuttXUserGuide.html#FileSystemOverview>`__
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()`` <mkfatfs>`__ NuttX API. This block device must
reside in the NuttX `pseudo file
system <NuttxUserGuide.html#FileSystemOverview>`__ and must have
system <NuttXUserGuide.html#FileSystemOverview>`__ 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 ``<path>``. 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()`` <NuttxUserGuide.html#mkfifo>`__ NuttX API.
```mkfifo()`` <NuttXUserGuide.html#mkfifo>`__ NuttX API.
**Example**::
@ -1018,23 +1018,23 @@ way association, binding:
supported value for ``<fstype>``
#. **Block Device.** The ``<block-device>`` argument is the full
or relative path to a block driver inode in the `pseudo file
system <NuttxUserGuide.html#FileSystemOverview>`__. By
system <NuttXUserGuide.html#FileSystemOverview>`__. By
convention, this is a name under the ``/dev`` sub-directory.
This ``<block-device>`` must have been previously formatted
with the same file system type as specified by ``<fstype>``
#. **Mount Point.** The mount point, ``<dir-path>``, is the
location in the `pseudo file
system <NuttxUserGuide.html#FileSystemOverview>`__ where the
system <NuttXUserGuide.html#FileSystemOverview>`__ where the
mounted volume will appear. This mount point can only reside in
the NuttX `pseudo file
system <NuttxUserGuide.html#FileSystemOverview>`__. By
system <NuttXUserGuide.html#FileSystemOverview>`__. 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 <NuttxUserGuide.html#FileSystemOverview>`__, it may be
system <NuttXUserGuide.html#FileSystemOverview>`__, 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 ``<file-path>`` name from the
mounted file system. Recall that NuttX uses a `pseudo file
system <NuttxUserGuide.html#FileSystemOverview>`__ for its root
system <NuttXUserGuide.html#FileSystemOverview>`__ 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 ``<dir-path>`` directory from
the mounted file system. Recall that NuttX uses a `pseudo file
system <NuttxUserGuide.html#FileSystemOverview>`__ for its root
system <NuttXUserGuide.html#FileSystemOverview>`__ 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*

2
Documentation/applications/nsh/config.rst
View File

@ -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. <NuttxPortingGuide.html>`__
discussed in the `NuttX Porting Guide. <NuttXPortingGuide.html>`__
Configuration settings specific to NSH as discussed at the
`bottom <#nshconfiguration>`__ of this document.

2
Documentation/components/drivers/character/index.rst
View File

@ -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 <NuttxUserGuide.html#driveroperations>`__ including
operations <NuttXUserGuide.html#driveroperations>`__ including
``open()``, ``close()``, ``read()``, ``write()``, etc.
- **Specialized Character Drivers**. Within the common character

2
Documentation/components/drivers/special/syslog.rst
View File

@ -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
-----------------

4
Documentation/components/nxflat.rst
View File

@ -42,7 +42,7 @@ NXFLAT is derived from `XFLAT <http://xflat.sourceforge.net/>`__. 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 ``<some-dir>/nuttx``
- You must have already configured NuttX in ``<some-dir>/nuttx``
- Download the buildroot package ``buildroot-0.x.y`` into
``<some-dir>``
- Unpack ``<some-dir>/buildroot-0.x.y.tar.gz`` using a command like ``tar zxf buildroot-0.x.y``. This will result in a new directory like ``<some-dir>/buildroot-0.x.y``

2
Documentation/guides/nfs.rst
View File

@ -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`` <NuttxPortingGuide.html#NxFileSystem>`__ and is
```porting guide`` <NuttXPortingGuide.html#NxFileSystem>`__ 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)

2
Documentation/guides/simulator.rst
View File

@ -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

10
Documentation/introduction/detailed_support.rst
View File

@ -185,7 +185,7 @@ There are ports to two Microchip SAMA5D3 boards:
- A full-loaded NuttShell (:ref:`NSH <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 <https://cwiki.apache.org/confluence/display/NUTTX/High+Performance%2C+Zero+Latency+Interrupts>`__.
@ -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 <https://github.com/apache/incubator-nuttx/blob/master/boards/arm/lpc17xx_40xx/zkit-arm-1769/README.txt>`__
@ -2455,7 +2455,7 @@ Also refer to the NuttX board
`README <https://github.com/apache/incubator-nuttx/blob/master/boards/arm/samd5e5/metro-m4/README.txt>`__
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
----------------

2
Documentation/introduction/resources.rst
View File

@ -9,7 +9,7 @@ Here's a list of Apache NuttX resources that you might find helpful:
* Apache NuttX
* `Apache NuttX website <https://apache.nuttx.org>`_
* `Apache NuttX online documentation <https://cwiki.apache.org/confluence/display/NUTTX/Nuttx>`_
* `Apache NuttX online documentation <https://cwiki.apache.org/confluence/display/NUTTX/NuttX>`_
* `Apache NuttX mailing list <https://nuttx.apache.org/community/>`_ – a very active mailing list, the place to get help with your application or any questions you have about NuttX.
* `Apache NuttX YouTube channel <https://www.youtube.com/channel/UC0QciIlcUnjJkL5yJJBmluw/videos>`_ – Alan Carvalho de Assis's YouTube channel on NuttX. It's a source of a lot of great practical information.
* `Apache NuttX Coding Standard <https://cwiki.apache.org/confluence/display/NUTTX/Coding+Standard>`_ — How code should look when you submit new files or modify existing ones.

2
Documentation/quickstart/organization.rst
View File

@ -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

2
Documentation/reference/user/02_task_scheduling.rst
View File

@ -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

2
Documentation/reference/user/09_env_vars.rst
View File

@ -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`

2
Documentation/reference/user/10_filesystem.rst
View File

@ -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 <NuttxPortingGuide.html#DeviceDrivers>`__ *nodes* in the any
`driver <NuttXPortingGuide.html#DeviceDrivers>`__ *nodes* in the any
pseudo file system directory. (By convention, however, all driver nodes
should be in the ``/dev`` pseudo file system directory).

4
Documentation/reference/user/index.rst
View File

@ -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 <NuttxPortingGuide.html>`__.
Guide <NuttXPortingGuide.html>`__.
Information about configuring and building NuttX is also needed by the
application developer. That information can also be found in the `NuttX
Porting Guide <NuttxPortingGuide.html#configandbuild>`__.
Porting Guide <NuttXPortingGuide.html#configandbuild>`__.
.. toctree::
:maxdepth: 1

2
Kconfig
View File

@ -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

4
README.md
View File

@ -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:
<https://cwiki.apache.org/NUTTX/Nuttx>
<https://cwiki.apache.org/NUTTX/NuttX>
## 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.

30
ReleaseNotes
View File

@ -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

2
TODO
View File

@ -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.

2
arch/arm/include/lpc43xx/chip.h
View File

@ -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

2
arch/arm/src/arm/arm_head.S
View File

@ -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.

2
arch/arm/src/armv7-a/arm_pghead.S
View File

@ -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 */

2
arch/arm/src/dm320/dm320_restart.S
View File

@ -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

2
arch/arm/src/sama5/sam_trng.c
View File

@ -4,7 +4,7 @@
* Copyright (C) 2013, 2016-2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
*
* 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 <mh@uvc.de>

4
arch/arm/src/samv7/sam_trng.c
View File

@ -4,8 +4,8 @@
* Copyright (C) 2015-2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt <gnutt@nuttx.org>
*
* 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 <mh@uvc.de>

4
arch/arm/src/stm32/stm32_adc.c
View File

@ -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

2
arch/risc-v/src/gap8/gap8_head.S
View File

@ -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

2
arch/risc-v/src/gap8/gap8_interrupt.c
View File

@ -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)
{

4
arch/risc-v/src/gap8/gap8_uart.c
View File

@ -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.
*
****************************************************************************/

2
arch/sim/src/sim/up_head.c
View File

@ -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();
}

4
arch/xtensa/src/esp32/esp32_wifi_adapter.c
View File

@ -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

4
boards/Kconfig
View File

@ -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"

12
boards/README.txt
View File

@ -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
^^^^^^^^^^^^^^^^^

2
boards/arm/am335x/beaglebone-black/README.txt
View File

@ -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

2
boards/arm/c5471/c5471evm/README.txt
View File

@ -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 <some-dir>nuttx.
1. You must have already configured NuttX in <some-dir>nuttx.
tools/configure.sh c5471evm:<sub-dir>

2
boards/arm/dm320/ntosd-dm320/README.txt
View File

@ -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 <some-dir>nuttx.
1. You must have already configured NuttX in <some-dir>nuttx.
tools/configure.sh ntosd-dm320:<sub-dir>

2
boards/arm/dm320/ntosd-dm320/doc/README.txt
View File

@ -47,7 +47,7 @@ General instructions.
make oldconfig
make
6. Build Nuttx:
6. Build NuttX:
cd <directory>nuttx
make

2
boards/arm/imxrt/imxrt1060-evk/README.txt
View File

@ -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.

2
boards/arm/kinetis/freedom-k28f/include/board.h
View File

@ -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

2
boards/arm/kinetis/freedom-k64f/include/board.h
View File

@ -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.

2
boards/arm/kinetis/freedom-k66f/include/board.h
View File

@ -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

2
boards/arm/kl/freedom-kl25z/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh freedom-kl25z:<sub-dir>

2
boards/arm/kl/freedom-kl26z/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh freedom-kl26z:<sub-dir>

1
boards/arm/lpc17xx_40xx/olimex-lpc1766stk/configs/usbserial/defconfig
View File

@ -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

2
boards/arm/lpc214x/mcu123-lpc214x/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh eagle100:<sub-dir>

1
boards/arm/lpc214x/mcu123-lpc214x/configs/usbserial/defconfig
View File

@ -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

2
boards/arm/lpc2378/olimex-lpc2378/README.txt
View File

@ -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.

2
boards/arm/lpc31xx/ea3131/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh ea3131:<sub-dir>

1
boards/arm/lpc31xx/ea3131/configs/usbserial/defconfig
View File

@ -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

2
boards/arm/lpc31xx/ea3152/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh ea3152:<sub-dir>

2
boards/arm/lpc31xx/olimex-lpc-h3131/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh olimex-lpc-h3131:<sub-dir>

2
boards/arm/nuc1xx/nutiny-nuc120/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh nutiny-nuc120:<sub-dir>

2
boards/arm/s32k1xx/s32k146evb/README.txt
View File

@ -114,7 +114,7 @@ Thread-Aware Debugging with Eclipse
Based on correspondence with Han Raaijmakers <han.raaijmakers@nxp.com>
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.

6
boards/arm/sama5/sama5d3-xplained/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh sama5d3-xplained:<sub-dir>
@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh sama5d3-xplained:<sub-dir>

4
boards/arm/sama5/sama5d3x-ek/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh sama5d3x-ek:<sub-dir>
@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh sama5d3x-ek:<sub-dir>

1
boards/arm/sama5/sama5d3x-ek/configs/demo/defconfig
View File

@ -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"

4
boards/arm/sama5/sama5d4-ek/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh sama5d4-ek:<sub-dir>
@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh sama5d4-ek:<sub-dir>

4
boards/arm/samd2l2/samd20-xplained/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh samd20-xplained:<sub-dir>

4
boards/arm/samd2l2/saml21-xplained/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh saml21-xplained:<sub-dir>

2
boards/arm/samv7/samv71-xult/README.txt
View File

@ -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 *

2
boards/arm/stm32/fire-stm32v2/README.txt
View File

@ -237,7 +237,7 @@ for more information. Using the script:
cd <nuttx-build-directory>
boards/arm/stm32/fire-stm32v2/tools/oocd.sh $PWD
2) Load Nuttx
2) Load NuttX
cd <nuttx-built-directory>
arm-none-eabi-gdb nuttx

2
boards/arm/stm32/hymini-stm32v/README.txt
View File

@ -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.

1
boards/arm/stm32/hymini-stm32v/configs/usbserial/defconfig
View File

@ -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

4
boards/arm/stm32/nucleo-f446re/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh lpcxpresso-lpc1768:<sub-dir>

4
boards/arm/stm32/nucleo-f4x1re/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh lpcxpresso-lpc1768:<sub-dir>

2
boards/arm/stm32/stm3210e-eval/README.txt
View File

@ -100,7 +100,7 @@ for more information. Using the script:
cd <nuttx-build-directory>
boards/arm/stm32/stm3210e-eval/tools/oocd.sh $PWD
2) Load Nuttx
2) Load NuttX
cd <nuttx-built-directory>
arm-none-eabi-gdb nuttx

1
boards/arm/stm32/stm3210e-eval/configs/usbserial/defconfig
View File

@ -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

2
boards/arm/stm32/stm32f4discovery/README.txt
View File

@ -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)

2
boards/arm/stm32/viewtool-stm32f107/README.txt
View File

@ -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

2
boards/arm/stm32f7/nucleo-144/README.txt
View File

@ -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

4
boards/arm/stm32l4/nucleo-l432kc/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh lpcxpresso-lpc1768:<sub-dir>

6
boards/arm/stm32l4/nucleo-l476rg/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh lpcxpresso-lpc1768:<sub-dir>
@ -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.

4
boards/arm/str71x/olimex-strp711/README.txt
View File

@ -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 <some-dir>nuttx.
1. You must have already configured NuttX in <some-dir>nuttx.
tools/configure.sh olimex-strp711:<sub-dir>

2
boards/arm/tiva/dk-tm4c129x/README.txt
View File

@ -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:

2
boards/arm/tiva/tm4c123g-launchpad/README.txt
View File

@ -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

4
boards/avr/at90usb/micropendous3/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh micropendous3:<sub-dir>

4
boards/avr/at90usb/teensy-2.0/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh Teensy++:<sub-dir>

4
boards/avr/atmega/amber/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh amber:<sub-dir>

2
boards/hc/m9s12/demo9s12ne64/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh demo9s12nec64:<sub-dir>

2
boards/hc/m9s12/ne64badge/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh ne64badge:<sub-dir>

2
boards/mips/pic32mx/mirtoo/README.txt
View File

@ -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.

8
boards/mips/pic32mx/pic32mx-starterkit/README.txt
View File

@ -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 <subdir> 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

2
boards/mips/pic32mx/pic32mx7mmb/README.txt
View File

@ -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.

2
boards/mips/pic32mx/sure-pic32mx/README.txt
View File

@ -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.

2
boards/mips/pic32mx/ubw32/README.txt
View File

@ -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.

2
boards/misoc/lm32/misoc/README.txt
View File

@ -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 <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh misoc:<sub-dir>
make oldconfig context

2
boards/renesas/sh1/us7032evb1/README.txt
View File

@ -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 <some-dir>nuttx.
1. You must have already configured NuttX in <some-dir>nuttx.
tools/configure.sh us7032evb1:<sub-dir>

2
boards/x86/qemu/qemu-i486/README.txt
View File

@ -116,7 +116,7 @@ Cygwin Buildroot Toolchain
Buildroot Instructions
----------------------
1. You must have already configured Nuttx in <some-dir>/nuttx.
1. You must have already configured NuttX in <some-dir>/nuttx.
tools/configure.sh qemu-i486:<sub-dir>

4
boards/x86_64/intel64/qemu-intel64/README.txt
View File

@ -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):

34
drivers/sensors/README.txt
View File

@ -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.

2
drivers/syslog/README.txt
View File

@ -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

2
fs/binfs/Make.defs
View File

@ -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.
#

2
fs/cromfs/Make.defs
View File

@ -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.
#

2
fs/fat/Make.defs
View File

@ -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.
#

2
fs/hostfs/Make.defs
View File

@ -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.
#

2
fs/mmap/Make.defs
View File

@ -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.
#

2
fs/nfs/Make.defs
View File

@ -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.
#

2
fs/nxffs/Make.defs
View File

@ -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.
#

2
fs/procfs/Make.defs
View File

@ -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.
#

2
fs/romfs/Make.defs
View File

@ -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.
#

2
fs/smartfs/Make.defs
View File

@ -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.
#

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