You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by ag...@apache.org on 2020/11/28 11:20:44 UTC
[incubator-nuttx] 06/06: style/Document: remove unnecessary
trailing whitespace
This is an automated email from the ASF dual-hosted git repository.
aguettouche pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-nuttx.git
commit b1a042734ff595569bb45bf9a7c248e66efd9f49
Author: chao.an <an...@xiaomi.com>
AuthorDate: Sat Nov 28 12:03:51 2020 +0800
style/Document: remove unnecessary trailing whitespace
N/A
Signed-off-by: chao.an <an...@xiaomi.com>
---
DISCLAIMER-WIP | 22 ++++++++++----------
LICENSE | 2 +-
README.md | 10 ++++-----
boards/arm/sama5/giant-board/README.md | 20 +++++++++---------
boards/renesas/rx65n/rx65n-grrose/README.txt | 2 +-
.../renesas/rx65n/rx65n-grrose/include/README.TXT | 2 +-
boards/renesas/rx65n/rx65n-rsk2mb/README.txt | 2 +-
boards/x86_64/intel64/qemu-intel64/README.txt | 10 ++++-----
boards/xtensa/esp32/esp32-core/README.txt | 24 +++++++++++-----------
libs/libnx/README.txt | 22 ++++++++++----------
10 files changed, 58 insertions(+), 58 deletions(-)
diff --git a/DISCLAIMER-WIP b/DISCLAIMER-WIP
index 102e9ea..e4eb139 100644
--- a/DISCLAIMER-WIP
+++ b/DISCLAIMER-WIP
@@ -1,20 +1,20 @@
-Apache NuttX is an effort undergoing incubation at The Apache Software Foundation (ASF),
-sponsored by the Apache Incubator. Incubation is required of all newly accepted projects
-until a further review indicates that the infrastructure, communications, and decision
-making process have stabilized in a manner consistent with other successful ASF projects.
-While incubation status is not necessarily a reflection of the completeness or stability
+Apache NuttX is an effort undergoing incubation at The Apache Software Foundation (ASF),
+sponsored by the Apache Incubator. Incubation is required of all newly accepted projects
+until a further review indicates that the infrastructure, communications, and decision
+making process have stabilized in a manner consistent with other successful ASF projects.
+While incubation status is not necessarily a reflection of the completeness or stability
of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
-Some of the incubating project's releases may not be fully compliant with ASF policy. For
-example, releases may have incomplete or un-reviewed licensing conditions. What follows is
-a list of known issues the project is currently aware of (note that this list, by definition,
-is likely to be incomplete):
+Some of the incubating project's releases may not be fully compliant with ASF policy. For
+example, releases may have incomplete or un-reviewed licensing conditions. What follows is
+a list of known issues the project is currently aware of (note that this list, by definition,
+is likely to be incomplete):
* Releases may have incomplete licensing conditions.
* Some ASF files still have BSD headers. Most of the top contributors have signed an ICLA and
we are working on updating the headers and getting approvals from other copyright holders.
If you are planning to incorporate this work into your product/project, please be aware that
-you will need to conduct a thorough licensing review to determine the overall implications of
-including this work. For the current status of this project through the Apache Incubator
+you will need to conduct a thorough licensing review to determine the overall implications of
+including this work. For the current status of this project through the Apache Incubator
visit: https://incubator.apache.org/projects/nuttx.html
diff --git a/LICENSE b/LICENSE
index b0d6de0..a1375f7 100644
--- a/LICENSE
+++ b/LICENSE
@@ -199,7 +199,7 @@
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-
+
------------------------------------------------------------------------------
uIP
diff --git a/README.md b/README.md
index d8316e8..ad1b029 100644
--- a/README.md
+++ b/README.md
@@ -556,7 +556,7 @@ in the source tree.
* Legacy download locations:
- <https://bitbucket.org/nuttx/nuttx/downloads>
+ <https://bitbucket.org/nuttx/nuttx/downloads>
<https://sourceforge.net/projects/nuttx/files/nuttx/>
## Semi-Optional apps/ Package
@@ -682,8 +682,8 @@ some scripts like configure.sh. Before cloning, do the following:
These are standalone repositories:
- * <https://gitbox.apache.org/repos/asf/incubator-nuttx-apps>
- or
+ * <https://gitbox.apache.org/repos/asf/incubator-nuttx-apps>
+ or
<https://github.com/apache/incubator-nuttx-apps.git>
This directory holds an optional package of applications and libraries
@@ -993,9 +993,9 @@ The `menuconfig` make target depends on two things:
case, you can use the modified version of kconfig-frontends
that can be found at
- <http://uvc.de/posts/linux-kernel-configuration-tool-kconfig-under-windows.html>
+ <http://uvc.de/posts/linux-kernel-configuration-tool-kconfig-under-windows.html>
- or a more recent port that can be found at
+ or a more recent port that can be found at
<http://reclonelabs.com/more-kconfig-awesomeness-for-windows/>.
diff --git a/boards/arm/sama5/giant-board/README.md b/boards/arm/sama5/giant-board/README.md
index 159a55f..79d9fe0 100644
--- a/boards/arm/sama5/giant-board/README.md
+++ b/boards/arm/sama5/giant-board/README.md
@@ -34,8 +34,8 @@ or a zip file of the required files from this page:
https://www.starcat.io/starcat-nuttx/
The SD Card has to be FAT formatted, have an AT91Bootstrap binary called boot.bin,
-a U-Boot binary called u-boot.bin as well as a compiled device tree for the
-SAMA5D27C-D1G called `at91-sama5d27_giantboard.dtb` in the `dtbs/` folder. You can
+a U-Boot binary called u-boot.bin as well as a compiled device tree for the
+SAMA5D27C-D1G called `at91-sama5d27_giantboard.dtb` in the `dtbs/` folder. You can
build these yourself using the tools at
https://github.com/Groboards/giantboard-tools
@@ -48,7 +48,7 @@ The layout should look like this:
u-boot.bin
dtbs/
at91-sama5d27_giantboard.dtb
-
+
You only need uboot.env if you want to boot automatically. See the U-Boot
documentation for instructions on how to create this file.
@@ -379,7 +379,7 @@ need to know how to configure the subsystem.
CONFIG_U[S]ARTn_2STOP - Two stop bits
#### AT91SAMA5 USB Host Configuration
-
+
Pre-requisites
CONFIG_USBDEV - Enable USB device support
@@ -447,7 +447,7 @@ NOTES:
Here are the relevant current settings:
Build Setup:
-
+
CONFIG_HOST_WINDOWS=y : Microsoft Windows
CONFIG_WINDOWS_CYGWIN=y : Using Cygwin or other POSIX environment
@@ -467,8 +467,8 @@ Board Selection -> CPU Frequency
Summary: Some of the descriptions below are long and wordy. Here is the
concise summary of the available Giant Board configurations:
-- nsh:
-
+- nsh:
+
This is a basic NuttShell (NSH) configuration.
There may be issues with some of these configurations. See the details
@@ -609,7 +609,7 @@ concise summary of the available Giant Board configurations:
on the SD Card.
NuttX will mount the SD Card at `/mnt/mmcsd1`.
-
+
- sdmmc-net-nsh:
-
- This is a combination of the netnsh and sdmmcnsh configurations.
+
+ This is a combination of the netnsh and sdmmcnsh configurations.
diff --git a/boards/renesas/rx65n/rx65n-grrose/README.txt b/boards/renesas/rx65n/rx65n-grrose/README.txt
index e44c137..6ef8a25 100644
--- a/boards/renesas/rx65n/rx65n-grrose/README.txt
+++ b/boards/renesas/rx65n/rx65n-grrose/README.txt
@@ -222,7 +222,7 @@ CONFIG_EXAMPLES_UDPBLASTER_TARGETIP=0x0a4b189b (10.75.24.155) ---------> Target
RSPI
-----------
-For GRROSE board only channel 1 can be tested since RSPI channel1 pinout is only brought out as
+For GRROSE board only channel 1 can be tested since RSPI channel1 pinout is only brought out as
Pin number 2 and 3 in CN4 is used for MOSIB and MISOB respectively.
RTC
diff --git a/boards/renesas/rx65n/rx65n-grrose/include/README.TXT b/boards/renesas/rx65n/rx65n-grrose/include/README.TXT
index 276276b..4270f9a 100644
--- a/boards/renesas/rx65n/rx65n-grrose/include/README.TXT
+++ b/boards/renesas/rx65n/rx65n-grrose/include/README.TXT
@@ -60,7 +60,7 @@ README
gid: Group ID
users: A comma separated list of members of the group
- /etc/init.d/rcS should have the following contents :
+ /etc/init.d/rcS should have the following contents :
vi rcS
echo "This is NuttX"
diff --git a/boards/renesas/rx65n/rx65n-rsk2mb/README.txt b/boards/renesas/rx65n/rx65n-rsk2mb/README.txt
index 44ea05a..b6af98c 100644
--- a/boards/renesas/rx65n/rx65n-rsk2mb/README.txt
+++ b/boards/renesas/rx65n/rx65n-rsk2mb/README.txt
@@ -114,7 +114,7 @@ Ethernet Connections
P71 ET0_MDIO
P54 ET0_LINKSTA
------ ---------
-
+
USB Device
-----------
diff --git a/boards/x86_64/intel64/qemu-intel64/README.txt b/boards/x86_64/intel64/qemu-intel64/README.txt
index 57bf019..76c9fae 100644
--- a/boards/x86_64/intel64/qemu-intel64/README.txt
+++ b/boards/x86_64/intel64/qemu-intel64/README.txt
@@ -50,7 +50,7 @@ menuentry "kernel" {
Use the following command to create the disk.
P.S. In some distros, `grub-mkrescue` is called `grub2-mkrescue`
```
-grub-mkrescue -o boot.iso iso
+grub-mkrescue -o boot.iso iso
```
@@ -69,7 +69,7 @@ It supports creations of virtual machines in Linux systems.
It is usually coupled with Qemu as its I/O supporting layer.
The qemu can be build from source or downloaded from distro repositories.
-However, a modern CPU and KVM support are mandatory because the X2APIC is not available
+However, a modern CPU and KVM support are mandatory because the X2APIC is not available
in pure emulator mode.
This mean using this build with qemu in windows or old x86 machine can be frustrating.
In such case, looks the next section and use bochs emulator instead.
@@ -85,7 +85,7 @@ Running QEMU
Use control-a 1 and 2 to switch between.
Use control-a x to terminate the emulation.
- P.S. Make sure that you CPU supports the mandatory features. Look at Real machine
+ P.S. Make sure that you CPU supports the mandatory features. Look at Real machine
section for more information.
Bochs
@@ -98,7 +98,7 @@ Here are some links (which will probably be mostly outdated by the time your rea
Home Page: http://bochs.sourceforge.net
The bochs can be build from source.
-Unlike qemu, it do not rely on KVM to support modern hardware features, therefor it can
+Unlike qemu, it do not rely on KVM to support modern hardware features, therefor it can
also be used under windows.
When building bochs, remember to enable x86-64 support with "--enable-x86-64".
If you also want the support of SIMD instruction, enable them with "--enable-avx --enable-evex".
@@ -121,7 +121,7 @@ Running Bochs
```
com1: enabled=1, mode=file, dev=com1.out
```
-
+
In the top-level NuttX directory:
```
diff --git a/boards/xtensa/esp32/esp32-core/README.txt b/boards/xtensa/esp32/esp32-core/README.txt
index 31b487d..1c54e12 100644
--- a/boards/xtensa/esp32/esp32-core/README.txt
+++ b/boards/xtensa/esp32/esp32-core/README.txt
@@ -23,7 +23,7 @@ Contents
o Buttons and LEDs
o Ethernet
o 64-bit Timers
- o Watchdog Timers
+ o Watchdog Timers
o SMP
o OpenOCD for the ESP32
o Executing and Debugging from FLASH and IRAM
@@ -211,7 +211,7 @@ Ethernet
connect to an external PHY chip. Current driver also only supports RMII option.
The RMII GPIO pins are fixed, but the SMI and functional GPIO pins are optional.
-
+
RMII GPIO pins are as following:
ESP32 GPIO PHY Chip GPIO
@@ -250,12 +250,12 @@ causes failing to bring the ESP32 chip up.
acessible as character drivers, the configuration along with a guidance on how
to run the example and the description of the application level interface can be found here:
- https://nuttx.apache.org/docs/latest/components/drivers/character/timer.html
+ https://nuttx.apache.org/docs/latest/components/drivers/character/timer.html
Watchdog Timers
===============
- ESP32 has 3 WDTs. 2 MWDTS from the Timers Module and 1 RWDT from the RTC Module
+ ESP32 has 3 WDTs. 2 MWDTS from the Timers Module and 1 RWDT from the RTC Module
(Currently not supported yet). They're acessible as character drivers,
The configuration along with a guidance on how to run the example and the description
of the application level interface can be found here:
@@ -824,36 +824,36 @@ NOTES:
2MB or 4MB depending on PSRAM chip used on your board:
nsh> ramtest -w 0x3F800000 65536
- RAMTest: Marching ones: 3f800000 65536
- RAMTest: Marching zeroes: 3f800000 65536
+ RAMTest: Marching ones: 3f800000 65536
+ RAMTest: Marching zeroes: 3f800000 65536
RAMTest: Pattern test: 3f800000 65536 55555555 aaaaaaaa
- RAMTest: Pattern test: 3f800000 65536 66666666 99999999
- RAMTest: Pattern test: 3f800000 65536 33333333 cccccccc
+ RAMTest: Pattern test: 3f800000 65536 66666666 99999999
+ RAMTest: Pattern test: 3f800000 65536 33333333 cccccccc
RAMTest: Address-in-address test: 3f800000 65536
timer:
This config test the general use purpose timers. It includes the 4 timers,
adds driver support, registers the timers as devices and includes the timer
- example.
+ example.
To test it, just run the following:
`nsh> timer -d /dev/timerx`
- Where x in the timer instance.
+ Where x in the timer instance.
watchdog:
This config test the watchdog timers. It includes the 2 MWDTS,
adds driver support, registers the WDTs as devices and includes the watchdog
- example.
+ example.
To test it, just run the following:
`nsh> wdog -d /dev/watchdogx`
- Where x in the watchdog instance.
+ Where x in the watchdog instance.
Things to Do
============
diff --git a/libs/libnx/README.txt b/libs/libnx/README.txt
index be0941a..4af57e1 100644
--- a/libs/libnx/README.txt
+++ b/libs/libnx/README.txt
@@ -1,11 +1,11 @@
-README
-======
-
- The graphics capability consist both of components internal to the RTOS
- and of user-callable interfaces. In the NuttX kernel mode build there are
- some components of the graphics subsystem are callable in user mode and
- other components that are internal to the RTOS. This directory, libs/libnx/,
- contains only those user-callable components.
-
- The RTOS internal functions are contained in the graphics/ directory.
- Please refer to graphics/README.txt for more detailed information.
+README
+======
+
+ The graphics capability consist both of components internal to the RTOS
+ and of user-callable interfaces. In the NuttX kernel mode build there are
+ some components of the graphics subsystem are callable in user mode and
+ other components that are internal to the RTOS. This directory, libs/libnx/,
+ contains only those user-callable components.
+
+ The RTOS internal functions are contained in the graphics/ directory.
+ Please refer to graphics/README.txt for more detailed information.