From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/8] mx28evk: Configure CONFIG_BOOTDELAY to one second
Date: Tue, 20 Nov 2012 16:44:19 +0100 [thread overview]
Message-ID: <50ABA553.8020303@denx.de> (raw)
In-Reply-To: <201211200052.07676.marex@denx.de>
On 20/11/2012 00:52, Marek Vasut wrote:
> Dear Stefano Babic,
>
>> On 16/11/2012 16:09, Fabio Estevam wrote:
>>> From: Fabio Estevam <fabio.estevam@freescale.com>
>>>
>>> One second is enough time for users to react in case they want to stop
>>> the booting process.
>>>
>>> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
>>> ---
>>>
>>> include/configs/mx28evk.h | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/include/configs/mx28evk.h b/include/configs/mx28evk.h
>>> index 2916c71..8b89b25 100644
>>> --- a/include/configs/mx28evk.h
>>> +++ b/include/configs/mx28evk.h
>>> @@ -238,7 +238,7 @@
>>>
>>> */
>>>
>>> #define CONFIG_CMDLINE_TAG
>>> #define CONFIG_SETUP_MEMORY_TAGS
>>>
>>> -#define CONFIG_BOOTDELAY 3
>>> +#define CONFIG_BOOTDELAY 1
>>>
>>> #define CONFIG_BOOTFILE "uImage"
>>> #define CONFIG_LOADADDR 0x42000000
>>> #define CONFIG_SYS_LOAD_ADDR CONFIG_LOADADDR
>>
>> Applied (whole series) to u-boot-imx, thanks.
>
> What about making some generic ... config-mx28.h AND config-fsl.h ... and
> including those in board-specific configs?
Any clean-up is welcome. Then maybe (and this is not related to i.MX
only) we could have a cpu-config, a vendor config and on the top a board
config.
#include <cpu-config.h>
#include <vendor-config.h>
#include <board-config.h>
The main problem is that an exception can breaks our castle, and we are
constrained to add #undef in board configuration file.
Best regards,
Stefano
--
=====================================================================
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
=====================================================================
next prev parent reply other threads:[~2012-11-20 15:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 15:09 [U-Boot] [PATCH 1/8] mx28evk: Configure CONFIG_BOOTDELAY to one second Fabio Estevam
2012-11-16 15:09 ` [U-Boot] [PATCH 2/8] mx53loco: " Fabio Estevam
2012-11-16 15:09 ` [U-Boot] [PATCH 3/8] mx6qsabrelite: " Fabio Estevam
2012-11-19 3:28 ` Liu Hui-R64343
2012-11-16 15:09 ` [U-Boot] [PATCH 4/8] mx6qsabre_common: " Fabio Estevam
2012-11-19 3:28 ` Liu Hui-R64343
2012-11-16 15:09 ` [U-Boot] [PATCH 5/8] mx51evk: " Fabio Estevam
2012-11-16 15:09 ` [U-Boot] [PATCH 6/8] mx25pdk: " Fabio Estevam
2012-11-16 15:09 ` [U-Boot] [PATCH 7/8] mx31pdk: " Fabio Estevam
2012-11-16 15:09 ` [U-Boot] [PATCH 8/8] mx35pdk: " Fabio Estevam
2012-11-19 7:51 ` [U-Boot] [PATCH 1/8] mx28evk: " Stefano Babic
2012-11-19 23:52 ` Marek Vasut
2012-11-20 15:44 ` Stefano Babic [this message]
2012-11-20 17:50 ` Otavio Salvador
2012-11-20 18:09 ` Marek Vasut
2012-11-20 18:19 ` Otavio Salvador
2012-11-20 18:43 ` Marek Vasut
2012-11-20 23:00 ` Scott Wood
2012-11-21 0:15 ` Marek Vasut
2012-11-21 0:20 ` Scott Wood
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=50ABA553.8020303@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox