All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add bootstrap command
Date: Thu, 16 Jul 2009 22:24:22 +0200	[thread overview]
Message-ID: <200907162224.23377.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <20090716193625.25459832E416@gemini.denx.de>

> Dear Matthias Fuchs,
> 
> In message <200907161547.17433.matthias.fuchs@esd.eu> you wrote:
> >
> > > Hi Dirk,
> > > 
> > > On Wednesday 15 July 2009 16:46:12 Mike Frysinger wrote:
> > > > On Wednesday 15 July 2009 09:48:00 Dirk Eibach wrote:
> > > > > This adds a generic command for programming I2C bootstrap eeproms.
> > > > > Implementation for Canyonlands board is included.
> > > >
> > > > "bootstrap" is pretty generic.  can you pick something a little more
> > > > descriptive/specific ?
> > > 
> > > I agree with Mike. Please change the command name and the files to something 
> > > more specific. How about "4xxbootstrap"? Or "4xxstrap"? 
> > To long for my taste. 
> > 
> > > Any other good ideas  
> > > about this naming welcome. :)
> > We called this command "sbe" on our PMC440 (440EPx) and upcoming 
> > PMC405DE (405EP) board. I must admit that I forget its meaning.
> > Probably something like 'setup bootstrap eeprom'. But it works
> 
> Indeed. "sbe" is not an acceptable name as nobody will know what it's
> suppost to mean.
> 
> > a little mit different that the bootstrap command.
> 
> Actually the name "bootstrap" command itself is something that I
> really dislike.
> 
> Please find a better description (avoiding "bootstrap"), and then
> chose a descriptive name.
ccc - config chip|cpu configuration
scc - setup chip|cpu configuration
wcc - write chip|cpu configuration
wcce - write chip|cpu configuration eeprom

I am not a friend of long names :-)

Matthias

  parent reply	other threads:[~2009-07-16 20:24 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
2009-07-17 21:41               ` Wolfgang Denk
2009-07-16 20:24         ` Matthias Fuchs [this message]
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=200907162224.23377.matthias.fuchs@esd-electronics.com \
    --to=matthias.fuchs@esd-electronics.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.