public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add bootstrap command
Date: Fri, 17 Jul 2009 06:38:46 +0200	[thread overview]
Message-ID: <200907170638.46173.sr@denx.de> (raw)
In-Reply-To: <4A5FC1FD.1090201@gmail.com>

On Friday 17 July 2009 02:12:45 Dave Mitchell wrote:
> >> 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.

I'm aware of this fact. And changing this name is of course non-optimal. But 
from my point of view, the advantages of enhancing this command and making it 
easier usable/portable for all 4xx boards overweight this disadvantage.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2009-07-17  4:38 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
2009-07-17  4:38               ` Stefan Roese [this message]
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=200907170638.46173.sr@denx.de \
    --to=sr@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