From: Scott Wood <scottwood@freescale.com>
To: Felix Radensky <felix@embedded-sol.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: Thu, 22 Oct 2009 11:07:36 -0500 [thread overview]
Message-ID: <4AE08348.9000102@freescale.com> (raw)
In-Reply-To: <4AE015DD.1010009@embedded-sol.com>
Felix Radensky wrote:
> Are you aware of Freescale plans to fix the problem in new silicon
> revisions ?
I don't know anything yet -- still trying to get in touch with the
relevant hardware people.
> Also, can you please tell what CPUs are affected by this, except 8536
> and 8572.
I suppose anything with an eLBC could be affected.
-Scott
next prev parent reply other threads:[~2009-10-22 16:07 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
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 [this message]
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=4AE08348.9000102@freescale.com \
--to=scottwood@freescale.com \
--cc=felix@embedded-sol.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
/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).