public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Ron Madrid <ron_madrid@sbcglobal•net>
To: Scott Wood <scottwood@freescale•com>,
	Anton Vorontsov <cbouatmailru@gmail•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: MPC8313: fsl_elbc_nand and MDR
Date: Mon, 26 Apr 2010 16:46:02 -0700 (PDT)	[thread overview]
Message-ID: <253970.571.qm@web83505.mail.sp1.yahoo.com> (raw)
In-Reply-To: <20100426192947.GA25762@oksana.dev.rtsoft.ru>

> From: Anton Vorontsov <cbouatmailru@gmail•com>
> Subject: Re: MPC8313: fsl_elbc_nand and MDR
> To: "Scott Wood" <scottwood@freescale•com>
> Cc: linuxppc-dev@ozlabs•org, "Ron Madrid" <ron_madrid@sbcglobal•net>
> Date: Monday, April 26, 2010, 12:29 PM
> On Mon, Apr 26, 2010 at 02:28:00PM
> -0500, Scott Wood wrote:
> > 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?
> 
> Yep, u-boot or platform code.

Thank you both.  This is an easier (and probably better)
solution.

Ron

      reply	other threads:[~2010-04-26 23:46 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
2010-04-26 19:29           ` Anton Vorontsov
2010-04-26 23:46             ` Ron Madrid [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=253970.571.qm@web83505.mail.sp1.yahoo.com \
    --to=ron_madrid@sbcglobal$(echo .)net \
    --cc=cbouatmailru@gmail$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=scottwood@freescale$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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