Dear Pali =?ISO-8859-1?Q?Roh=E1r?=,
In message <1886523.MLHYlDJPrM@pali> you wrote:
>
> I need to run some script before monitor code but after menucmd.
> And preboot is called before bootdelay and also before menucmd.
> So I added premonitor which is called before monitor, but after
> bootdel
On Saturday 28 April 2012 22:39:51 Wolfgang Denk wrote:
> Dear =?UTF-8?q?Pali Rohár?=,
>
> In message <1335634011-9104-11-git-send-email-
pali.ro...@gmail.com> you wrote:
> > * if defined run env "premonitor" before Main Loop for
> > Monitor Processing
> What would be the difference compared to "
Dear =?UTF-8?q?Pali=20Roh=C3=A1r?=,
In message <1335634011-9104-11-git-send-email-pali.ro...@gmail.com> you wrote:
> * if defined run env "premonitor" before Main Loop for Monitor Processing
What would be the difference compared to "preboot" ?
Best regards,
Wolfgang Denk
--
DENX Software Eng
* if defined run env "premonitor" before Main Loop for Monitor Processing
Signed-off-by: Pali Rohár
---
Changes since v1:
- use run_command instead run_command2
Changes since original version:
- removed #ifdef CONFIG_PREMONITOR in main.c
common/env_common.c |3 +++
common/main.c
4 matches
Mail list logo