From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/85xx: corenet_ds: increase console buffer size to 1024
Date: Wed, 28 Sep 2011 22:57:06 +0200 [thread overview]
Message-ID: <20110928205706.BCF66140799B@gemini.denx.de> (raw)
In-Reply-To: <4E821558.8030902@freescale.com>
Dear Scott Wood,
In message <4E821558.8030902@freescale.com> you wrote:
>
> > You don't write all your C code in a single line per function, or do
> > you?
>
> Of course not, but this a rather different environment, that doesn't
> support multiline code in the same way. It's more like macro
> substitution, and yes, there are times when I'd have C macros that are
> more than 256 characters.
Actually U-Boot does support multi-line macro definitions...
> If 256 is "more than reasonably long", are you going to force all the
> boards that set it to 512 or 1024 to change? Or does this just apply to
> those boards that were unlucky enough to not have the bigger limit from
> day one?
Neither one nore the other.
It applies to boards that use strings in their default environment
that exceed the length of the buffer.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
It's hard to think of you as the end result of millions of years of
evolution.
prev parent reply other threads:[~2011-09-28 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 16:38 [U-Boot] [PATCH] powerpc/85xx: corenet_ds: increase console buffer size to 1024 Kim Phillips
2011-09-23 18:22 ` Kumar Gala
2011-09-23 19:00 ` Kim Phillips
2011-09-25 20:11 ` Wolfgang Denk
2011-09-26 16:27 ` Kim Phillips
2011-09-26 18:09 ` Wolfgang Denk
2011-09-26 21:11 ` Scott Wood
2011-09-26 22:15 ` Brian Grayson
2011-09-26 22:55 ` Kim Phillips
2011-09-27 9:45 ` Wolfgang Denk
2011-09-27 18:26 ` Scott Wood
2011-09-28 20:57 ` Wolfgang Denk [this message]
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=20110928205706.BCF66140799B@gemini.denx.de \
--to=wd@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