From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Mitchell Date: Thu, 16 Jul 2009 19:12:45 -0500 Subject: [U-Boot] [PATCH] Add bootstrap command In-Reply-To: <20090716221157.6998B832E416@gemini.denx.de> References: <1247665680-23494-1-git-send-email-eibach@gdsys.de> <200907151046.13717.vapier@gentoo.org> <200907161521.29197.sr@denx.de> <200907161547.17433.matthias.fuchs@esd.eu> <20090716193625.25459832E416@gemini.denx.de> <4A5F8A1D.4030701@gmail.com> <20090716221157.6998B832E416@gemini.denx.de> Message-ID: <4A5FC1FD.1090201@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.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