From: Tom Warren <TWarren@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM: tegra: jetson-tk1: Increase console buffer size
Date: Thu, 1 Sep 2016 22:42:40 +0000 [thread overview]
Message-ID: <ebbfff7e8b2545b684925aaa1ef910f7@HQMAIL103.nvidia.com> (raw)
In-Reply-To: <80e858d4-a14c-2d08-0934-f26a2a2a7cd8@wwwdotorg.org>
Peter,
It appears that this got rolled into 'ARM: tegra: increase console buffer size and sys args num', so I'm going to mark it as Superseded in my Patchwork queue.
What's the status of the 'increase console buffer size and sys args num' patch? I've currently got it marked as 'Changes Requested'.
Thanks,
Tom
--
nvpublic
> -----Original Message-----
> From: Stephen Warren [mailto:swarren at wwwdotorg.org]
> Sent: Monday, August 22, 2016 4:11 PM
> To: Peter Chubb <Peter.Chubb@data61.csiro.au>
> Cc: u-boot at lists.denx.de; Stephen Warren <swarren@nvidia.com>; Tom
> Warren <TWarren@nvidia.com>
> Subject: Re: [U-Boot] ARM: tegra: jetson-tk1: Increase console buffer size
>
> On 08/22/2016 04:46 PM, Peter Chubb wrote:
> >
> > U-Boot's console buffer size needs to be bigger to allow the default
> > image on NVIDIA's Linux4Tegra to boot.
> >
> > Otherwise one sees:
> > bootarg overflow 602+0+0+1 > 512
> > on the console, and the board refuses to boot.
>
> This is probably fine, but ...
>
> > diff --git a/include/configs/tegra-common.h
> > b/include/configs/tegra-common.h
> ...
> > -#define CONFIG_SYS_CBSIZE (256 * 2) /* Console I/O Buffer Size */
> > +#define CONFIG_SYS_CBSIZE (256 * 3) /* Console I/O Buffer Size */
>
> ... "3" feels odd since it's not a power of 2:-) Perhaps you could try cherry-
> picking the following commit from our L4T U-Boot and if it works for you,
> submit that instead. That would also reduce the mainline<->L4T U-Boot delta.
>
> > http://nv-tegra.nvidia.com/gitweb/?p=3rdparty/u-boot.git;a=commit;h=d0
> > 3e1b861b9eaaf13fa37a8d4251d78b3814eaaf
>
> git remote add nv-tegra-u-boot \
> git://nv-tegra.nvidia.com/3rdparty/u-boot.git
> git fetch nv-tegra-u-boot
> git cherry-pick -s 81df4b5097ef72b9e1565c8f3fb45a9c14a9984e
next prev parent reply other threads:[~2016-09-01 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 22:46 [U-Boot] ARM: tegra: jetson-tk1: Increase console buffer size Peter Chubb
2016-08-22 23:10 ` Stephen Warren
2016-08-23 0:00 ` [U-Boot] [PATCH] ARM: tegra: increase console buffer size and sys args num Peter Chubb
2016-08-23 16:04 ` Stephen Warren
2016-08-23 22:21 ` Peter Chubb
2016-08-23 22:35 ` Stephen Warren
2016-09-01 22:42 ` Tom Warren [this message]
2016-09-01 22:53 ` [U-Boot] ARM: tegra: jetson-tk1: Increase console buffer size Peter.Chubb at data61.csiro.au
2016-09-01 23:19 ` Tom Warren
2016-09-01 23:25 ` Stephen Warren
2016-09-01 23:47 ` Peter.Chubb at data61.csiro.au
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=ebbfff7e8b2545b684925aaa1ef910f7@HQMAIL103.nvidia.com \
--to=twarren@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox