Changes between Version 1 and Version 2 of Developer/Removing_a_Port


Ignore:
Timestamp:
Nov 3, 2015, 12:10:22 AM (4 years ago)
Author:
Joel Sherrill
Comment:

Add first steps

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Removing_a_Port

    v1 v2  
    33[[TOC(Developer/Removing_a_Port , depth=2)]]
    44
     5This page describes the process of removing an architectural port from the RTEMS source repository. This is normally a fairly infrequent occurrence and happens after some combination of the following:
     6
     7* the architecture is no longer available for purchase
     8* GCC has dropped support for the architecture
     9* there are no RTEMS users
     10* the port is incomplete and tools are unstable
     11
     12Before an architecture can be removed, an announcement must be made to the community in order to allow for feedback that it can be removed or is still in use. In some cases, still being in use is not a sufficient condition if current tool versions do not support the architecture and users have no plans to upgrade to a newer RTEMS version.
     13
     14In these instructions, it is assumed that '''ALL''' BSPs for this architecture have been removed. Each BSP should be removed per the procedures in [wiki:Developer/Removing_a_BSP Removing a BSP].
     15
     16== Removing an Architecture from the Source ==
     17
     18Unlike the instructions for [wiki:Developer/Removing_a_BSP Removing a BSP], these instructions assume the reader is familiar with RTEMS Developer Practices and provides a checklist as opposed to detailed instructions. An important facet of removing an architecture is that it will require changes to multiple areas of the RTEMS Project spread across multiple repositories. This makes it more complicated and the developer removing the architecture should be careful, use grep, and update this page as other areas to update are identified:
     19
     20* File a Trac ticket - This should list all tickets associated with removing BSPs within this architecture. All commit messages associated with removing the architecture should reference this ticket number. See [https://devel.rtems.org/ticket/2443 ticket 2443] for a simple example.
     21
     22* bootstrap -c - From the top of the RTEMS source tree.
     23
     24* Make a local development branch in git
     25
     26* Remove cpukit/score/cpu/@ARCHITECTURE@ - Commit as a single patch updating ticket.
     27
     28* Remove @ARCHITECTURE@ from cpukit/libnetworking - If the architecture has optimized in_cksum code, then this will require editing the files machine/in_cksum.h, netinet/in_cksum.c, and Makefile.am. There may also be files referencing the architecture which need updating. Commit as a single patch updating ticket.
     29
     30* Remove c/src/lib/libcpu/@ARCHITECTURE@ - Commit as a single patch updating ticket.
     31
     32* Remove c/src/lib/libbsp/@ARCHITECTURE@ including shared - Commit as a single patch updating ticket.
     33
     34* Remove @ARCHITECTURE@ from doc/cpu_supplement - This requires removing a file and updating the top level cpu_supplement.t file. There may also be examples using the architecture. Commit as a single patch updating ticket.
     35
     36* Remove @ARCHITECTURE@ from doc/user/preface.texi - This requires a manual edit. Commit as a single patch updating ticket.
     37
     38XXX tables, RPC, promotional material, architecture table in wiki