RTEMS monitor commands and the shell

Thomas Dörfler thomas.doerfler at embedded-brains.de
Fri Mar 16 07:39:45 UTC 2018


just my two cents: Would an additional call 'rtems_shell_init_once_commandset()' make sense, where the user can specify, which comamnds are available? 

I agree that changing the functionality of an existing call is not a good idea.


----- Ursprüngliche Mail -----
Von: "Chris Johns" <chrisj at rtems.org>
An: "Development" <devel at rtems.org>
Gesendet: Freitag, 16. März 2018 08:01:14
Betreff: RTEMS monitor commands and the shell


The monitor commands are registered automatically in `rtems_shell_init_once()`
which means an application has no control over these being present, the command
mix and naming, for example there is a `config` command in the monitor.

I am not sure what to do, if it is removed some applications may break assuming
these commands are present. A way to disable the command using shellconfig.h
would be nice.


devel mailing list
devel at rtems.org
embedded brains GmbH
Thomas Doerfler
Dornierstr. 4
D-82178 Puchheim
email: Thomas.Doerfler at embedded-brains.de
Phone: +49-89-18 94 741-12
Fax:   +49-89-18 94 741-09
PGP: Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

More information about the devel mailing list