public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: FWD: [ECOS] Problem with PowerPC cache init order
Date: Mon, 21 Jun 2004 09:58:00 -0000	[thread overview]
Message-ID: <20040621095820.GD2031@lunn.ch> (raw)

Hi Folks

Could somebody who knows about PPC caches take a look at this patch.

        Thanks
                Andrew



----- Forwarded message from "Retallack, Mark (Siemens)" <mark.retallack@siemens.com> -----

From: "Retallack, Mark (Siemens)" <mark.retallack@siemens.com>
To: ecos-discuss@sources.redhat.com
Date: Mon, 14 Jun 2004 13:50:04 +0100
Subject: [ECOS] Problem with PowerPC cache init order
X-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=2.63

I have found a problem with the PowerPC architecture hal. 

The sequence for cache initialisation after reset (in hal_enable_caches)
should be:

unlock all
invalidate all
enable cache

Instead it is:

invalidate all
unlock all
enable cache

This can cause problems if there are sections of the cache that are locked
and contain invalid data. My target crashed with an exception when it needed
to do a copyback after a first time power up (not a pretty sight!!). The
copyback address was an invalid address.

I have attached a patch to fix the problem. This works for the MPC850, but I
do not know if it is correct for the complete PowerPC family.

 <<my.patch>> 

Mark Retallack
Graduate Engineer
Siemens Traffic Controls 
Sopers Lane, Poole, Dorset. BH17 7ER. UK.
Tel: 01202 782844
Fax: 01202 782545
www.siemenstraffic.com

Committed to quality traffic solutions and service excellence





Siemens Traffic Controls is a division of Siemens plc. Registered No.
727817, England. 
Registered office: Siemens House, Oldbury, Bracknell, Berkshire, RG12 8FZ. 

This communication contains information which is confidential and 
may also be privileged. It is for the exclusive use of the addressee. 
If you are not the addressee please note that any distribution, 
reproduction, copying, publication or use of this communication 
or the information in it is prohibited.  If you have received this 
communication in error, please contact us immediately and also 
delete the communication from your computer. 




-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

----- End forwarded message -----

             reply	other threads:[~2004-06-21  9:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21  9:58 Andrew Lunn [this message]
2004-06-21 10:21 ` Nick Garnett
2004-06-21 10:23   ` Andrew Lunn
2004-06-21 11:17   ` Gary Thomas

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=20040621095820.GD2031@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-maintainers@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).