ChangeLog

ChangeLog
=========

2014-09-01:  Removed support for 8051 from main source tree.

  REASON: There are three:
  1. The older 8051 architecture has a hardware stack and required special
     case handling throughout the OS.  With a current focus on supporting
     true processes, the limitations of the 8051 architecture are becoming
     obstacles to the advancement of the design.
  2. The port was at one time functional, but never worked reliably.  It
     would occasionally exceed the limited 8051 stack size.  It is possible,
     however, that this problem could be fixed with additional tuning.
  3. The 8051 is basically a bad architecture for multi-tasking.  Since
     the 8051 has a hardware stack, the entire stack has to be copied on
     contex switches.
  4. I do not thing that anyone has ever used the port and because of bit
     rot, it is not even certain that it is still function.

  NEW HOME:
    Obsoleted/nuttx/configs/8051 and Obsoleted/nuttx/configs/pjrc-8051

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-8051-2014-9-1.patch

2014-09-05:  Removed support for the 16z board from the main source tree.

  REASON:
    The port is not yet ready for use.  It may return to the NuttX source
    tree at some point in the future.

  NEW HOME:
    Obsoleted/nuttx/configs/16z

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-16z-2014-9-5.patch

2014-11-10:  Removed support for the stm32f100rc_generic board configuration

  REASON
    This support was obsoleted because of a decision to stop support of
    generic board configurations. Generic board configurations do not
    provide support for any specific hardware but can be useful only if
    there are not other examples for the setup for a particular
    architecture.

  NEW HOME:
   Obsoleted/nuttx/configs/stm32f100rc_generic

  REMOVAL PATCH
    Obsoleted/Patches/Remove-stm32f100rc_generic-2014-11-10.patch

2015-01-14: Removed support for the px4fmu-v2_upstream board configuration

  REASON
    This is not the official configuration for the PX4 board and has led
    to confusion by NuttX users.  The board configuration also requires
    some ongoing maintenance and customization to support ongoing PX4
    testing and evaluation.  It is best retained the PX4 repositories
    where it can be properly maintained and not in the upstream NuttX
    repository.

  NEW HOME
    Obsoleted/nuttx/configs/px4fmu-v2_upstream

  REMOVAL PATCH
    Obsoleted/Patches/Remove-stm32f100rc_generic-2014-11-10.patch

2015-04-13: Remove fragmentary support for the Intel Galileo bord.

  REASON
    That port is not going to happen (I don't even have the Galileo
    board anymore).

  NEW HOME
    Obsoleted/nuttx/configs/galileo

  REMOVAL PATCH
     Obsoleted/Patches/Remove-Galileo-2015-04-13.patch

2016-01-27: Remove apps/system/ramtron

  REASON
    First, this is an inappropriate application because it uses
    purely internal, operating system interfaces.  It was really
    a part of the OS board support in the wrong location.

    But then the SPI internal interfaces changed so that it is
    now (correctly) impossible to support such an application.
    Basically, the up_spiinitialize() internal interface is
    gone.

  NEW HOME
    None..  See the Removal Patch.

  REMOVAL PATCH
    Obsoleted/Patches/Remove-appsramtron-2016-01-27.patch

2016-03-29: Remove nuttx/configs/vsn

  REASON
    This configuration is not being maintained and does things in
    ways that are not now considered standard.  I doubt that the
    VSN boards are even still available.  Thus, the configuration
    is both useless and a maintenance problem for me.

  NEW HOME
    Obsoleted/nuttx/configs/vsn

  REMOVAL PATH
    Obsoleted/Patches/Remove-vsn-config-2016-03-29.patch

2016-03-29: Remove apps/system/sdcard

  REASON
    This applicatin violates the POSIX OS/Application interface by
    calling directly into the OS internal functions.

  NEW HOME
    Obsoleted/apps/system/sdcard

  REMOVAL PATCH
    Obsoleted/Patches/Remove-apps-sdcard-2016-03-29.patch

