public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Allow console input to be disabled
Date: Thu, 07 Aug 2008 08:43:35 -0400	[thread overview]
Message-ID: <489AEDF7.9000400@ge.com> (raw)
In-Reply-To: <m2myjp10ht.fsf@ohwell.denx.de>

Detlev Zundel wrote:
> Hi Haavard,
> 
>> Mark Jackson <mpfj@mimc.co.uk> wrote:
>>> Added CONFIG_SILENT_CONSOLE_INPUT define.
>>>
>>> When used (in conjunction with CONFIG_SILENT_CONSOLE) it disables all console input.
>> Does anyone have an opinion about this? I think it's a nice thing to
>> have.
> 
> Hm, defining this and then "setenv silent=1;saveenv;reset" and we have
> lost any chance to access u-boot command line?  This looks pretty
> dangerous to me, so I do not particularly like it.
> 
> What is the original motivation to skip the input?
> 
> Cheers
>   Detlev

Dual-use of a serial port: Mark originally asked about dynamically 
inhibiting u-boot's use of the serial port for normal use, but allowing 
u-boot to use it for development/debug, selected by a jumper:
   <http://article.gmane.org/gmane.comp.boot-loaders.u-boot/44640>
Hardware starved software development. :-/

For completeness, the gmane thread for the patch is here:
   <http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/44788>

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 
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 ;-).

Best regards,
gvb

  reply	other threads:[~2008-08-07 12:43 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 [this message]
2008-08-09 23:16       ` Wolfgang Denk
2008-08-10 17:45         ` Mark Jackson
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=489AEDF7.9000400@ge.com \
    --to=gerald.vanbaren@ge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox