From: Wolfgang Denk Date: Fri, 12 Sep 2008 11:08:51 +0200 Subject: [U-Boot] ctrl-c detection (on 4xx platforms) In-Reply-To: <200809120955.10866.matthias.fuchs@esd-electronics.com> References: <200809111723.54133.matthias.fuchs@esd-electronics.com> <20080911205543.4E25C248B8@gemini.denx.de> <200809120900.56200.matthias.fuchs@esd-electronics.com> <200809120955.10866.matthias.fuchs@esd-electronics.com> Message-ID: <20080912090851.4A20424926@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Matthias Fuchs, In message <200809120955.10866.matthias.fuchs@esd-electronics.com> you wrote: > > when I disable CONFIG_AUTOBOOT_KEYED ctrl-c checking is not disabled. I think there is one "dis" ot "not" too many. > We are using CONFIG_AUTOBOOT_KEYED to have a special key (SPACE) to > abort autoboot and not the 'any' key. I thought so. > Is there any special reason why ctrl-c checking is disabled for CONFIG_AUTOBOOT_KEYED? Excellent question. Next question, please. I think the rationale behind this is to prevent users from getting an interactive prompt by just pressing ^C - the intention of CONFIG_AUTOBOOT_KEYED is similar to a login with password - without the correct password you are denied access to an interactive inter- face. But if you could use ^C as soon as the bootcmd has started - what should happen next? We cannot simply drop you into the interactive shell? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de When the ax entered the forest, the trees said, "The handle is one of us!" -- Turkish proverb