From: Scott Wood <scottwood@freescale.com>
To: Ron Madrid <ron_madrid@sbcglobal.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: MPC8313: fsl_elbc_nand and MDR
Date: Mon, 26 Apr 2010 14:28:00 -0500 [thread overview]
Message-ID: <4BD5E940.7000109@freescale.com> (raw)
In-Reply-To: <335466.44978.qm@web83505.mail.sp1.yahoo.com>
Ron Madrid wrote:
> Thanks. Although this doesn't handle programming the
> UPM, which is where my conflict is occurring. MDR is
> used when programming the UPM. Do you think I would
> be better served to program the UPM in U-boot and
> therefore preempt this conflict?
If you don't need to reprogram it dynamically, doing it either in u-boot
or early in platform code is probably best.
I guess the UPM NAND code relies on U-Boot doing this?
-Scott
next prev parent reply other threads:[~2010-04-26 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 18:04 MPC8313: fsl_elbc_nand and MDR Ron Madrid
2010-04-26 18:34 ` Scott Wood
2010-04-26 19:08 ` Ron Madrid
2010-04-26 19:10 ` Scott Wood
2010-04-26 19:24 ` Ron Madrid
2010-04-26 19:28 ` Scott Wood [this message]
2010-04-26 19:29 ` Anton Vorontsov
2010-04-26 23:46 ` Ron Madrid
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=4BD5E940.7000109@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ron_madrid@sbcglobal.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).