[RTEMS Project] #4150: Delete or fix shell command fdt (rtems-fdt.c is untested and not in user documentation) (was: Delete or fix shell command fdt (rtems-fdt.c is dead code))

[RTEMS trac]

#4150: Delete or fix shell command fdt (rtems-fdt.c is untested and not in user
documentation)
----------------------------+-------------------------
 Reporter:  Frank Kuehndel  |       Owner:  (none)
     Type:  enhancement     |      Status:  assigned
 Priority:  low             |   Milestone:  Indefinite
Component:  shell           |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  shell, fdt      |  Blocked By:
 Blocking:                  |
----------------------------+-------------------------

Comment (by Joel Sherrill):

 Calling this dead code is inappropriate. At best it is deactivated code
 which has the bug of not having a configuration option and documentation.

 RTEMS provides functionality which may be used by applications. Sometimes
 we have functionality which has no tests or user documentation. That is
 usually an oversight we should have caught when it was merged. This does
 not make it dead.

 Using this logic for dead code, one could delete a lot of driver code
 (e.g. can, spacewire, 1553, gpio) and network code because there is no
 direct test in RTEMS of that.

 We should be very careful using terms like dead code which have very
 specific meanings in the context of safety certification standards. See
 https://de.mathworks.com/products/polyspace/dead-code-coverage.html for a
 decent discussion which cites the DO-178 definition.

 The bug here is missing documentation and configuration option.

--
Ticket URL: <http://devel.rtems.org/ticket/4150#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project