Remove the double blank line from source files

Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
2026-10-06 11:03:16 +08:00 · 2022-02-20 20:10:14 +01:00
parent 746b68befc
commit 1d1bdd85a3
191 changed files with 0 additions and 501 deletions
@@ -169,7 +169,6 @@ that in ``apps/examples/hello/Makefile`` is abstracted below:
      context:
        $(call REGISTER,$(APPNAME),$(PRIORITY),$(STACKSIZE),$(APPNAME)_main)

-
 **Other Uses of Built-In Application.** The primary purpose of builtin
 applications is to support command line execution of applications from
 NSH. However, there is one other use of builtin applications that should
@@ -1843,4 +1843,3 @@ Example::

 ``ping6`` differs from ``ping`` in that it uses IPv6 addressing.

-
@@ -398,7 +398,6 @@ CMD                 w/o ``CONFIG_NSH_VARS``               w/``CONFIG_NSH_VARS``
 ``env``             Lists all environment variables       Lists all environment variables (*only*)
 ==================  ===================================   =============================================

-
 If Telnet is selected for the NSH console, then we must configure the
 resources used by the Telnet daemon and by the Telnet clients.

@@ -358,4 +358,3 @@ containing the ROMFS file system image.
 NuttShell <#customizingnsh>`__ for additional, more detailed
 information about the NSH start-up script and how to modify it.

-
@@ -75,7 +75,6 @@ pointer to a write-able instance of :c:struct:`binfmt_s`.
      int (*load)(FAR struct binary_s *bin); /* Verify and load binary into memory */
    };

-
  The ``load`` method is used to load the binary format into memory. It
  returns either ``OK`` (0) meaning that the binary object was loaded
  successfully, or a negated ``errno`` indicating why the object was not
@@ -38,4 +38,3 @@ Block device drivers have these properties:
 -  **Examples**. ``drivers/loop.c``,
   ``drivers/mmcsd/mmcsd_spi.c``, ``drivers/ramdisk.c``, etc.

-
@@ -140,4 +140,3 @@ application decoding interfaces.
 these interfaces. These stream interfaces are defined in
 ``include/nuttx/streams.h``.

-
@@ -165,7 +165,6 @@ Notectl Device (``/dev/notectl``)
  :return: If success, 0 (``OK``) is returned and the given IRQ filter mode is set as the current settings.
    If failed, a negated ``errno`` is returned.

-
 .. _noteram:

 Noteram Device (``/dev/note``)
@@ -174,7 +173,6 @@ Noteram Device (``/dev/note``)
  ``/dev/note`` is the device to get the trace (instrumentation) data.
  The device has read function to get the data and ioctl function to control the buffer mode.

-
 ``/dev/note`` Header Files
 --------------------------

@@ -81,7 +81,6 @@ The first necessary thing to be done in order to use the timer driver in an appl

  #include <nuttx/timers/timer.h>

-
 At an application level, the timer functionalities may be accessed through ``ioctl`` systems calls. The available ``ioctl`` commands are:

 * :c:macro:`TCIOC_START`
@@ -140,8 +139,6 @@ These ``struct timer_ops_s`` keeps pointers to the implementation of each operat
                              FAR uint32_t *maxtimeout);
   };

-
-
 Since  ``ioctl`` system calls expect a file descriptor, before using these commands, it's necessary to open the timer device special file in order to get a file descriptor. The following snippet demonstrates how to do so:

 .. code-block:: c
@@ -296,7 +293,6 @@ This command may be used like so:
      return EXIT_FAILURE;
    }

-
 .. c:macro:: TCIOC_MAXTIMEOUT

 The ``TCIOC_MAXTIMEOUT`` command calls the ``maxtimeout`` operation, which is described below.
@@ -328,6 +324,5 @@ This command may be used like so:

  printf("Maximum supported timeout: %" PRIu32 "\n", max_timeout);

-
 Those snippets were taken from the Example which provides a great resource to demonstrate how to use those ``ioctl`` commands.

@@ -82,7 +82,6 @@ The previously selected example will basically do the following:
 * Ping (feed the dog) during the ``pingtime`` with a delay of ``pingdelay`` and print out the wdt status in case debug was enabled.
 * Enter into an endless loop without pinging. It will cause the watchdog timer to reset the chip on timeout, i.e., after timer expiration.

-
 The `example code <https://github.com/apache/incubator-nuttx-apps/blob/master/examples/watchdog/watchdog_main.c>`_  may be explored, its path is at ``/examples/watchdog/watchdog_main.c`` in the apps' repository.

 In NuttX, the watchdog timer driver is a character driver and when a chip supports multiple watchdog timers, each one is accessible through its respective special file in ``/dev`` directory. Each watchdog timer is registered using a unique numeric identifier (i.e. ``/dev/watchdog0``, ``/dev/watchdog1``, ...).
@@ -108,7 +107,6 @@ The first necessary thing to be done in order to use the watchdog timer driver i

  #include <nuttx/timers/watchdog.h>

-
 At an application level, the watchdog timer functionalities may be accessed through ``ioctl`` systems calls. These ``ioctl`` commands internally call lower-half layer operations and the parameters are forwarded to these operations through the ``ioctl`` system call. The example provides a great resource to demonstrate how to use those ``ioctl`` commands. The available ``ioctl`` commands are:

 .. c:macro:: WDIOC_START
@@ -2,7 +2,6 @@
 SYSLOG
 ======

-
 SYSLOG Interfaces
 =================

