linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daris Nevil <dnevil@snmc.com>
To: Lucinda Schafer <lucsch@adaptivemicro.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: MMU problems?
Date: Thu, 22 Jun 2000 09:19:26 -0500	[thread overview]
Message-ID: <3952206E.E2CBD46C@snmc.com> (raw)
In-Reply-To: A109131318C4D1119AC20060088DECE330F4B1@amwmail.adaptivemicro.com


Lucinda,

I am having good success with the MPC850.  Our board is able to
run without MMU problems, and shutting down is not a problem.
We are using a kernel leveraged from 2.2.5, so it is a bit older,
and I think some of the MMU code has changed since them.

Daris Nevil
SiSIC Inc/SNMC
www.snmc.com

Lucinda Schafer wrote:

> I agree. I believe we ARE dealing with a kernel bug, and it is particular to
> the MPC823.
>
> Let's hear some success stories--embedded units in production, running in
> the field for days, shutting down power and rebooting with no kernel panics.
> That may help convince me we are dealing with a hardware issue.
>
> Lucinda Schafer
> Staff Software Engineer
> Adaptive Micro-Ware, Inc.
>
> -----Original Message-----
> From: Patrick Lerda [mailto:Lerda@microprocess.com]
> Sent: Thursday, June 22, 2000 2:01 AM
> To: 'Dan Malek'; Nguyen Xuan Hoang
> Cc: linuxppc-embedded@lists.linuxppc.org
> Subject: RE: MMU problems?
>
> Have you tried to do complex operation on a 8xx board like compiling the
> kernel. This operation
> works well on a PPC740 board, but on a 8xx after a long time the kernel goes
> in an unstable
> state. Theses bugs are related to the 8xx MMU code.
>
> Patrick LERDA
>
> > -----Message d'origine-----
> > De:   Dan Malek [SMTP:dan@netx4.com]
> > Date: jeudi 22 juin 2000 05:56
> > À:    Nguyen Xuan Hoang
> > Cc:   linuxppc-embedded@lists.linuxppc.org
> > Objet:        Re: MMU problems?
> >
> >
> > Nguyen Xuan Hoang wrote:
> >
> > > I have seen a lot of discussions about MMU on MPC823,
> >
> >
> > There are no MMU or cache related problems on any of the MPC8xx
> > processors and stable versions of Linux.  These are just people
> > discussing the challenges of building custom boards and making
> > source code changes.
> >
> > There are dozens of people shipping products with Linux running on
> > these processors.  You seldom hear from people that are happy and
> > successful.
> >
> >
> >       -- Dan
> >
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-06-22 14:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-22 13:44 MMU problems? Lucinda Schafer
2000-06-22 14:19 ` Daris Nevil [this message]
2000-06-22 17:25 ` Wolfgang Denk
     [not found] <17B78BDF120BD411B70100500422FC63079FA3@IIS000>
2000-06-25 16:41 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2000-06-23  8:06 Patrick Lerda
2000-06-23  7:43 Patrick Lerda
2000-06-23  8:32 ` Wolfgang Denk
2000-06-22  7:01 Patrick Lerda
2000-06-22 15:58 ` Dan Malek
1999-12-22  4:02 Nguyen Xuan Hoang
2000-06-22  3:56 ` Dan Malek

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=3952206E.E2CBD46C@snmc.com \
    --to=dnevil@snmc.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=lucsch@adaptivemicro.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).