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:15:04 -0500 [thread overview]
Message-ID: <4E73A038.8030201@freescale.com> (raw)
In-Reply-To: <1316190465-11186-1-git-send-email-yorksun@freescale.com>
York Sun wrote:
> +Interactive DDR debugging
> +===========================
> +
> +For DDR parameter tuning up and debugging, the interactive DDR debugging can
> +be activated by saving an environment variable "ddr_interactive". The value
> +doesn't matter. Once activated, U-boot prompts "FSL DDR>" before enabling DDR
> +controller. The available commands can be seen by typing "help".
> +
> +The example flow of using interactive debugging is
> +type command "compute" to calculate the parameters from the default
> +type command "print" with arguments to show SPD, options, registers
> +type command "edit" with arguments to change any if desired
> +type command "go" to continue calculation and enable DDR controller
> +
> +Note, check "next_step" to show the flow. For example, after editing registers,
> +DDR controller will be enabled with current setting without further
> +calculation.
This is pretty skimpy for such a powerful feature. How about some examples and
a detailed description of each command?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-09-16 19:15 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 ` Timur Tabi [this message]
2011-09-16 19:38 ` [U-Boot] [u-boot-release] " York Sun
2011-09-16 19:42 ` Timur Tabi
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=4E73A038.8030201@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.