@@ -440,7 +440,6 @@ CONFIG_NXFONT_SANS23X27 for examaples:
      NULL
    };

-
 NX Test Coverage
 ================

@@ -716,4 +716,3 @@ Move a rectangular region within the window.

 .. _nx-tool-kit-nxtk-1:

-
@@ -47,4 +47,3 @@ NX Cursor Support (``NXCURSOR``)

  :return: OK on success; ERROR on failure with errno set appropriately.

-
@@ -33,7 +33,6 @@ NXFONTS types
      FAR const uint8_t *bitmap;     /* Pointer to the character bitmap */
    };

-
 .. c:struct:: nx_fontset_s

  This structure describes one contiguous grouping of glyphs that can be
@@ -117,7 +117,6 @@ NXGL Types
                    FAR const struct nxgl_point_s *v1, \
                    FAR const struct nxgl_point_s *v2);

-
 Add two 2x1 vectors and save the result to a third.

 .. c:function:: void nxgl_vectsubtract(FAR struct nxgl_point_s *dest, \
@@ -247,7 +246,6 @@ NXGL Types
 .. c:function:: void nxgl_circletraps(FAR const struct nxgl_point_s *center, nxgl_coord_t radius, \
                     FAR struct nxgl_trapezoid_s *circle);

-
  Given a description of a a circle, return 8 trapezoids
  that can be used to fill the circle by
  :c:func:`nx_fillcircle` and other interfaces.
@@ -436,7 +436,6 @@ these sub-windows to be managed more-or-less independently:
                     FAR const struct nx_callback_s *cb, \
                     FAR void *arg);

-
  Create a tool bar at the top of the specified framed
  window.

@@ -468,7 +467,6 @@ these sub-windows to be managed more-or-less independently:
 .. c:function:: int nxtk_filltoolbar(NXTKWINDOW hfwnd, FAR const struct nxgl_rect_s *rect, \
                     nxgl_mxpixel_t color[CONFIG_NX_NPLANES]);

-
  Fill the specified rectangle in the toolbar sub-window
  with the specified color.

@@ -487,7 +485,6 @@ these sub-windows to be managed more-or-less independently:
                    unsigned int plane, FAR uint8_t *dest, \
                    unsigned int deststride);

-
  Get the raw contents of graphic memory within a
  rectangular region. NOTE: Since raw graphic memory is returned, the
  returned memory content may be the memory of windows above this one and
@@ -530,7 +527,6 @@ these sub-windows to be managed more-or-less independently:
                         nxgl_coord_t width, nxgl_mxpixel_t color[CONFIG_NX_NPLANES], \
                         uint8_t caps);

-
  Fill the specified line in the toolbar sub-window with
  the specified color. This is simply a wrapper that uses
  ``nxgl_splitline()`` to break the line into trapezoids and then calls
@@ -558,7 +554,6 @@ these sub-windows to be managed more-or-less independently:
      #define NX_LINECAP_PT2   0x02  /* Line cap on pt2 on of the vector only */
      #define NX_LINECAP_BOTH  0x03  /* Line cap on both ends of the vector only */

-
  :return: ``OK`` on success; ``ERROR`` on failure with
    ``errno`` set appropriately

@@ -650,4 +645,3 @@ these sub-windows to be managed more-or-less independently:

 .. _nx-fonts-support-nxfonts-1:

-
@@ -27,4 +27,3 @@ Linux/Cygwin-based NuttX simulator. Instructions are provided for
 building that simulation are provided in `Appendix C <#testcoverage>`__
 of this document.

-
@@ -186,7 +186,6 @@ All PM interfaces are declared in the file ``include/nuttx/power/pm.h``.
 Callbacks
 =========

-
 .. c:struct:: pm_callback_s

  This struct includes the pointers to the driver
@@ -920,7 +920,6 @@ conditional compilation does *not* cause any change to the indentation.
    ...
    #endif /* __INCLUDE_SOMEHEADER_H */

-
 Parentheses
 ===========

@@ -1146,7 +1145,6 @@ Parameters and Local Variables
      return ret;
    }

-
 **NOTE:** You will see the local variable named ``ret`` is frequently
 used in the code base for the name of a local variable whose value will
 be returned or to received the returned value from a called function.
@@ -2392,7 +2390,6 @@ Appendix
 C Source File Structure
 =======================