2016-04-12: Remove nuttx/configs/nucleus2g

  REASON
    Removed the Nucleus2G configuration because there has not been any
    activity with the commercial board in a few years and it no longer
    appears to be available from the 2g-eng.com website.  Since the board
    is commercial and no longer publically available, it no longer qualifies
    for inclusion in the open source repositories.

  NEW HOME
    Obsoleted/nuttx/nuttx/configs/nucleus2g

  REMOVAL PATCH
    Obsoleted/Patches/Remove-configs-nucleus2g-2016-04-12.patch.

2016-06-03: Remove apps/system/flash_eraseall

  REASON
    This tool is useful, but violates the OS/application interface.  This
    can be replaced with an MDIOC_BULKERASE IOCTL call on any MTD-based
    driver instance.

    NOTE: apps/system/flash_eraseall was subsequently replaced in a slightly
    different form and so could probably be removed from the Obsoleted
    repository.

  NEW HOME
    Obsoleted/apps/system/flash_eraseall

  REMOVAL PATCH
    Obsoleted/Patches/Remove-appsflasherasall-2016-06-02.patch

2016-06-03:  Remove nuttx/drivers/mtd/flash_eraseall.c

  REASON
    This has never been used within the OS and is simply a wrapper around
    the MDIOC_BULKERASE IOCTL command.  It used to be called (only) from
    apps/system/flash_eraseall, but that has been also removed because it
    violated the OS/applicatin interface -- by calling flash_eraseall().

  NEW HOME
    Obsoleted/nuttx/drivers/mtd/flash_eraseall.c

  REMOVAL PATCH
    Obsoleted/Patches/Remove-mtdflasheraseall-2016-06-03.patch

2016-12-02:  Remove RGMP

  REASON
    I don't believe anyone has ever used the RGMP code in the NuttX
    repository.  The RGMP project has the last working NuttX code and
    that project has not been updated in several years.  It appears to
    be abandoned.  Keep this untested, abandoned code in the NuttX
    repository is a maintenance problem.

  NEW HOME:
    Obsoleted/nuttx/arch/rgmp
    Obsoleted/nuttx/drivers/net/e1000.c, e1000.h, vnet.c
    Obsoleted/nuttx/configs/rgmp
    Obsoleted/arch/examples/rgmp

  REMOVAL PATCHES:
    Obsoleted/Patches/Remove-RGMP-2016-12-02.patch
    Obsoleted/Patches/Remove-RGMP-Example-2016-12-02.patch

2016-12-13:  Remove Calypso architecture and support for all Calypso boards

  REASON
    This was a good idea that never caught on.  I had hoped that NuttX
    would create some interest and the port would mature.  But never
    happened.  It was a very incomplete, very low effort port that never
    developed.  Now those only Calypso platforms are obsolete so there
    is no point keeping this around

  NEW HOME:
    Obsoleted/nuttx/arch/arm/include/calypso
    Obsoleted/nuttx/arch/arm/src/calypso
    Obsoleted/nuttx/configs/compal_e86
    Obsoleted/nuttx/configs/compal_e88
    Obsoleted/nuttx/configs/compal_e99
    Obsoleted/nuttx/configs/pirelli-dpl10
    Obsoleted/nuttx/drivers/sercomm
    Obsoleted/nuttx/include/nuttx/sercomm

  REMOVAL PATCHES:
    Obsoleted/Patches/Remove-Calypso-arch-2016-12-13.patch
    Obsoleted/Patches/Remove-Calypso-configs-2016-12-13.patch

2017-03-09:  Remove apps/examples/usbterm

  REASON
    This kind of a silly little terminal example and, under certain
    configurations, it will make illegal calls into the OS (calling
    usbterm_dev_init()).  Perhaps I am being hasty;? perhaps it would
    have been bettern to just eliminate the call to usbterm_dev_init()?

  NEW HOME:
    Obsoleted/apps/examples/usbterm

  REMOVAL PATCH
    Obsoleted/Patches/Remove-usbterm-2017-03-09.patch

