All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Scott <hashcode0f@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: tegra: increase buffer size and sys args num
Date: Fri, 24 Oct 2014 11:45:31 -0700	[thread overview]
Message-ID: <1414176331-16951-1-git-send-email-hashcode0f@gmail.com> (raw)

From: Bryan Wu <pengw@nvidia.com>

Tegra kernel booting needs a long bootargs command line.

Default value of CONFIG_SYS_CBSIZE is too small to printf out the
long command line and will cause system panic.

Default value of CONFIG_SYS_MAXARGS is too small to setenv bootargs
as the long command line, then kernel won't boot without the complete
bootargs.

Increase this 2 config options solve this problem.

Signed-off-by: Bryan Wu <pengw@nvidia.com>
Signed-off-by: Michael Scott <hashcode0f@gmail.com>
Cc: Tom Warren <twarren@nvidia.com>
Cc: Stephen Warren <swarren@nvidia.com>
Cc: Bryan Wu <pengw@nvidia.com>
---
 include/configs/tegra-common.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/configs/tegra-common.h b/include/configs/tegra-common.h
index 5d2b12a..a6d7bf1 100644
--- a/include/configs/tegra-common.h
+++ b/include/configs/tegra-common.h
@@ -107,11 +107,11 @@
  * Increasing the size of the IO buffer as default nfsargs size is more
  *  than 256 and so it is not possible to edit it
  */
-#define CONFIG_SYS_CBSIZE		(256 * 2) /* Console I/O Buffer Size */
+#define CONFIG_SYS_CBSIZE		(1024 * 2) /* 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 args */
+#define CONFIG_SYS_MAXARGS		64	/* max number of command args */
 /* Boot Argument Buffer Size */
 #define CONFIG_SYS_BARGSIZE		(CONFIG_SYS_CBSIZE)
 
-- 
1.9.1

                 reply	other threads:[~2014-10-24 18:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1414176331-16951-1-git-send-email-hashcode0f@gmail.com \
    --to=hashcode0f@gmail.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.