> On Nov 30, 2020, at 18:07 , Gedare Bloom <ged...@rtems.org> wrote: > > Aren't nearly all shell commands at least a bit unsafe? And we don't > have a lot of commands that have to be explicitly turned on if > CONFIGURE_SHELL_COMMANDS_ALL is already set. I found only networking > commands. > > That seems accurate, you can go ahead with the approach you took then. It > seems to be mostly consistent with the state of practice. > >
I was surprised at the need to enable each command instead of adding all I2C commands with a single enable. I don't think code overhead is an issue. If you're testing I2C from the shell I'm not sure when it's important to have only e.g. i2cget but not i2cset. Peter ----------------- Peter Dufault HD Associates, Inc. Software and System Engineering This email is delivered through the public internet using protocols subject to interception and tampering.
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