-
 .. code-block:: c

   /****************************************************************************
@@ -2430,7 +2427,6 @@ C Source File Structure

 *All C pre-processor macros are defined here.*

-
 .. code-block:: c

   /****************************************************************************
@@ -28,7 +28,6 @@ Here's how to do it:
   If you don't have a `GitHub <https://www.github.com>`_ account, it's free to
   sign up.

-
 #. Fork the Projects

   Visit both these links and hit the Fork button in the upper right of the page:
@@ -36,7 +35,6 @@ Here's how to do it:
   * `NuttX <https://github.com/apache/incubator-nuttx/>`_
   * `NuttX Apps <https://github.com/apache/incubator-nuttx-apps/>`_

-
 #. Clone the Repositories

   On the GitHub web page for your forked ``incubator-nuttx`` project, copy the clone url – get it by hitting the
@@ -66,7 +64,6 @@ Here's how to do it:
       $ git checkout -b test/my-new-branch
       $ git push

-
 Git Workflow With an Upstream Repository
 ----------------------------------------

@@ -162,7 +159,6 @@ maybe doing that several times. Then when everything works, I get my branch read
       $ git commit my-file.c
       $ git push

-
 Submitting Your Changes to NuttX
 --------------------------------

@@ -143,7 +143,6 @@ modification.
        200aaa90: 0000 0000 0000 0000 0000 0000 0000 0000  ................
        200aaaa0: 0000 0000 0000 0000                      ........

-
 NuttX Drivers as a Reference
 ----------------------------

@@ -190,7 +190,6 @@ called ``/export``.

  # sudo mkdir /export

-
 It is important that ``/export`` directory allow access to everyone (777
 permissions) as we will be accessing the NFS share from the client with
 no authentication.
@@ -280,5 +279,4 @@ And also we can verify if NFS is running in the system with:
       100021   3   tcp   1629  nlockmgr
       100021   4   tcp   1629  nlockmgr

-
 Now your NFS sever is sharing ``/export`` directory to be accessed.
@@ -30,7 +30,6 @@ The following configurations must be enabled.
 - ``CONFIG_SYSTEM_TRACE`` : Enables "``trace``" command
 - ``CONFIG_SYSTEM_SYSTEM`` : Enables "``system``" command (required by :ref:`trace_cmd`)

-
 The following configurations are configurable parameters for trace.

 - ``CONFIG_SCHED_INSTRUMENTATION_FILTER_DEFAULT_MODE``
@@ -81,7 +80,6 @@ Getting the trace

 Trace is started by the following command.

-
 .. code-block::

  nsh> trace start
@@ -98,7 +96,6 @@ If you want to get the trace while executing some command, the following command

  nsh> trace cmd <command> [<args>...]

-
 Displaying the trace result
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

@@ -130,7 +127,6 @@ This will get the trace results like the following:
  <noname>-0   [0]   7.650000000: irq_handler_entry: irq=15
      :

-
 By using the logging function of your terminal software, the trace result can be saved into the host environment and it can be used as the input for `"Trace Compass" <https://www.eclipse.org/tracecompass/>`_.

 If the target has a storage, the trace result can be stored into the file by using the following command.
@@ -140,12 +136,10 @@ It also can be used as the input for "Trace Compass" by transferring the file in

  nsh> trace dump <file name>

-
 To display the trace result by `"Trace Compass" <https://www.eclipse.org/tracecompass/>`_, choose ``File`` -> ``Open Trace`` menu to specify the trace data file name.

 .. image:: image/trace-compass-screenshot.png

-
 Trace command description
 =========================

@@ -197,7 +191,6 @@ To use this command, ``CONFIG_SYSTEM_SYSTEM`` needs to be enabled.

  trace cmd [-c] <command> [<args>...]

-
 - ``-c`` : Continue the previous trace.
  The trace data is not cleared before starting new trace.

@@ -231,7 +224,6 @@ If the task trace is running, it is stopped before the output.
 - ``<filename>`` : Specify the filename to save the trace result.
  If not specified, the trace result is displayed to console.

-
 .. _trace_mode:

 trace mode
@@ -188,8 +188,6 @@ Application Configuration -> NSH LIbrary     .
 .                                            with the usbmon_start and usbmon_stop commands from the NSH console.
 ===========================================  ===================================================

-
-
 ===============================================   ============================================
 Application Configuration -> System NSH Add-Ons   .
 ``CONFIG_USBMONITOR=y`` 	                        Enable the USB monitor daemon
@@ -210,7 +208,6 @@ Application Configuration -> System NSH Add-Ons   .
 ``CONFIG_USBMONITOR_TRACEINTERRUPTS=y``           .
 ===============================================   ============================================

-
 NOTE: If USB debug output is also enabled, both outputs will appear on
 the serial console. However, the debug output will be asynchronous with
 the trace output and, hence, difficult to interpret.
@@ -130,8 +130,6 @@ user using the ZiLOG ZDS-II Windows-native toolchain:
   scripts) and setting ``CONVPATH`` to ``cygpath`` or ``winepath``
   regarding to currently used environment.

-
-
 Other Environments
 ==================

@@ -14,4 +14,3 @@ In the following sections you will find basic information introducing main NuttX
  trademarks.rst
  resources.rst

-
@@ -1,6 +1,5 @@
 .. include:: /substitutions.rst

-
 ===================
 Supported Platforms
 ===================
@@ -72,7 +72,6 @@ Thus if the LED is statically on, NuttX has successfully  booted and is,
 apparently, running normally.  If the LED is flashing at approximately
 2Hz, then a fatal error has been detected and the system has halted.

-
 Buttons
 -------

@@ -112,7 +112,6 @@ There are five user interface switches on the MIMXRT1050 EVK Board:
 Only the user button is available to the software.  It is sensed on the
 WAKEUP pin which will be pulled low when the button is pressed.

-
 J-Link External Debug Probe
 ===========================

@@ -106,7 +106,6 @@ There are five user interface switches on the MIMXRT1050 EVK Board:
 Only the user button is available to the software.  It is sensed on the
 WAKEUP pin which will be pulled low when the button is pressed.

-
 J-Link External Debug Probe
 ===========================

@@ -168,7 +168,6 @@ by starting "fb" in console. The LCD display is connected via SPI4.
 This configuration can be easily changed to work with Teensy 4.0 by
 selecting ``CONFIG_TEENSY_40=y``.

-
 Flash
 =====

@@ -155,7 +155,6 @@ GPIOS (6-9). Regular and high speed GPIO share the same pins (GPIO1 is with GPIO
 therefore IOMUXC_GPR_GPR26-29 registers are used to determine what module is used for the
 GPIO pins.

-
 I2C
 ---

@@ -16,14 +16,12 @@ PolarFire SoC FPGA (MPFS250T-FCVG484EES)
 - SiFive U54 Application cores (4 x RV64GC)
 - and Secure boot

-
 Memory and storage
 ------------------
 - 2 GB LPDDR4 x 32
 - 1 Gb SPI flash
 - 8 GB eMMC flash & SD card slot (multiplexed)

-
 Programming & Debugging
 -----------------------
 Onboard JTAG connector or onboard embedded FlashPro (multiplexed)
@@ -31,7 +29,6 @@ Onboard JTAG connector or onboard embedded FlashPro (multiplexed)
 - UART via micro USB
 - 52 x test points

-
 Interfaces
 ----------

@@ -53,8 +50,6 @@ Sensor
 ------
 - Power sensor (pac1934)

-
-
 Buttons and LEDs
 ================

@@ -63,12 +58,10 @@ Buttons
 There are 3 buttons and reset button.  The Reset button is not available
 to software by default.

-
 LEDs
 ----
 There is 4 user controlled on-board LEDs.

-
 Configurations
 ==============

@@ -5,14 +5,12 @@ Microchip Polarfile (MPFS)
 RV64 64-bit RISC-V multiprocessor-based Microcontroller Subsystem
 (MPFS025T, MPFS095T, MPFS160T, MPFS250T, MPFS460T)

-
 MPFS Toolchain
 ==============

 A generic RISC-V toolchain can be used to build MPFS projects.
 Like: https://xpack.github.io/riscv-none-embed-gcc or https://github.com/sifive/freedom-tools/releases

-
 Booting
 =======

@@ -20,7 +18,6 @@ The NuttX works as a standalone operating system that may initialize all the req
 peripherals including DDR memory. Alternatively, the vendor's HSS bootloader may be used instead to
 perform all the initialization steps.

-
 Building and flashing
 =====================

@@ -49,19 +46,16 @@ Create HSS payload bin::

   hss-payload-generator -v -c hss-nuttx.yml payload.bin

-
 Debugging with OpenOCD
 ======================

 Compatible OpenOCD and configs can be downloaded from:
 https://www.microsemi.com/product-directory/design-tools/4879-softconsole#downloads

-
 OpenOCD can then be used::

   openocd -c "set DEVICE MPFS" --file board/microsemi-riscv.cfg

-
 Peripheral Support
 ==================

@@ -83,8 +77,6 @@ eNVM           No
 USB            No
 ============   =======  =====

-
-
 Supported Boards
 ================

@@ -27,7 +27,6 @@ All you need to do is select your desired board profile configuratioon

    $ make

-
 Running
 =======

@@ -95,7 +95,6 @@ board + LAN8720 module. If users have some issue about using this driver,
 please refer the upper official document, specially the issue that GPIO0
 causes failing to bring the ESP32 chip up.

-
 Pin Mapping
 ===========

@@ -141,7 +141,6 @@ Data / Instruction 0x50000000 0x50001FFF Embedded Memory
 .                  0x50002000 0xFFFFFFFF                 Reserved
 ================== ========== ========== =============== ===============

-
 Embedded Memory
 ---------------

@@ -98,4 +98,3 @@ Naming and Header File Conventions
   in common logic outside of the platform-specific source
   directories.

-
@@ -25,7 +25,6 @@ below:

  :return: Zero (OK) is returned on success; a negated errno value is returned on failure.

-
 .. c:function:: int up_shmdt(uintptr_t vaddr, unsigned int npages)

  Detach, i.e, unmap, on shared memory region from a user virtual address.
@@ -543,7 +543,6 @@ with NuttX tasks.

  :return: ``OK`` or ``ERROR``

-
  **POSIX Compatibility:** This is a NON-POSIX interface. VxWorks
  provides the following comparable interface:

@@ -166,7 +166,6 @@ depend on internal, kernel-space facilities.
 -  ``CONFIG_LIBC_USRWORKSTACKSIZE``. The stack size allocated for
   the lower priority worker thread. Default: 2048.

-
 Common Work Queue Interfaces
 ============================

@@ -173,7 +173,6 @@ Directory Operations (``dirent.h``)

 .. c:function:: int        telldir(FAR DIR *dirp);

-
 UNIX Standard Operations (``unistd.h``)
 ---------------------------------------

@@ -276,7 +276,6 @@ the following paragraphs.
     socket. In this case the process will also receive a SIGPIPE unless
     MSG_NOSIGNAL is set.

-
 .. c:function:: ssize_t recv(int sockfd, void *buf, size_t len, int flags);

  The ``recv()`` call is identical to
@@ -291,7 +290,6 @@ the following paragraphs.

  **Returned Value:** See ```recvfrom()`` <#recvfrom>`__.

-
 .. c:function:: ssize_t recvfrom(int sockfd, void *buf, size_t len, int flags, \
                 struct sockaddr *from, socklen_t *fromlen);

@@ -2,4 +2,3 @@

   <br/>

-
@@ -39,7 +39,6 @@ FAT Long File Names

  So you have been forewarned:  Use the long filename at your own risk!

-
 NXP Restriction for SPIFI code
 ==============================

@@ -987,7 +987,6 @@ The `menuconfig` make target depends on two things:
     the more detailed build instructions in the top-level README.txt
     file of the tools repository at <https://bitbucket.org/nuttx/tools>.

-
     The `make install` step will, by default, install the `kconfig-mconf`
     tool at `/usr/local/bin/mconf`.  Where ever you choose to
     install `kconfig-mconf`, make certain that your PATH variable includes
@@ -11568,7 +11568,6 @@ detailed bugfix information):

    * Atmel SAMA5:

-
    * Atmel SAM3/4 Drivers:

      - Fix some errors in AFEC header file.  From OrbitalFox.
@@ -27370,7 +27369,6 @@ NuttX-9.1.0 Release Notes -------------------------
      See git commit # e83c1400b65c65cbdf59c5abcf2ae368f540faef in the main
      NuttX repository.

-
 NuttX-10.0.0 Release Notes
 ------------------------

@@ -27644,8 +27642,6 @@ of all remaining wdog function calls from. For example, replace a call like `ret
 * [PR-1997](https://github.com/apache/incubator-nuttx/pull/1997) libc: Remove
 all calls to fclose with stdin/stdout/stderr with fclose

-
-
 ## Major Changes to Documentation

 * [PR-1763](https://github.com/apache/incubator-nuttx/pulls/1763) Add
@@ -27785,8 +27781,6 @@ PR-1531 Kinetis K28: Add USB state change notifiers in notifier work queue

 PR-1456 Kinetis K28: Reworked USB driver for setup out data phase

-
-
 #### NRF52

 * [PR-1418](https://github.com/apache/incubator-nuttx/pull/1418) NRF52: Add
@@ -28101,8 +28095,6 @@ both FlexCAN and ENET are used
 * [PR-1452](https://github.com/apache/incubator-nuttx/pull/1452) lcd: Fix
 memory leak when board\_graphics\_setup fail

-
-
 ### New Driver Support

 * [PR-1797](https://github.com/apache/incubator-nuttx/pull/1797) leds: WS2812
@@ -28554,8 +28546,6 @@ want to remove this unnecessary boilerplate.

 In your custom board's `scripts/Make.defs` file, remove lines like these:

-
-
 ARCHCCVERSION = ${shell $(CC) -v 2>&1 | sed -n '/^gcc version/p' | sed -e
 's/^gcc version \\(\[0-9\\.\]\\)/\\1/g' -e 's/\[-\\ \].\*//g' -e '1q'}
 ARCHCCMAJOR = ${shell echo $(ARCHCCVERSION) | cut -d'.' -f1}