2017-07-01: Remove apps/examples/thttpd netstat example.

  REASON:
    Removed the netstats demo.  That demo depended on an illegal function
    call to netdev_foreach() and cannot be supported.  That example could
    have been replaced with logic that uses the procfs network entries as
    was done for NSH which had the same issue.  But I am too lazy to
    implement that.

  NEW HOME:
    Obsoleted/apps/examples/thttd/content/netstats

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-THTTPD-netstats-2017-07-01.patch

2017-07-04: Remove apps/examples/keypadtest and nuttx/include/nuttx/input/keypad.h

  REASON:
    The keypad.h head file descibes a global function that was used years
    ago (I think by the Calypso architecture).  It is not longer valid.

    The keypadtest was just a bad clone of apps/examples/hidkbd for a keypad
    driver that was removed years ago.  It also uses illegal function calls
    into the OS.  So it has no purpse:  It is redundant, it uses illegal
    interfaces, and is a test for non-existent code.

  NEW HOME:
    Obsoleted/apps/examples/keypadtest
    Obsoleted/nuttx/include/nuttx/input/keypad.h

   REMOVAL PATCH:
     Obsoleted/Patches/Remove-appskeypadtest-2017-07-04.patch

2017-10-14:  Remove apps/examples/lcdrw

  REASON:
    This was an ad hoc test that I wrote to verify some LCD hardware.  It,
    however, is not of general use and it violates the portable POSIX OS
    interface.  It must be removed for the second reason.

  NEW HOME:
    Obsoleted/apps/examples/lcdrw

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-appsexampleslcdrw-2017-10-14.patch

2017-10-14:  Remove Single User Graphics mode

  REASON:
    Although this mode is lighter weight the the multi-user graphics mode
    with its NX server, teh single user graphics mode logic violates the
    portable POSIX OS interface and, hence, cannot be supported because it
    is not on the NuttX roadmap.

  NEW HOME:
    Obsoleted/nuttx/graphics/nxsu

  REMOVAL PATCHES:
    Obsoleted/Patches/Remove-apps-singleuser-graphics-2017-10-14.patch
    Obsoleted/Patches/Remove-nuttx-singleuser-graphics-2017-10-14.patch
    Obsoleted/Patches/Remove-nxwidgets-singleuser-graphics-2017-10-24.patch

2017-10-28:  Remove Crystal LAN Network Driver

  REASON:
    I started this a long time ago and never finished it.  I no longer even
    have hardware with Crystal LAN parts nor to I expect to ever have such
    hardware in the future.

  NEW HOME:
    Obsoleted/nuttx/drivers/net/cs89x0.c
    Obsoleted/nuttx/drivers/net/cs89x0.h
    Obsoleted/nuttx/include/nuttx/net/cs89x0.h

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-driversnet-cs89x0-2017-10-28.patch

2017-10-28:  Remove MX1ADS Board Support

  REASON:
    That board port is unfinished and I know longer have the hardware to
    complete the port (nor it is likely that I will get another MX1ADS in
    the future).

  NEW HOME:
    Obsoleted/nuttx/configs/mx1ads

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-configs-mx1ads-2017-10-28.patch

2017-10-28:  Remove apps/examples/ltdc.

  REASON:
    Remove apps/examples/ltdc.  This configuration has been deleted because
    it violated the portable POSIX OS interface.  It used apps/examples/ltdc
    and include ltdc.h and dma2d.h which were also removed for the same
    reason.

    arch/arm/include/stm32 and stm32f7:  Remove ltdc.h and dma2d.h.  Those
    header files in that location permitted inclusion into application space
    logic and, hence, facilitated and encouraged calling into the OS and
    violating the portable POSIX OS interface.  The definitions in those
    header files were move the appropriate location in the counterpart,
    architecture specific files at arch/arm/src/stm32 and stm32f7 dma2d.h
    and ltdc.h.

    configs/stm32f429i-disco/ltdc:  This configuration has been deleted
    because it used apps/examples/ltdc which was removed for the same reason.

  NEW HOME:
    Obsoleted/apps/examples/ltdc
    Obsoleted//nuttx/configs/stm32f429i-disco/ltdc

  REMOVAL PATCHES:
    Obsoleted/Patches/Remove-appsexamplesltdc-2017-11-06.patch
    Obsoleted/Patches/Remove-nuttxltdcdma2d-2017-11-06.patch

2017-11-13:  Remove apps/system/free

  REASON:
    Removed because it called directly into the OS to obtain information
    about FLASH usage, violating the portable POSIX OS interface.  This
    capability will, enventually, be replaced and a procfs entry.

  NEW HOME:
    Obsoleted/apps/system/free

  REMOVAL PATCHES:
    None

2017-11-16: Remove configs/stm32f429i-disco/ide and configs/stm3220g-eval/ide

  REASON:
    The stm32f429i-disco/ide is part of the LTDC configuration that was
    removed on 2017-10-28.  I just missed this directory at the time.

    I decided to remove all of the IAR/uVision IDE support for the STM32's.
    These have not been updated for years and I am sure cannot be used in
    their current form.  I cannot maintain them and there is no one else
    maintaining them so they need to go.

   NEW HOME:
    Obsoleted/nuttx/configs/stm32f429i-disco/ide
    Obsoleted/nuttx/configs/stm3220g-eval/ide
    Obsoleted/nuttx/configs/stm3220g-eval/scripts/stm32f207xG.icf

   REMOVAL PATCHES:
    Obsoleted/Patches/Remove-stm3220g-eval-ide-2017-11-16.patch

2017-11-24:  Remove configs/xtrs

  REASON:
    Removed the XTRS configuration This was an unverified port of NuttX
    to a TRS-80 simulator.  It was removed because (1) it is, as I said,
    unverified as well as unsupported, and (2) the TRS-80 simulation is
    a sub-optimal platform.  That platform includes a 16-bit ROM image
    and only a 48Kb RAM space.

  NEW HOME:
    Obsoleted/nuttx/configs/xtrs

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-configs-xtrs-2017-11-24.patch

2018-03-22:  Remove apps/canutils/libuavcan, apps/examples/uacan, and
    board configurations that use them.

  REASON:
    Remove apps/canutils/libuavcan, apps/examples/uavcan and nuttx
    configurations that use them.  libuavcan has not built for a year or
    so.  The basic problem is that as NuttX advances, the old frozen
    version of libuavcan has become obsolete because it violates the
    portable POSIX OS interface.  No one is maintaining the port so
    there is no alternative but to remove it.

  NEW HOME:
    Obsoleted/apps/canutils/libuavcan
    Obsoleted/apps/examples/uavcan
    Obsoleted/nuttx/configs/nucleo-f404re/uavcan
    Obsoleted/nuttx/configs/stm32f4discovery/uavcan

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-appscanutilsuavcan-2018-03-23.patch
    Obsoleted/Patches/Remove-configs-uavcan-2017-03-23.patch

2018-04-04:  Remove CC3000 support and Spark support

  REASON
    Alan Carvalho de Assis and Sebastien Lorquet objected to the
    implementation of CC3000.  To my knowledge, there was no technical
    reason to remove this support, but I cowed to the demands and
    accepted the patch to remove this support.

    The preferred way to support CC3000 would be via the USRSOCK socket
    interface.

    Spark board support was also removed.  Without CC3000 support there
    no reason support the Spark either.  It would be just a crappy
    STM32F103CBT board with no peripherals other than USB.

  NEW HOME:
    Obsoleted/apps/examples/cc3000
    Obsoleted/nuttx/configs/spark
    Obsoleted/nuttx/drivers/wireless/cc3000
    Obsoleted/nuttx/include/nuttx/wireless/cc3000

  REMOVAL PATCHES:
    Obsoleted/Patches/Remove-CC3000-configs-2018-04-04.patch
    Obsoleted/Patches/Remove-CC3000-drivers-2018-04-04.patch
    Obsoleted/Patches/Remove-CC3000-fixups-2018-04-04.patch
    Obsoleted/Patches/Remove-Spark-configs-2018-04-04.patch

