All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] bootstopkey  reason behind it
Date: Fri, 02 Aug 2013 13:35:04 +0200	[thread overview]
Message-ID: <51FB9968.2080907@denx.de> (raw)
In-Reply-To: <D5A6F3355F664C40AFB65BB1277D8D450193B22639@MAAX7MCDC101.APAC.DELL.COM>

On 02/08/2013 07:58, Paavaanan_T_N at Dell.com wrote:
> Hi,
> 
> To stop autoboot we have 2 ifdef  (CONFIG_AUTOBOOT_STOP_ [STR2 ||
> STR1] ). Which is very easy and straightforward to implement. Halting
> a boot with single "Keystroke" is having its own advantages to the
> user. But, why multiple key support is ignored say like [ctrl +
> anykey ] combination. Especially, BIOS vendors prefer at least
> simultaneous pressing of 2 or more keys to halt the boot. Any
> specific reasons to avoid this. Other than simplicity is there any
> specific reason to stick on this.
> 
> I mean why  simultaneous two key press support is avoided and
> implemented  a secondary bootstopkey to halt the boot say like
> CONFIG_AUTOBOOT_STOP_STR2.

But does not the keyboard send a single key code ? Maybe it is enough
you put in CONFIG_AUTOBOOT_STOP_STR1 the keycode of your CTRL+key.

Best regards,
Stefano Babic



-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

  reply	other threads:[~2013-08-02 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  5:58 [U-Boot] bootstopkey reason behind it Paavaanan_T_N at Dell.com
2013-08-02 11:35 ` Stefano Babic [this message]
2013-08-02 11:41   ` Paavaanan_T_N at Dell.com
2013-08-02 11:50     ` Heiko Schocher
2013-08-02 14:08       ` Paavaanan_T_N at Dell.com
2013-08-04 20:21 ` 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=51FB9968.2080907@denx.de \
    --to=sbabic@denx.de \
    --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.