@@ -28609,8 +28599,6 @@ CC = $(CROSSDEV)gcc CXX = $(CROSSDEV)g++ CPP = $(CROSSDEV)gcc -E -P -x c LD =
 $(CROSSDEV)ld STRIP = $(CROSSDEV)strip --strip-unneeded AR = $(ARCROSSDEV)ar rcs
 NM = $(ARCROSSDEV)nm OBJCOPY = $(CROSSDEV)objcopy OBJDUMP = $(CROSSDEV)objdump

-
-
 You may want to do one of the following:

 *   If they are redundant to the definitions provided in the included
@@ -49,7 +49,6 @@ directory plus the board-specific configurations in the boards/
 directory.  Each architecture must provide a subdirectory <arch-name>
 under arch/ with the following characteristics:

-
        <arch-name>/
        |-- include/
        |   |--<chip-name>/
@@ -27,7 +27,6 @@

 #ifdef CONFIG_ARCH_FPU

-
 /****************************************************************************
 * Pre-processor Definitions
 ****************************************************************************/
@@ -27,7 +27,6 @@

 #ifdef CONFIG_ARCH_FPU

-
 /****************************************************************************
 * Pre-processor Definitions
 ****************************************************************************/
@@ -112,7 +112,6 @@ else ifeq ($(CONFIG_ARCH_CORTEXM55),y)
  endif
 endif

-
 # NuttX buildroot under Linux or Cygwin

 ifeq ($(CONFIG_ARMV8M_TOOLCHAIN),BUILDROOT)
@@ -214,7 +214,6 @@ config LC823450_SLEEP_MODE
 	bool "sleep mode"
 	default n

-
 config HRT_TIMER
 	bool "High resolution timer"
 	default n
@@ -22,7 +22,6 @@ or dual 10-bit ADC(s), 10-bit DAC, PWM channels and 45 fast GPIO lines with up
 to nine edge or level sensitive external interrupt pins make these microcontrollers
 suitable for industrial control and medical systems.

-
 Features
 ^^^^^^^^

@@ -379,7 +379,6 @@
 #endif
 	.endm

-
 /* Configure the Memory Accelerator Module (MAM) */

 	.macro	configmam, base, val
@@ -122,7 +122,6 @@ Known issues: (carried forward)
 2. Option SPIFI_CAP_SUBBLKERASE is not working.
 3. Device S25FL129P is un-tested.

-
 LPCSpifilib version <0.04>
 ===========================
 Release date <4/25/2014>
@@ -18,7 +18,6 @@
 #
 ############################################################################

-
 CMN_ASRCS  = phy62xx_exception.S phy62xx_start.S arm_saveusercontext.S arm_fullcontextrestore.S
 #CMN_ASRCS += arm_switchcontext.S vfork.S
 CMN_ASRCS += vfork.S
@@ -156,4 +155,3 @@ EXTRA_LIBPATHS += -L$(TOPDIR)/../apps/phy6222/bbb_sdk/components/xiaomi/libs/mes
 EXTRA_LIBS += -lmesh-auth-cortex-m0plus-debug
 endif

