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

Fix typos in README files.

Browse Source
This commit is contained in:
Nathan Hartman 2019-07-25 12:10:10 -06:00 committed by Gregory Nutt
parent 497db422c3
commit e581647f48
3 changed files with 28 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
configs/README.txt
View File

@ -6,9 +6,9 @@ by NuttX. This directory is retained in a separate repository and is a Sub-
Module of NuttX and will appear as nuttx/configs when the NuttX repository Module of NuttX and will appear as nuttx/configs when the NuttX repository
is cloned. is cloned.
The nuttx/configs directory is a part of the internal OS. It there should The nuttx/configs directory is a part of the internal OS. It should contain
contain only OS bring-up logic and driver initialization logic. THERE SHOULD only OS bring-up logic and driver initialization logic. THERE SHOULD BE NO
BE NO APPLICATION CALLABLE LOGIC IN THIS DIRECTORY. APPLICATION CALLABLE LOGIC IN THIS DIRECTORY.
If you have board-specific, application callable logic, that logic should not If you have board-specific, application callable logic, that logic should not
go here. Please consider using a sub-directory under apps/platform instead. go here. Please consider using a sub-directory under apps/platform instead.
@ -31,11 +31,11 @@ The NuttX configuration consists of:
o Processor architecture specific files. These are the files contained o Processor architecture specific files. These are the files contained
in the arch/<arch-name>/ directory. in the arch/<arch-name>/ directory.
o Chip/SoC specific files. Each processor processor architecture o Chip/SoC specific files. Each processor architecture is embedded
is embedded in chip or System-on-a-Chip (SoC) architecture. The in a chip or System-on-a-Chip (SoC) architecture. The full chip
full chip architecture includes the processor architecture plus architecture includes the processor architecture plus chip-specific
chip-specific interrupt logic, general purpose I/O (GIO) logic, and interrupt logic, general purpose I/O (GIO) logic, and specialized,
specialized, internal peripherals (such as UARTs, USB, etc.). internal peripherals (such as UARTs, USB, etc.).
These chip-specific files are contained within chip-specific These chip-specific files are contained within chip-specific
sub-directories in the arch/<arch-name>/ directory and are selected sub-directories in the arch/<arch-name>/ directory and are selected
@ -124,7 +124,7 @@ Make.defs -- This makefile fragment provides architecture and
different if CONFIG_DEBUG_FEATURES=y. different if CONFIG_DEBUG_FEATURES=y.
The included tools/Config.mk file contains additional definitions that may The included tools/Config.mk file contains additional definitions that may
be overriden in the architecture-specific Make.defs file as necessary: be overridden in the architecture-specific Make.defs file as necessary:
COMPILE, ASSEMBLE, ARCHIVE, CLEAN, and MKDEP macros COMPILE, ASSEMBLE, ARCHIVE, CLEAN, and MKDEP macros

18
configs/dk-tm4c129x/README.txt
View File

