From: Mark Jackson <mpfj@mimc.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Allow console input to be disabled
Date: Sun, 10 Aug 2008 18:45:59 +0100 [thread overview]
Message-ID: <489F2957.9090701@mimc.co.uk> (raw)
In-Reply-To: <20080809231636.2EB1E24885@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Jerry Van Baren,
>
> In message <489AEDF7.9000400@ge.com> you wrote:
>> For what it is worth, I'm with Haavard - it seems useful. WRT the
>> dangerous part - it's intended use is for debug, so presumably it will
>
> It may be intended for debug, but it's available there without warning
> for the end user.
Is there some "warning" mechanism I should use ?
>> be the developer that locks himself out of the console and will have the
>> tools to break back in. From that POV, it isn't any more dangerous than
>> all the other ways a user/developer can brick a board (starting with
>> erasing flash ;-).
>
> I think this one is a bit nastier. It's like this rope hanging out of
> a black box labeled "silencer". The label doesn't mention that it
> goes "KABOOOOM!" first, before there is a big silence (and a cloud of
> dust and a pile of debris).
I agree that it could all go very wrong, but it was a quick and easy way for me to implement that particular feature.
Does anyone have any suggestions on how to achieve the same outcome in a less "hoist by your own petard" way ?
Mark
next prev parent reply other threads:[~2008-08-10 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 12:17 [U-Boot-Users] [PATCH] Allow console input to be disabled Mark Jackson
2008-08-07 10:27 ` Haavard Skinnemoen
2008-08-07 12:19 ` Detlev Zundel
2008-08-07 12:43 ` Jerry Van Baren
2008-08-09 23:16 ` Wolfgang Denk
2008-08-10 17:45 ` Mark Jackson [this message]
2008-08-11 7:25 ` Haavard Skinnemoen
2008-08-11 8:28 ` Wolfgang Denk
2008-08-11 8:36 ` Wolfgang Denk
2008-08-11 11:19 ` Haavard Skinnemoen
2008-08-11 12:19 ` [U-Boot] " Wolfgang Denk
2008-08-11 12:31 ` Haavard Skinnemoen
2008-08-11 12:53 ` Mark Jackson
2008-08-11 13:13 ` Haavard Skinnemoen
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=489F2957.9090701@mimc.co.uk \
--to=mpfj@mimc.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox