From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3EVM: Increase bootargs string length.
Date: Thu, 17 Dec 2009 15:26:18 +0100 [thread overview]
Message-ID: <4B2A3F8A.6040105@googlemail.com> (raw)
In-Reply-To: <1261056567-5214-1-git-send-email-srk@ti.com>
On 17.12.2009 14:29, Sriramakrishnan wrote:
> Increase the bootargs string length as multiple options
> (especially for Video settings) are passed to the kernel
> through bootargs. Also increase the number of args.
>
> Signed-off-by: Sriramakrishnan<srk@ti.com>
> ---
> include/configs/omap3_evm.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/configs/omap3_evm.h b/include/configs/omap3_evm.h
> index a5514ae..fe7b0e2 100644
> --- a/include/configs/omap3_evm.h
> +++ b/include/configs/omap3_evm.h
> @@ -200,11 +200,11 @@
> #define CONFIG_SYS_HUSH_PARSER /* use "hush" command parser */
> #define CONFIG_SYS_PROMPT_HUSH_PS2 "> "
> #define CONFIG_SYS_PROMPT V_PROMPT
> -#define CONFIG_SYS_CBSIZE 256 /* Console I/O Buffer Size */
> +#define CONFIG_SYS_CBSIZE 512 /* Console I/O Buffer Size */
> /* Print Buffer Size */
> #define CONFIG_SYS_PBSIZE (CONFIG_SYS_CBSIZE + \
> sizeof(CONFIG_SYS_PROMPT) + 16)
> -#define CONFIG_SYS_MAXARGS 16 /* max number of command */
> +#define CONFIG_SYS_MAXARGS 32 /* max number of command */
> /* args */
> /* Boot Argument Buffer Size */
> #define CONFIG_SYS_BARGSIZE (CONFIG_SYS_CBSIZE)
Should we do this for some more OMAP3 boards, too? E.g. Overo and
Beagle? Or for all OMAP3 boards?
Best regards
Dirk
next prev parent reply other threads:[~2009-12-17 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 13:29 [U-Boot] [PATCH] OMAP3EVM: Increase bootargs string length Sriramakrishnan
2009-12-17 14:26 ` Dirk Behme [this message]
2009-12-17 14:48 ` Govindarajan, Sriramakrishnan
2009-12-17 15:55 ` [U-Boot] RFC common omap3 subconfig ? was " Tom
2009-12-17 15:58 ` Premi, Sanjeev
2009-12-17 16:07 ` Dirk Behme
2009-12-17 16:36 ` Stefan Roese
2009-12-17 18:23 ` Heiko Schocher
2009-12-18 8:43 ` Stefan Roese
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=4B2A3F8A.6040105@googlemail.com \
--to=dirk.behme@googlemail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.