All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Mitchell <dmitch71@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add bootstrap command
Date: Thu, 16 Jul 2009 19:12:45 -0500	[thread overview]
Message-ID: <4A5FC1FD.1090201@gmail.com> (raw)
In-Reply-To: <20090716221157.6998B832E416@gemini.denx.de>

On 7/16/2009 5:11 PM, Wolfgang Denk wrote:
> Dear Dave Mitchell,
>
> In message<4A5F8A1D.4030701@gmail.com>  you wrote:
>>> Please find a better description (avoiding "bootstrap"), and then
>>> chose a descriptive name.
>> Keep in mind the processor UM documentation section that covers these
>> boot methods is labeled "Bootstrap Operations". It refers the registers
>> that the EEPROM values populate as "bootstrap registers", etc.
>
> Yes, I know. But then, bootstrapping [1] is  really  a  name  with  a
> _very_ fuzzy meaning. It can be anything. The fact thay it was chosen
> in  the  UM documentation does't make it better - in U-Boot context I
> think about other activities, and in Linux context  yet  about  other
> things.

In general, the term does have a "fuzzy" meaning. But within the AMCC 
4xx processors, it does not. And we are talking about a command that 
would only be available to AMCC 4xx processors.

A command that's been in use on several U-Boot 4xx ports for some time.

>
>> There is some logic in tying the section of the processor manual to the
>> command. Whatever the command ends up being labeled, it would be nice if
>> its purpose was clear to those who actually work in 4xx space.
>
> We are changing the CPU configuration, right? It has nothing to do
> with actually booting or bootstrapping? We are setting parameters that
> will be used by the CPU when it comes up out of reset, that's all.

It does actually allow you to set the boot ROM location, just FYI.

>
> So maybe we call this config_cpu ?
>
>> Not to mention there is documentation referencing the current commands
>> used by the evaluation platforms.
>
> Documentation should be updated when new software versions become
> available - that's a matter of fact.

Of course. And I suppose I'm wasting energy typing since you have 
already made up your mind on the subject but no harm in trying.

Best regards,
-DM

  reply	other threads:[~2009-07-17  0:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 13:48 [U-Boot] [PATCH] Add bootstrap command Dirk Eibach
2009-07-15 14:46 ` Mike Frysinger
2009-07-16 13:21   ` Stefan Roese
2009-07-16 13:47     ` Matthias Fuchs
2009-07-16 14:06       ` Stefan Roese
2009-07-16 14:16         ` Felix Radensky
2009-07-16 18:04           ` Stefan Roese
2009-07-16 15:00         ` Matthias Fuchs
2009-07-16 18:25           ` Stefan Roese
2009-07-16 20:08             ` Matthias Fuchs
2009-07-16 22:05               ` Wolfgang Denk
2009-07-17  4:49               ` Stefan Roese
2009-07-16 19:36       ` Wolfgang Denk
2009-07-16 20:14         ` Dave Mitchell
2009-07-16 22:11           ` Wolfgang Denk
2009-07-17  0:12             ` Dave Mitchell [this message]
2009-07-17  4:38               ` Stefan Roese
2009-07-17 21:41               ` Wolfgang Denk
2009-07-16 20:24         ` Matthias Fuchs
2009-07-16 22:18           ` Wolfgang Denk
2009-07-16 13:55 ` Matthias Fuchs

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=4A5FC1FD.1090201@gmail.com \
    --to=dmitch71@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.