From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marek.vasut@gmail.com>
Date: Wed, 25 Jan 2012 22:28:17 +0100
Subject: [U-Boot] [PATCH 11/14] New config variable CONFIG_PREMONITOR
In-Reply-To: <5554871.WFipvrCe7b@pali>
References: <1327415291-13260-1-git-send-email-pali.rohar@gmail.com>
	<201201252151.38615.marek.vasut@gmail.com>
	<5554871.WFipvrCe7b@pali>
Message-ID: <201201252228.17208.marek.vasut@gmail.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

> On Wednesday 25 January 2012 21:51:38 Marek Vasut wrote:
> > > On Wednesday 25 January 2012 19:12:51 Marek Vasut wrote:
> > > > >  * if defined run env "premonitor" before Main Loop for Monitor
> > > > >  Processing
> > > > 
> > > > What is this good for?
> > > 
> > > before running monitor loop I'd like write some info to console
> > > (specific board info, board commands, board macros). but if these info
> > > will be written in preboot it can be deleted by menu section.
> > 
> > The "menu" here, you refer to the thing you implemented? So fix that
> > instead of introducing broken code and a pile of workarounds.
> 
> With "menu" I mean env menucmd. U-Boot run command stored in env menucmd
> after preboot and before monitor loop. For example in menucmd can be my
> bootmenu, but there are no problems - no broken code! My bootmenu clear
> screan and show menu, so anything printed before menu entries will be
> deleted. This is not bug - Also in Grub or LILO is debug/output log
> cleaned when showing menu entries.

Ok anyway, but you implemented custom menu system anyway ... so let's clear this 
first, is common/menu.c useless for your application?

M