From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Tue, 20 Nov 2012 18:20:27 -0600 Subject: [U-Boot] [PATCH 1/8] mx28evk: Configure CONFIG_BOOTDELAY to one second In-Reply-To: <201211210115.25694.marex@denx.de> (from marex@denx.de on Tue Nov 20 18:15:25 2012) References: <1353078550-574-1-git-send-email-festevam@gmail.com> <201211200052.07676.marex@denx.de> <1353452422.2863.10@snotra> <201211210115.25694.marex@denx.de> Message-ID: <1353457227.2863.12@snotra> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 11/20/2012 06:15:25 PM, Marek Vasut wrote: > Dear Scott Wood, > > > On 11/19/2012 05:52:07 PM, Marek Vasut wrote: > > > Dear Stefano Babic, > > > > > > > On 16/11/2012 16:09, Fabio Estevam wrote: > > > > > From: Fabio Estevam > > > > > > > > > > One second is enough time for users to react in case they > want to > > > > > > stop > > > > > > > > the booting process. > > > > > > > > > > Signed-off-by: Fabio Estevam > > > > > --- > > > > > > > > > > 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? > > > > What configuration subset would be applicable to every "fsl" target, > > including i.MX, mpc83xx, mpc85xx, mpc5xxx, m68k, etc? > > That's up to you to think about ... anyway, move it to a separate > thread please. I think the answer to that question is "nothing" -- and you can change the thread title at any time you wish; I'm not going to go create some unrelated thread to respond to a point that you raised in this thread. -Scott