2018-04-09:  Remove support for the CC3200 and the CC3200-Launchpad

  REASON:
    This was a port that was started but never completed.  What
    good is dated, partial CC3200-Launchpad board support with
    no wireless support?

  NEW HOME:
    Obsoleted/nuttx/configs/cc3200-launchpad

    NOTE: That covers only removal of the board supported. See the
    removal patch below for the removed architectural support.

  REMOVAL PATCHES:
    Obsoleted/Patches/Remove-configs-cc3200-launchpad-2018-94-09.patch
    Obsoleted/Patches/Remove-tiva-early-board-init-2018-12-04.patch

2018-05-19:  Remove support for the Nokia6100 LCD as was implemented
  in the Olimex-LPC1766STK configuration.

  REASON:
    That LCD uses a 9-bit SPI interface on the Olimex board (the 9th bit
    being the command/data bit that is normally a discrete).  That
    communication was never successfully integrated.  I now believe that
    it would would require some special support from the low-level,
    MCU SPI driver to manage that 9th bit.

  NEW HOME:
    Obsoleted/nuttx/configs/olimex-lpc1766stk/src/lpc17_lcd.c
    Obsoleted/nuttx/configs/olimex-lpc1766stk/nx/defconfig
    Obsoleted/nuttx/drivers/lcd/nokia6100.c
    Obsoleted/nuttx/include/lcd/nokia6100.h

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-configs-lcd-nokia6100-2018-05-19.patch

2018-05-24:  Remove support for the Indium-F7 Boards

  REASON:
    Support for the Indium-F7 board was removed for two reasons:  (1) The
    board support was just clone of the Nucleo-144 board support with
    naming changes.  There has been no support and no further development
    for the board support.  (2) There does not seem to be any available
    Indium-F7 board available to the public anywhere on the Internet.
    There is not even a reference to the board on the rafresearch.com web
    site.  Gotta go.  Its in the way.

  NEW HOME:
    Obsoleted/nuttx/configs/indium-f7

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-configs-indium-f7-2018-05-24.patch

