From: Eugene Surovegin <ebs@ebshome.net>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8272ADS stability issues
Date: Fri, 25 Nov 2005 21:22:07 -0800 [thread overview]
Message-ID: <20051126052207.GA11393@gate.ebshome.net> (raw)
In-Reply-To: <438732FD.7090201@ru.mvista.com>
On Fri, Nov 25, 2005 at 06:51:25PM +0300, Vitaly Bordug wrote:
> Unfortunately, low stability occasionally follows this boards. I have the
> same symptoms, and it is relative to something wrong with memory.
Yeah, I wasn't able to do any development on my 8272ADS due to
the same stability problems. Sometimes I wonder how Freescale can even
ship hw of such "quality".
--
Eugene
next prev parent reply other threads:[~2005-11-26 5:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 15:31 MPC8272ADS stability issues Alex Zeffertt
2005-11-25 15:51 ` Vitaly Bordug
2005-11-26 4:46 ` Walter L. Wimer III
2005-11-26 5:22 ` Eugene Surovegin [this message]
2005-11-28 9:51 ` Alex Zeffertt
-- strict thread matches above, loose matches on Subject: below --
2005-12-04 22:36 Liechty Ronald-RAT109
2005-12-18 23:36 Laurie, Ian
2005-12-20 5:22 ` Dmytro Bablinyuk
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=20051126052207.GA11393@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vbordug@ru.mvista.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).