On 7/16/2009 5:11 PM, Wolfgang Denk wrote: > Dear Dave Mitchell, > > In message<4a5f8a1d.4030...@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 _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
