Re: [U-Boot] Disable command at runtime

Hi Tom, thanks for your reply. Such way is of course possible, but you surely know I'm rather interested in more clever solutions. Besides the understandable fact that I don't want to maintain two u-boot variants and flash it twice, I also believe it can be useful to lock "almost everything" a

Re: [U-Boot] Disable command at runtime

mode, some commands would be disabled. Logic would be similar to CONFIG_OVERWRITE_ETHADDR_ONCE. On 07/29/2016 04:59 PM, Tom Rini wrote: On Fri, Jul 29, 2016 at 04:37:31PM +0200, Petr Kubizňák wrote: Hi Tom, thanks for your reply. Such way is of course possible, but you surely know I

Re: [U-Boot] Disable command at runtime

Dear ladis, Thanks for your comment, I didn't really know about the standalone applications mechanism, it might surely be useful. Best Regards, Petr On 08/01/2016 10:38 PM, Ladislav Michl wrote: You can still download U-Boot standalone application implementing whatever you need to do in pro

Re: [U-Boot] Disable command at runtime

Dear Wolfgang, On 08/01/2016 10:05 PM, Wolfgang Denk wrote: How could that ever be "safe" - in the sense of protecting against an attacker? How could you perform such a "switch" between modes? By setting some bit somewhere. And it has to be in some persistent storage. And the source code of

Re: [U-Boot] Disable command at runtime

Hi Simon, Also see cli_process_fdt() which allows you to lock out commands using a device-tree setting. This avoids changing the U-Boot binary - it is easy enough to update the device tree using fdtput. This is how Chrome OS did it. Hmm, interesting approach. Thanks for your suggestion. Petr _