-
@@ -156,7 +156,6 @@ exception_common:
 	mov		r10, r4
 	mov		r11, r5

-
 	/* Recover SP (R2), PRIMASK (R3), and R4-R7. Determine the value of
 	 * the stack pointer as it was on entry to the exception handler.
 	 */
@@ -194,7 +193,6 @@ exception_common:
 *
 ****************************************************************************/

-
 	.text
 	.align	2
 	.code	16
@@ -310,7 +308,6 @@ exception_common_inline:
 	mov		r10, r4
 	mov		r11, r5

-
 	/* Recover SP (R2), PRIMASK (R3), and R4-R7. Determine the value of
 	 * the stack pointer as it was on entry to the exception handler.
 	 */
@@ -45,7 +45,6 @@ __start:
 	msr		msp, r1					/* r2>>sp */
 	bl		c_start				/* R0=IRQ, R1=register save area on stack */

-
 	.size	__start, .-__start

 	.end
@@ -813,7 +813,6 @@ config SAMD5E5_USB_REGDEBUG

 endmenu # USB options

-
 if SAMD5E5_GMAC

 menu "GMAC device driver options"
@@ -2503,7 +2503,6 @@ config USART5_RS485_DIR_POLARITY

 endif # STM32F0L0G0_USART5_SERIALDRIVER

-
 choice
 	prompt "USART6 Driver Configuration"
 	default STM32F0L0G0_USART6_SERIALDRIVER
@@ -1222,7 +1222,6 @@ config STM32F7_HAVE_SAI2
 	bool
 	default n

-
 # These "hidden" settings are the OR of individual peripheral selections
 # indicating that the general capability is required.

@@ -138,7 +138,6 @@ config ARCH_CHIP_STM32H753AI
 		STM32 H7 Cortex M7, 2048 Kb FLASH, 1024K Kb SRAM,
 		with cryptographic accelerator, UFBGA169

-
 config ARCH_CHIP_STM32H753BI
 	bool "STM32H753BI"
 	select STM32H7_STM32H7X3XX
@@ -4222,7 +4221,6 @@ config STM32H7_TIM17_CAP
 		Timer devices may be used for different purposes.  One special purpose is
 		to capture input.

-
 menu "STM32 TIMx Outputs Configuration"

 config STM32H7_TIM1_CH1POL
@@ -135,7 +135,6 @@ ifeq ($(CONFIG_STM32H7_PWR),y)
 CHIP_CSRCS += stm32_pwr.c
 endif

-
 ifeq ($(CONFIG_STM32H7_QUADSPI),y)
 CHIP_CSRCS += stm32_qspi.c
 endif
@@ -27,7 +27,6 @@ endchoice
 # These "hidden" settings determine whether a peripheral option is available
 # for the selected MCU

-
 # When there are multiple instances of a device, these "hidden" settings
 # will automatically be selected and will represent the 'OR' of the
 # instances selected.
@@ -136,7 +136,6 @@
 #endif
 	.endm

-
 /****************************************************************************
 * .text
 ****************************************************************************/
@@ -893,7 +893,6 @@ config PIC32MZ_T9_EXTERNALCLOCK
 endmenu
 endif # PIC32MZ_T9

-
 endmenu # Timer Configuration

 menuconfig PIC32MZ_GPIOIRQ
@@ -80,7 +80,6 @@ up_fullcontextrestore:
  l.lwz   r30, 4*REG_R30(r3);
  l.lwz   r31, 4*REG_R31(r3);

-
  /* Get the return value */

  l.lwz   r11, 4*REG_R11(r3);
@@ -78,7 +78,6 @@ config ARCH_RX65N_RSK2MB
 	default n
 	select ARCH_RENESAS_RX

-
 config ARCH_RX65N_GRROSE
 	bool
 	default n
@@ -43,7 +43,6 @@

 __start:

-
  /* Disable all interrupts (i.e. timer, external) in mie */

  csrw mie, zero
@@ -39,7 +39,6 @@ config ARCH_SPARC_V8
 	default n
 	select ARCH_HAVE_STACKCHECK

-
 config ARCH_FAMILY
 	string
 	default "sparc_v8"	if ARCH_SPARC_V8
@@ -13,7 +13,6 @@ config BM3803_WDG
 	default n
 	select WATCHDOG

-
 config BM3803_TIM1
 	bool "Timer 1 (T1)"
 	default n
@@ -67,7 +66,6 @@ config BM3803_GPIOIRQ_PORT7

 endif # BM3803_GPIOIRQ

-
 menu "Timer Configuration"

 if SCHED_TICKLESS
@@ -332,7 +332,6 @@ simple_return:
        ldd     [%o0 + ISF_I2_OFFSET], %i2    ! restore i2, i3
        ldd     [%o0 + ISF_I4_OFFSET], %i4    ! restore i4, i5

-
        ldd     [%o0 + ISF_F0_OFFSET]  ,%f0
        ldd     [%o0 + ISF_F2_OFFSET]  ,%f2
        ldd     [%o0 + ISF_F4_OFFSET]  ,%f4
@@ -26,7 +26,6 @@

 #include <arch/irq.h>

-
 #define RTRAP(_vector, _handler)  mov   %g0, %l0 ; sethi %hi(_handler), %l4 ; jmp %l4+%lo(_handler); mov _vector, %l3
 #define TRAP(_vector, _handler)   mov   %psr, %l0; sethi %hi(_handler), %l4 ; jmp %l4+%lo(_handler); mov _vector, %l3

