linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol.com>
To: Scott Wood <scottwood@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS problem on MPC8536DS
Date: Mon, 19 Oct 2009 21:39:57 +0200	[thread overview]
Message-ID: <4ADCC08D.5080207@embedded-sol.com> (raw)
In-Reply-To: <20091019154002.GC19074@loki.buserror.net>

Scott Wood wrote:
> On Sun, Oct 18, 2009 at 11:38:13AM +0200, Felix Radensky wrote:
>   
>> Hi, Scott
>>
>> Scott Wood wrote:
>>     
>>> On Fri, Oct 16, 2009 at 07:01:43AM +0200, Felix Radensky wrote:
>>>       
>>>> Thanks for confirmation. So the real problem is eLBC ?
>>>> What happens if I access other devices on eLBC (e.g. FPGA)
>>>> simultaneously with NAND or NOR ?
>>>>         
>>> AFAICT, the problem is NAND being accessed simultaneously with anything else
>>> on the eLBC (at least GPCM -- not sure about UPM).  Instead of delaying the
>>> memory-like transaction until the NAND special operation has completed, it
>>> seems to just abort the NAND operation.
>>>
>>> eLBC can't really tell the difference whether you've got NOR or FPGA hooked
>>> up to a GPCM chip select, so the problem should still apply.
>>>
>>>       
>> Can you please provide some code example of synchronizing GPCM and NAND ?
>>     
>
> I don't have any.  It's something that would have to be written.
>   
OK, no problem. I just wanted to get an idea of what should be done.
Should the NOR code poll some eLBC register to wait for completion of
NAND special operation ? Can you tell what register is relevant ?

Thanks.

Felix.

  reply	other threads:[~2009-10-19 19:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14 10:54 UBIFS problem on MPC8536DS Felix Radensky
2009-10-14 12:36 ` Adrian Hunter
2009-10-14 13:02   ` Felix Radensky
2009-10-14 13:21   ` Felix Radensky
2009-10-14 16:44     ` Adrian Hunter
2009-10-14 17:48       ` Felix Radensky
2009-10-14 18:13         ` Scott Wood
2009-10-14 20:12           ` Felix Radensky
2009-10-15 20:07           ` Scott Wood
2009-10-16  5:01             ` Felix Radensky
2009-10-16 15:31               ` Scott Wood
2009-10-18  9:38                 ` Felix Radensky
2009-10-19 15:40                   ` Scott Wood
2009-10-19 19:39                     ` Felix Radensky [this message]
2009-10-19 19:47                       ` Scott Wood
2009-10-19 20:19                         ` Felix Radensky
2009-10-20 15:30                         ` Felix Radensky
2009-10-22  8:20                 ` Felix Radensky
2009-10-22 16:07                   ` Scott Wood
2009-10-15  9:54 ` Norbert van Bolhuis
2009-10-15 10:45   ` MPC5121 CAN and USB Kári Davíðsson
2009-10-15 11:20     ` Paul Gibson
2009-10-15 11:36       ` Kári Davíðsson
2009-10-15 18:30         ` Wolfgang Denk
2009-10-15 23:03           ` Paul Gibson
2009-10-15 23:10             ` Wolfgang Denk
2009-10-19  6:46               ` David Jander
2009-10-16 13:53           ` Kári Davíðsson
2009-10-15 12:49   ` UBIFS problem on MPC8536DS Felix Radensky

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=4ADCC08D.5080207@embedded-sol.com \
    --to=felix@embedded-sol.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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).