From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [u-boot-release] [Patch v3 7/7] powerpc/8xxx: Add support for interactive DDR programming interface
Date: Fri, 16 Sep 2011 14:42:27 -0500 [thread overview]
Message-ID: <4E73A6A3.6040502@freescale.com> (raw)
In-Reply-To: <1316201912.7327.22.camel@oslab-l1>
York Sun wrote:
> I think the interactive command is self-explained.
Why do people say things like that? If I say that it needs to be better
documented, then obviously it isn't self-explanatory.
> I can add some
> examples if needed. But I am afraid the example will be either too short
> or too long.
>
> For example, I can add the following
>
> First step, run "compute" command, it returns with the DIMM part number
>
> FSL DDR>compute
> Detected UDIMM UG51U6400N8SU-ACF
>
> Second step, users can run 'print' command with arguments. Without
> argument, a help message will print out
This is not an example. This is a walk-through. An example shows how
individual commands can be used, and what the output could look like.
> I can further show the examples of print/edit dimmparams, commonparams,
> opts, regs. It will be too long. It is not difficult to use the
> self-guided interface. Agree?
How could it be too long? Is there not enough room on the git server to store a
text file? This file could be 200KB is size, and that would be okay.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2011-09-16 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 16:27 [U-Boot] [Patch v3 7/7] powerpc/8xxx: Add support for interactive DDR programming interface York Sun
2011-09-16 19:15 ` [U-Boot] [u-boot-release] " Timur Tabi
2011-09-16 19:38 ` York Sun
2011-09-16 19:42 ` Timur Tabi [this message]
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=4E73A6A3.6040502@freescale.com \
--to=timur@freescale.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.