@@ -370,7 +369,6 @@ zerobss:
        ret
        restore

-
 /*
 * Init END
 */
@@ -421,7 +419,6 @@ _window_overflow:
        jmp  %l1                         ! Re-execute save.
         rett %l2

-
        /*
         *  Window underflow trap handler.
         *
@@ -468,7 +465,6 @@ _window_underflow:
        jmp  %l1                        ! Re-execute restore.
         rett  %l2

-
        /*
         *  Flush All Windows trap handler.
         *
@@ -604,7 +600,6 @@ _fpdis_enable:
        nop
 /*************************************************/

-
 /*************************************************/
 	.data
 	.global _fsrinit, _fpdata, g_idle_topstack
@@ -153,7 +153,6 @@ fix_pil:
        nop;
        nop;

-
 simple_return:
        ldd     [%o0 + ISF_I6_FP_OFFSET], %i6 ! restore i6/fp, i7
        sub     %fp, CONTEXT_CONTROL_INTERRUPT_FRAME_SIZE, %sp
@@ -200,7 +199,6 @@ simple_return:
        ldd     [%o0 + PRE_STACK_FRAME_I6_FP_OFFSET], %l4
        std	    %l4, [%fp + CPU_STACK_FRAME_I6_FP_OFFSET]

-
        ldd     [%o0 + ISF_F0_OFFSET]  ,%f0
        ldd     [%o0 + ISF_F2_OFFSET]  ,%f2
        ldd     [%o0 + ISF_F4_OFFSET]  ,%f4
@@ -26,7 +26,6 @@

 #include <arch/irq.h>

-
 #define RTRAP(_vector, _handler)  mov   %g0, %l0 ; sethi %hi(_handler), %l4 ; jmp %l4+%lo(_handler); mov _vector, %l3
 #define TRAP(_vector, _handler)   mov   %psr, %l0; sethi %hi(_handler), %l4 ; jmp %l4+%lo(_handler); mov _vector, %l3

@@ -370,7 +369,6 @@ zerobss:
        ret
        restore

-
 /*
 * Init END
 */
@@ -421,7 +419,6 @@ _window_overflow:
        jmp  %l1                         ! Re-execute save.
         rett %l2

-
        /*
         *  Window underflow trap handler.
         *
@@ -468,7 +465,6 @@ _window_underflow:
        jmp  %l1                        ! Re-execute restore.
         rett  %l2

-
        /*
         *  Flush All Windows trap handler.
         *
@@ -594,7 +590,6 @@ done_flushing:
        jmpl    %l2, %g0
        rett    %l2 + 4

-
 /* fpdis_enable */
    .global  _fpdis_enable
 _fpdis_enable:
@@ -605,7 +600,6 @@ _fpdis_enable:
        nop
 /*************************************************/

-
 /*************************************************/
 	.data
 	.global _fsrinit, _fpdata, g_idle_topstack
@@ -45,7 +45,6 @@ ifeq ($(filter y, \
  CONFIG_SPARC_TOOLCHAIN ?= LINUXGCC
 endif

-
 # Chip-specific CPU flags

 ifeq ($(CONFIG_ARCH_CHIP_BM3803),y)
@@ -125,7 +125,6 @@ up_saveusercontext:
 	 * if a priority change occurs or not.
 	 */

-
 	leal	4(%esp), %ecx
 	movl	%ecx, (4*REG_SP)(%eax)

@@ -69,5 +69,4 @@ config ARCH_EXCLUDE_MULTIBOOT
 	---help---
 		Some platforms, e.g. jailhouse, do not like to have a multiboot header

-
 endif # ARCH_X86_64
@@ -26,5 +26,3 @@ specific directories.
 broadwell
  This is the implementation of NuttX on the Intel Broadwell processors.

-
-
@@ -135,7 +135,6 @@ loader_gdt_ptr:

    .size	__reset_entry, . - __reset_entry

-
 /****************************************************************************
 * .text
 ****************************************************************************/
@@ -243,7 +242,6 @@ pd_loop:
    or      $X86_CR4_FGSBASE,   %eax
    mov     %eax,   %cr4

-
    // Load a GDT with 64bits mode set
    lgdt    gdt64_ptr

@@ -293,7 +291,6 @@ clear_bss:
    movabs  $g_idle_topstack,    %rbx
    mov     %rbx,   %rsp

-
    /* Initialize and start NuttX */
    call    up_lowsetup                     /* Low-level, pre-OS initialization */

@@ -364,7 +361,6 @@ __enable_sse_avx:

    .size    __enable_sse_avx, . - __enable_sse_avx

-
 /****************************************************************************
 * Name: __enable_pcid
 *
@@ -269,7 +269,6 @@ isr_common:
    leaq -512(%rsp), %rsp
    fxsaveq (%rsp)

-
 	/* The current value of the SP points to the beginning of the state save
 	 * structure.  Save that in RDI as the input parameter to isr_handler.
 	 */
@@ -394,4 +393,3 @@ irq_common:
 	.size	irq_common, . - irq_common
 	.end

-
@@ -107,7 +107,6 @@ config ARCH_CHIP_XTENSA_CUSTOM
 	---help---
 		Select this option if there is no directory for the chip under arch/xtensa/src/.

-
 endchoice # XTENSA chip selection

 config XTENSA_HAVE_ICACHE
@@ -387,7 +387,6 @@ config ESP32S2_UART1
 	select UART1_SERIALDRIVER
 	select ARCH_HAVE_SERIAL_TERMIOS

-
 config ESP32S2_WIRELESS
 	bool "Wireless"
 	default n
@@ -44,7 +44,6 @@
 #  undef CONFIG_Z8_COPYPRAM
 #endif

-
 /**************************************************************************
 * External References / External Definitions
 **************************************************************************/
@@ -26,7 +26,6 @@ HEAD_ASRC = z80_head.asm
 endif
 endif

-
 CMN_CSRCS  = z80_initialize.c z80_allocateheap.c z80_createstack.c
 CMN_CSRCS += z80_releasestack.c z80_interruptcontext.c z80_blocktask.c
 CMN_CSRCS += z80_unblocktask.c z80_exit.c z80_releasepending.c
@@ -230,7 +230,6 @@ config AUDIO_DEV_PATH
 endif
 endif

-
 # These are here as placeholders of what could be added

 if AUDIO_PLANNED
@@ -83,7 +83,6 @@ CONFIG_AUDIO_DEV_PATH
  Available if CONFIG_AUDIO_CUSTOM_DEV_PATH is selected and CONFIG_AUDIO_DEV_ROOT
  is not selected.

-
 Audio Format Support Selections
 -------------------------------

@@ -102,7 +101,6 @@ CONFIG_AUDIO_FORMAT_WMA
 CONFIG_AUDIO_FORMAT_OGG_VORBIS
  Specifies that Ogg Vorbis support should be enabled if available by a lower-half driver.

-
 Audio feature exclusion Selections
 ----------------------------------

@@ -2672,7 +2672,6 @@ config ARCH_IRQBUTTONS

 comment "Board-Specific Options"

-
 if ARCH_BOARD_PCDUINO_A10
 source "boards/arm/a1x/pcduino-a10/Kconfig"
 endif
@@ -61,7 +61,6 @@ The boards/ directory contains board specific configuration logic.  Each
 board must provide a subdirectory <board> under boards/ with the
 following characteristics:

-
  <board>
  |-- README.txt
  |-- include/
@@ -44,7 +44,6 @@ SECTIONS
    . = 0xffc0010C;                 /* advance to .+strlen("etherMAC-->")+1 */
    __EtherMAC = .;

-
    /* The OS entry point is here */

    . = 0x10300000;
@@ -586,7 +586,6 @@ A: Yes with the following modifications to the procedure above.
       gdb> mon reg pc 0x10800040
       gdb> s

-
 Debugging with QEMU
 ================================

@@ -54,7 +54,6 @@ NXFLATLDFLAGS1 = -r -d -warn-common
 NXFLATLDFLAGS2 = $(NXFLATLDFLAGS1) -T$(TOPDIR)$(DELIM)binfmt$(DELIM)libnxflat$(DELIM)gnu-nxflat-pcrel.ld -no-check-sections
 LDNXFLATFLAGS = -e main -s 2048

-
 # ELF module definitions

 CELFFLAGS = $(CFLAGS) -mlong-calls # --target1-abs
@@ -74,6 +74,4 @@ ifeq ($(CONFIG_IMXRT_ENC),y)
 CSRCS += imxrt_enc.c
 endif

-
-
 include $(TOPDIR)/boards/Board.mk
@@ -104,7 +104,6 @@ to the Primary and Secondary Elevator boards in a Tower system. The Primary
 Connector (comprised of sides A and B) is identified by a white strip.
 The Secondary Connector is comprised of sides C and D.

-
 TWR-SER Serial Board Connection
 ===============================

@@ -255,7 +254,6 @@ Networking Support
    3 packets transmitted, 3 received, 0% packet loss, time 2003ms
    rtt min/avg/max/mdev = 2.040/4.789/7.822/2.369 ms

-
  From the target side, you may should also be able to ping the host
  (assuming it's IP is 192.168.0.1):

@@ -378,7 +376,6 @@ Networking Support
      CONFIG_NSH_NETINIT_RETRYMSEC=2000     : Configure the network monitor as you like
      CONFIG_NSH_NETINIT_SIGNO=18

-
 LEDs
 ====

@@ -236,11 +236,9 @@ nsh> ifconfig
 eth0 Link encap:Ethernet HWaddr 00:e0:de:ad:be:ff at UP
     inet addr:192.168.1.244 DRaddr:192.168.1.1 Mask:255.255.255.0

-
 lo   Link encap:Local Loopback at UP
     inet addr:127.0.0.1 DRaddr:127.0.0.1 Mask:255.0.0.0

-
             IPv4   TCP   UDP  ICMP
 Received     0007  0000  0006  0000
 Dropped      0001  0000  0000  0000
@@ -18,7 +18,6 @@
 *
 ****************************************************************************/

-
 MEMORY
 {
  progmem (rx) : ORIGIN = 0x02000e00, LENGTH = 124K
@@ -95,7 +95,6 @@ SECTIONS
        _ebss = ABSOLUTE(.);
    } > SRAM

-
    /* Stabs debugging sections */

    .stab 0 : { *(.stab) }
--- a/Show More
+++ b/Show More
				`@@ -1843,4 +1843,3 @@ Example::`

				``ping6`` differs from ``ping`` in that it uses IPv6 addressing.
				`@@ -716,4 +716,3 @@ Move a rectangular region within the window.`

				`.. _nx-tool-kit-nxtk-1:`
				@@ -47,4 +47,3 @@ NX Cursor Support (``NXCURSOR``)

				`:return: OK on success; ERROR on failure with errno set appropriately.`