Remove the double blank line from source files

Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
2026-06-04 14:53:47 +08:00 · 2022-02-20 17:18:01 +08: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.
@@ -6,7 +6,6 @@ Detailed Platform Support
 information see the *README* files that can be found
 `here <https://cwiki.apache.org/confluence/display/NUTTX/README+Files>`__.

-
 Linux User Mode Simulation
 ==========================

@@ -96,7 +95,6 @@ Support for the NXP LPC315x
 family has been incorporated into the code base as of NuttX-6.4. Support
 was added for the Embedded Artists EA3152 board in NuttX-6.11.

-
 Other ARMv4
 ===========

@@ -108,7 +106,6 @@ RS-232/422/485 serial device servers was contributed by Anton D.
 Kachalov in NuttX-7.11. This port includes :ref:`NSH <nsh>`
 configuration with support for the Faraday FTMAC100 Ethernet MAC Driver.

-
 ARM1176JZ
 =========

@@ -129,8 +126,6 @@ The incomplete port along with all support for the BCM2708 was removed
 from the repository with the NuttX-7.28 release but can still be be
 found in the *Obsoleted* repository.

-
-
 ARM Cortex-A5
 =============

@@ -146,7 +141,6 @@ Microchip SAMA5D2
  Giant Board board. This board features the Microchip SAMA5D27C-D1G.
  See http://groboards.com/giant-board.

-
 Microchip SAMA5D3
 -----------------

@@ -291,7 +285,6 @@ native toolchain, or 4) Native Windows. All testing has been performed
 with the CodeSourcery toolchain (GCC version 4.7.3) in the Cygwin
 environment under Windows.

-
 ARM Cortex-A8
 =============

@@ -367,8 +360,6 @@ The basic port has been completed for the following i.MX6 board:
   `README <https://github.com/apache/incubator-nuttx/blob/master/boards/arm/imx6/sabre-6quad/README.txt>`__
   file for the board.

-
-
 ARM Cortex-R4
 =============

@@ -386,8 +377,6 @@ Architecture support for the TMS570LS3137ZWT
 part was added in NuttX 7.25 by Ivan Ucherdzhiev. Ivan also added
 support for the TI Hercules TMS570LS31x USB Kit.

-
-
 ARM Cortex-M0/M0+
 =================

@@ -772,7 +761,6 @@ to two different STM32 L0 boards in the repository:
   `README <https://github.com/apache/incubator-nuttx/blob/master/boards/arm/stm32f0l0g0/nucleo-g070rb/README.txt>`__
   file for further information.

-
 **STATUS:** Status for the STM32F0xx, STM32L0xx, and STM32G0xx is shown
 together since these parts share many drivers in common.

@@ -1273,8 +1261,6 @@ SPI0-based SD card.

 ` <#>`__ (ARM Cortex-M3)

-
-
 ARM Cortex-M4
 =============

@@ -1382,7 +1368,6 @@ Refer to the NuttX board
 `README <https://github.com/apache/incubator-nuttx/blob/master/boards/arm/kinetis/twr-k64f120m/README.txt>`__
 file for further information.

-
 **Driver Status**.

 -  **NuttX-6.8**. Ethernet and SD card (SDHC) drivers also exist: The
@@ -1406,7 +1391,6 @@ contributed by David Sidrane in NuttX 7.20. Refer to the NuttX board
 `README <https://github.com/apache/incubator-nuttx/blob/master/boards/arm/kinetis/freedom-k66f/README.txt>`__
 file for further information.

-
 **Driver Status**.

 -  Most K6x drivers are compatible with the K66.
@@ -2063,7 +2047,6 @@ LPC4337-WS development board featuring the NXP LPC4337JBD144 MCU.
   Alexander Vasiljev. Alexander also contributed an LPC43xx AES driver
   available in NuttX-7.16.

-
 **Driver Status**.

 -  **NuttX-6.20** Several drivers have been copied from the related
@@ -2119,7 +2102,6 @@ graphics configurations (nxwm, fb, and lvgl).
 **LPC4508**. The port was verified on an LPC5408 by a NuttX user with
 relevant changes incorporated in NuttX-7.26.

-
 **Driver Status**.

 -  **NuttX-7.24** The initial release for the LPC54xx in NuttX included
@@ -2364,8 +2346,6 @@ provided by the NuttX
 `buildroot <https://bitbucket.org/nuttx/buildroot/downloads/>`__
 package.

-
-
 ARM Cortex-M7
 =============

@@ -2594,7 +2574,6 @@ for one board from this family:

   This port is still a work in progress.

-
 **NuttX-7.30**. Added support for Ethernet, SDMMC, and Timer drivers.
 All from Jukka Laitinen.

@@ -2677,8 +2656,6 @@ recommended for the Cortex-M7 as for the Cortex-M4. It would be wise to
 use the latest GNU toolchains for this part because as of this writing
 (2015-02-09), support for the Cortex-M7 is a very new GCC feature.

-
-
 Microchip AVR
 =============

@@ -2785,7 +2762,6 @@ NuttX board
 `README <https://github.com/apache/incubator-nuttx/blob/master/boards/avr/at32uc3/avr32dev1/README.txt>`__
 file for further information.

-
 Misoc
 =====

@@ -2799,8 +2775,6 @@ Ramtin Amin in NuttX 7.29.
 Timer, and Ethernet. "Board" support is a available for developing with
 Misoc LM32 under Qemu or on your custom FPGA.

-
-
 OpenRISC mor1kx
 ===============

@@ -2823,8 +2797,6 @@ NuttX `buildroot <https://bitbucket.org/nuttx/buildroot/downloads/>`__
 provides a properly patched GCC 3.4.4 toolchain that is highly optimized
 for the m9s12x family.

-
-
 Intel 80x86
 ===========

@@ -2856,8 +2828,6 @@ This kernel with ostest have been tested with
 -  Qemu/KVM on a Xeon 2630v4 machine.
 -  Bochs with broadwell_ult emulation.

-
-
 Microchip PIC32MX
 =================

@@ -2917,7 +2887,6 @@ PIC32MX795F512L. There one two board ports using this chip:
 #. The MIPS SDE toolchain available from the `Mentor
   Graphics <http://www.mentor.com>`__ website.

-
 Microchip PIC32MZEC
 -------------------

@@ -2983,7 +2952,6 @@ Renesas/Hitachi SuperH
 Board (SH1_LCEVB1), US7032EVB, with a GNU ELF toolchain\* under Linux or
 Cygwin.

-
 Renesas M16C/26
 ---------------

@@ -3017,8 +2985,6 @@ release:
 -  **NuttX-8.2**
 -  **NuttX-9.0** RTC driver for the RX65N was added.

-
-
 RISC-V
 ======

@@ -3035,7 +3001,6 @@ LiteX on ARTY A7
 Support for the Digilent ARTY_A7 board along with CPU VexRiscV SOC were
 added in NuttX-9.0.

-
 ESP32 (Dual Xtensa LX6)
 =======================

@@ -3079,7 +3044,6 @@ driver was added in NuttX-7.2. Refer to the NuttX board
 `README <https://github.com/apache/incubator-nuttx/blob/master/boards/z16/z16f/z16f2800100zcog/README.txt>`__
 file for further information.

-
 Zilog eZ80 Acclaim!
 ===================

@@ -3150,8 +3114,6 @@ this port is verified on hardware. Refer to the NuttX board
 `README <https://github.com/apache/incubator-nuttx/blob/master/boards/z80/z180/p112/README.txt>`__
 file for further information.

-
-
 Zilog Z80
 =========

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

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