From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Disable command at runtime
Date: Fri, 29 Jul 2016 10:59:40 -0400 [thread overview]
Message-ID: <20160729145940.GP17970@bill-the-cat> (raw)
In-Reply-To: <232d6d3e-c07a-09ee-d0d1-00bea9f7e1b2@elnico.cz>
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'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"
> and unlock it once I need, e.g. in case of some troubles.
>
> So any suggestions which would really answer my question, please?
It wouldn't be two variants, but two defconfigs. But, no, we do support
locking things down such that we only boot verified images. We don't
have any sort of lock/unlock or disable/enable of certain commands at
the prompt. You would be better served by having an emergency
self-contained kernel + ramdisk to deal with troubles rather than being
in U-Boot, most likely.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160729/c88e2639/attachment.sig>
next prev parent reply other threads:[~2016-07-29 14:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 11:40 [U-Boot] Disable command at runtime kubiznak.petr
2016-07-29 13:31 ` Tom Rini
2016-07-29 14:37 ` Petr Kubizňák
2016-07-29 14:59 ` Tom Rini [this message]
2016-07-29 15:57 ` Petr Kubizňák
2016-08-01 20:05 ` Wolfgang Denk
2016-08-02 6:57 ` Petr Kubizňák
2016-08-03 12:53 ` Wolfgang Denk
2016-08-01 20:38 ` Ladislav Michl
2016-08-02 7:11 ` Petr Kubizňák
2016-08-09 18:20 ` Simon Glass
2016-08-10 5:54 ` Petr Kubizňák
2016-08-01 19:59 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160729145940.GP17970@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.