From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
Date: Fri, 12 Sep 2008 09:00:56 +0200
Subject: [U-Boot] ctrl-c detection (on 4xx platforms)
In-Reply-To: <20080911205543.4E25C248B8@gemini.denx.de>
References: <200809111723.54133.matthias.fuchs@esd-electronics.com>
	<20080911205543.4E25C248B8@gemini.denx.de>
Message-ID: <200809120900.56200.matthias.fuchs@esd-electronics.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Wolfgang,

yes I do have CONFIG_AUTOBOOT_KEYED enabled. It's the PMC440 board:

include/configs/PMC440.h:
...
#define CONFIG_AUTOBOOT_KEYED	1
#define CONFIG_AUTOBOOT_PROMPT	\
	"Press SPACE to abort autoboot in %d seconds\n", bootdelay
#undef CONFIG_AUTOBOOT_DELAY_STR
#define CONFIG_AUTOBOOT_STOP_STR " "
...

Matthias


On Thursday 11 September 2008 22:55, Wolfgang Denk wrote:
> Dear Matthias Fuchs,
> 
> In message <200809111723.54133.matthias.fuchs@esd-electronics.com> you wrote:
> > 
> > I noticed some strange CTRL-C behavior in a BSP command. 
> > When I run my bsp command interactively everything is fine.
> ...
> > But when I call this bsp command as bootcmd CTRL-C does not stop the while loop. So CTRL-C 
> > is not detected. Any idea?
> 
> Do you happen to have CONFIG_AUTOBOOT_KEYED set in your board
> configuration?
> 
> Best regards,
> 
> Wolfgang Denk
>