@ -1,8 +1,8 @@
README.txt README.txt
========== ==========
This README file discuss discusses the port of NuttX to the Texas This README file discusses the port of NuttX to the Texas Instruments
Instruments DK-TM4C129X Connected Development Kit. DK-TM4C129X Connected Development Kit.
Description Description
----------- -----------
@ -78,7 +78,7 @@ Using OpenOCD and GDB with ICDI
Starting OpenOCD Starting OpenOCD
If you are in the top-level NuttX build directlory then you should If you are in the top-level NuttX build directory then you should
be able to start the OpenOCD daemon like: be able to start the OpenOCD daemon like:
oocd.sh $PWD oocd.sh $PWD
@ -242,7 +242,7 @@ Networking Support
CONFIG_NET_ICMP=y : Enable ICMP networking CONFIG_NET_ICMP=y : Enable ICMP networking
CONFIG_NET_ICMP_SOCKET=y : Needed for NSH ping command CONFIG_NET_ICMP_SOCKET=y : Needed for NSH ping command
: Defaults should be okay for other options : Defaults should be okay for other options
f Application Configuration -> Network Utilities Application Configuration -> Network Utilities
CONFIG_NETDB_DNSCLIENT=y : Enable host address resolution CONFIG_NETDB_DNSCLIENT=y : Enable host address resolution
CONFIG_NETUTILS_TELNETD=y : Enable the Telnet daemon CONFIG_NETUTILS_TELNETD=y : Enable the Telnet daemon
CONFIG_NETUTILS_TFTPC=y : Enable TFTP data file transfers for get and put commands CONFIG_NETUTILS_TFTPC=y : Enable TFTP data file transfers for get and put commands
@ -257,8 +257,8 @@ f Application Configuration -> Network Utilities
CONFIG_NSH_NOMAC=y : Need to make up a bogus MAC address CONFIG_NSH_NOMAC=y : Need to make up a bogus MAC address
: Defaults should be okay for other options : Defaults should be okay for other options
You can also enable enable the DHCPC client for networks that use You can also enable the DHCPC client for networks that use dynamically
dynamically assigned address: assigned address:
Application Configuration -> Network Utilities Application Configuration -> Network Utilities
CONFIG_NETUTILS_DHCPC=y : Enables the DHCP client CONFIG_NETUTILS_DHCPC=y : Enables the DHCP client
@ -314,7 +314,7 @@ f Application Configuration -> Network Utilities
56 bytes from 10.0.0.1: icmp_seq=10 time=0 ms 56 bytes from 10.0.0.1: icmp_seq=10 time=0 ms
10 packets transmitted, 10 received, 0% packet loss, time 10100 ms 10 packets transmitted, 10 received, 0% packet loss, time 10100 ms
NOTE: In this configuration is is normal to have packet loss > 0% NOTE: In this configuration it is normal to have packet loss > 0%
the first time you ping due to the default handling of the ARP the first time you ping due to the default handling of the ARP
table. table.
@ -358,7 +358,7 @@ f Application Configuration -> Network Utilities
numerous timeouts and retries, the network will not be available -- numerous timeouts and retries, the network will not be available --
even if the network cable is plugged in later. even if the network cable is plugged in later.
The long delays can be eliminated by using a separate the network The long delays can be eliminated by using a separate network
initialization thread discussed below. Recovering after the network initialization thread discussed below. Recovering after the network
becomes available requires the network monitor feature, also discussed becomes available requires the network monitor feature, also discussed
below. below.
@ -409,7 +409,7 @@ f Application Configuration -> Network Utilities
CONFIG_NETDEV_PHY_IOCTL. Enable PHY IOCTL commands in the Ethernet CONFIG_NETDEV_PHY_IOCTL. Enable PHY IOCTL commands in the Ethernet
device driver. Special IOCTL commands must be provided by the Ethernet device driver. Special IOCTL commands must be provided by the Ethernet
driver to support certain PHY operations that will be needed for link driver to support certain PHY operations that will be needed for link
management. There operations are not complex and are implemented for management. These operations are not complex and are implemented for
the Atmel SAMA5 family. the Atmel SAMA5 family.
CONFIG_ARCH_PHY_INTERRUPT. This is not a user selectable option. CONFIG_ARCH_PHY_INTERRUPT. This is not a user selectable option.

8
configs/tm4c1294-launchpad/README.txt
View File

@ -32,7 +32,7 @@ Where <subdir> is one of the following:
nsh: nsh:
--- ---
Configures the NuttShell (nsh) located at apps/examples/nsh. The Configures the NuttShell (nsh) located at apps/examples/nsh. The
configuration enables the serial ICDI vitual UART on UART0. Support for configuration enables the serial ICDI virtual UART on UART0. Support for
builtin applications is enabled, but in the base configuration no builtin applications is enabled, but in the base configuration no
builtin applications are selected. builtin applications are selected.
@ -113,9 +113,9 @@ Where <subdir> is one of the following:
Telnet does work with IPv6 but is not enabled in this Telnet does work with IPv6 but is not enabled in this
configuration (but could be). configuration (but could be).
2. This configuration can be modified to that both IPv4 and IPv6 2. This configuration can be modified so that both IPv4 and IPv6
are support. Here is a summary of the additional configuration are supported. Here is a summary of the additional configuration
settings requird to support both IPv4 and IPv6: settings required to support both IPv4 and IPv6:
CONFIG_NET_IPv4=y CONFIG_NET_IPv4=y
CONFIG_NET_ARP=y CONFIG_NET_ARP=y