All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/85xx: corenet_ds: increase console	buffer size to 1024
Date: Mon, 26 Sep 2011 16:11:14 -0500	[thread overview]
Message-ID: <4E80EA72.3090807@freescale.com> (raw)
In-Reply-To: <20110926180955.32B721407999@gemini.denx.de>

On 09/26/2011 01:09 PM, Wolfgang Denk wrote:
> In message <20110926112756.bb93d41b.kim.phillips@freescale.com> you wrote:
>> We need to enable reverting an env var to its original default
>> definition.
> 
> Do we? We have not had that feature for over a decade and nobody ever
> really suffered from it. Now we have "env -f reset" for almost a
> year, and guess how many percent of the users even know about this
> command? And how many have ever actually used it yet?

I think he's saying that one shouldn't be prohibited by length from
manually typing "setenv nfsboot ..." to set a value that is no longer
than (or even is identical to) the default value.

>> Perhaps over time the nfsboot norm setting should be migrated to
>> something more modular in the board config files, but right now,
>> users are complaining about simply expecting to being able to type
>> two more characters on the command line.
> 
> Then educate your users that a boot loader is a resource restricted
> environment, and that there at least 10 different ways to do what they
> want, at least 8 of them resulting in a much simpler and easier to
> comprehend environment setup.

What is the resource constraint here that prevents accepting longer
console commands?  This is a change to the config for a board that comes
with multiple gigabytes of RAM.  This is not code that runs prior to
relocation.

Whether the environment scripts could, in time, be structured better is
a separate issue from whether there's a good reason to keep this
arbitrary limit at its current value that prevents people from manually
typing in what is currently being used.

-Scott

  reply	other threads:[~2011-09-26 21:11 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 [this message]
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

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=4E80EA72.3090807@freescale.com \
    --to=scottwood@freescale.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.