2018-06-18:  Remove apps/interpreters/micropython.

  REASON:
    There are several reasons for the removal of micropython.  (1) the
    current version 1.3.8 is very old and no one is supporting it.  (2) the
    port only includes the core micropython logic and none of the Python
    libraries.  As such it is useless in any real application.  (3) There
    have recently been compile failures reported.  It looks like this is due
    to changes in newlib based toolchains that now bring in incompatible
    newlib header files.  See issue 104 at
    https://bitbucket.org/nuttx/nuttx/issues/104/build-micropython-138-error.
    With no one dedicated to the support of micropython, it can no longer be
    carried in the NuttX apps/ repository.

  NEW HOME:
    Obsoleted/apps/interpreters/micropython

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-appsinterpretersmicropython-2018-06-18.patch

  NOTE:  There are some kluges to get a clean micropython compilation
  here: https://bitbucket.org/nuttx/nuttx/issues/108/fix-micropython-138-compile.
  The root cause of the micropython build isses are due to the fact that
  the build brings in non-compatible newlib header files.  The changes of
  that issues are, however, not acceptable for incorporation upstream.

  Update:  People are still using micropython in older NuttX versions that
  still have it.  This is purported to be a build fix (but for an unrelated
  issue`

  Before:
    .built: $(MICROPYTHON_UNPACKNAME) $(OBJ)
    $(call ARCHIVE, $(BIN), $(OBJ))
    @touch $@

  After:
    .built: $(MICROPYTHON_UNPACKNAME) $(OBJ)
    $(call ARCHIVE, -t $(BIN), $(OBJ))
    @touch $@

2018-07-11:  Remove the KX224, BH1749nuc and BH1790glc Drivers

  REASON:
    This removes the KX224, BH1749nuc and BH1790glc.  These are very nicely
    written drivers, but they are based on some external sequencer logic
    which is not available to everyone.  Hence, these are inapropriate to
    carry in the NuttX repository.

  NEW HOME:
    Obsoleted/nuttx/drivers/sensors/
    Obsoleted/nuttx/include/sensors/

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-driverssensors-bh1749-bh1790-kx224.-20180711.patch

2018-09-05:  Remove apps/netutils/ping

  REASON:
    This is an old IPv4/IPv6 PING implementation.  That functionality has been
    replaced with apps/system/ping and apps/system/ping6.  The only thing lost
    here is that the netutils/ping was C-callable.  The system/ping[6] is an
    application.

  NEW HOME
    Obsoleted/apps/netutils/ping

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-appsnetutilsping-2018-09-05.patch

2018-10-17:  Remove configs/pcblogic-pic32mx

  REASON:
    I do not find any references to PCB Logic on the web and I do not believe
    that this breakout board is available any longer.

  NEW HOME:
    Obsoleted/nuttx/configs/pcblogic-pic32mx

  REMOVAL PATCH:
    Patches/Remove-configs-pcblogic-pic32mx-2018-10-17.patch

2018-10-19:  Remove apps/system/progmem

  REASON:
    The program system utility violates the portable POSIX OS interface and
    must be removed.

  NEW HOME:
    Obsoleted/apps/system/progmem

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-apps-system-progmem-2018-10-19.patch

2019-01-02:  Remove Raspberry Pi Zero

  REASON:
    The Raspberry Pi Zero support was started with the best of intentions,
    but was never finished.  Since there is no apparent interest in the
    board port, It was decided to obsolete the unfinished board port to keep
    the main repository clearn.  Support for the BCM2708/2835 was also
    removed.  That CPU support was very minimal, completely untested and
    relevant only to the Raspberry Pi.

  NEW HOME:
    Obsoleted/nuttx/configs/pizero
    Obsoleted/nuttx/arch/arm/src/bcm2708
    Obsoleted/nuttx/arch/arm/include/bcm2708

  REMOVAL PATCHES:
    Obsoleted/Patches/Remove-configs-pizero-2019-01-02.patch
    Obsoleted/Patches/Remove-arch-bcm2708-2019-01-02.patch

2019-01-02:  Remove Support for the LPC11 Architecture in General and for
   the LPCXpresso-LPC1115 in Particular

  REASON:
    Support for the LPCXpresso-LPC1115 and for the LPC1115 architecture in
    general was removed after NuttX-7.30. The LPC11 port was never really
    used (to my knowledge) and was no longer supported.

  NEW HOME
    Obsoleted/nuttx/configs/lpcxpresso-lpc1115
    Obsoleted/nuttx/arch/arm/src/lpc11xx
    Obsoleted/nuttx/arch/arm/include/lpc11xx

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-lpc11xx-2018-07-11.patch

2019-08-22:  Removed the Entire nonbsd Repository

  REASON:
    The repository contained old, never used GPL code.  It is being remove
    because it is of no value and because this eliminates the appearance
    that there is GPL code that code come into NuttX.

  NEW HOME:
    Obsoleted/nonbsd

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-drivers-usbhost-rtl8187-hooks.patch

2019-10-26:  Remove mtp Branch

  REASON:
    The mtp branch contained some WIP implementation of an MTP USB device.
    That work was done by Alan Carvalho de Assis.  That branch became
    corrupted and Alan was no longer able to work on the driver (at least
    for the time being).  The essense of the mtp branch was extracted and
    saved as a patch here in the event that Alan (or someone else) picks
    up that effort in the future.

  NEW HOME:
    (See REMOVAL PATCH)

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-mtp-branch-2019-10-26.patch

2019-11-21:  Remove Support for Pascal Runtime P-Code

  REASON:
    The ancient Pascal compiler that I wrote many years ago is never used
    and not relevant to a modern RTOS.

  NEW HOME:
    Obsoleted/apps/examples/pashello/
    Obsoleted/apps/interpreters/pcode/
    Obsoleted/apps/system/prun/
    Obsoleted/nuttx/binfmt/libpcode/
    Obsoleted/nuttx/binfmt/pcode.c
    Obsoleted/nuttx/boards/sim/sim/sim/configs/pashello/
    Obsoleted/nuttx/boards/z16/z16f2811/z16f2800100zcog/
    Obsoleted/nuttx/boards/z80/z80/z80sim/configs/pashello/
    Obsoleted/nuttx/include/nuttx/binfmt/pcode.h
    Obsoleted/nuttx/include/nuttx/poff.h

  REMOVAL PATCHES:
    Obsoleted/Patches/Remove-apps-Pascal-2019-11-21.patch
    Obsoleted/Patches/Remove-nuttx-Pascal-2019-11-21.patch

2019-11-25:  Remove Suduko Game

  REASON:
    This is a likttle Suduko game that I wrote years ago.  It does not
    belong in a professional, open source RTOS.
 
  NEW HOME:
    Obsoleted/apps/system/sudoku

  REMOVAL PATCH:
    Obsoluted/Patches/Remove-apps-system-suduko-191125.patch

2019-11-25:  Remove Traveler Game

  REASON:
    Traveler was a 3-D FPS game that I wrote years ago (pre Direct-X).
    While a fun probject a couple of decades ago, it has does not
    belong in a professiona, open source RTOS.

  NEW HOME:
    Obsoleted/apps/graphics/traveler

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-nuttx-sim-traveler-191125.patch
    Obsoleted/Patches/Remove-appgs-graphics-traveler-191125.patch

2019-12-09:  Remove tools/mkimage.sh

   REASON:
     Remove support for generation of RRLOAD binary files.  The RRLOAD
     binary format was used with Linux BSPs from www.ridgerun.com circa
     2000-2001.  It is still need by the the c5471 board if that
     bootloader is used.  Removes the CONFIG_RRLOAD_BINARY option and
     tools/mkimage.sh

     This change was motivated by the presence of the mkimage.sh file
     under tools.  That is the tool that created the RRLOAD binary
     format.  That bash script has a GPL license and, hence, may not
     be included in an Apache-licensed project.

  NEW HOME:
     Still available in the tools/ repository

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-nuttx-tools-mkimage-2019-12-09.patch

2020-04-24:  Remove the Obsolete ChangeLog files

  REASON:
    We do not intend to update the ChangeLog file for releases past 8.2. It
    used to be a stepping stone between the 'git log' and the ReleaseNotes.
    However, it no longer serves that purpose. In fact it has no purpose at
    all; all of the change history is in the 'git log'. That is where people
    look for historical information, not in the obsolete ChangeLog.

  NEW HOME:
    Obsoleted/nuttx/ChangeLog
    Obsoleted/apps/ChangeLog.txt

  REMOVAL PATCH:
    N/A

2020-04-24:  Remove tools/logparser.c

  REASON:
    Remove tools/logparser.c.  This tool converted 'git log' output into the
    format used by the obsoleted ChangeLog files.  Since the ChangeLog files
    are obsoleted, the tool servers no purpose.

  NEW HOME:
    Obsoleted/nuttx/tools/logparser.c

  REMOVAL PATCH:
    Obsoleted/Patches/Remove-tools-logparser-2020-04-24.patchA