linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alan Mimms <alan@packetengines.com>
To: Dan Malek <dan@netx4.com>
Cc: "Mark S. Mathews" <mark@absoval.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: RPXLite 823 PCMCIA troubles
Date: Wed, 01 Dec 1999 09:46:38 -0800	[thread overview]
Message-ID: <38455EFD.1E37B102@packetengines.com> (raw)
In-Reply-To: 38455921.52C11DB2@netx4.com


Sorry to have implied that it is OK to code as if it won't happen on 8xx processors.
I have personally been bitten by 8xx code written by others with lots of missing
EIEIOs.  I would NEVER recommend any coding practice that left off the proper guarded
characteristic on pages or left out the necessary EIEIOs between necessarily
sequential operations and the necessary cache flushing and SYNCs before DMAs.

Upon rereading what I had written, it does appear I was suggesting this type of coding
is optional, which IT MOST POINTEDLY IS NOT.

Thanks for amplifying, Dan.

a

Dan Malek wrote:

> Alan Mimms wrote:
>
> > This issue probably is nearly moot on the nearly non-superscalar (dumb as a rock)
> > 8xx processors, but is MUCH more important (i.e., VITAL) on the 82xx processors
> > with the 603ish core and on all "real" PowerPC processors.
>
> In defense of the 8xx, it isn't as dumb as some people believe.
> It is a PPC core that performs a number of performance enhancements,
> including branch folding and speculative loads.  Not to the extent
> of a superscalar (and the 603 isn't a shining star compared to
> other PPCs, either), but they still happen and you have to be
> careful of them just like any other PPC.
>
> Designing a system using a "it doesn't happen as often" requirement
> is a very poor engineering practice.
>
>         -- Dan

--
Alan Mimms     Packet Engines, Inc.     Spokane, Washington [99214-0497]
  USA, Earth, Sol, Milky Way, The Local Group, Virgo Supercluster, U0
Despite the cost of living, have you noticed how popular it remains?
  -- Steven Wright?


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

  reply	other threads:[~1999-12-01 17:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-30 19:43 RPXLite 823 PCMCIA troubles Mark S. Mathews
1999-12-01  2:51 ` Dan Malek
1999-12-01  3:41   ` Mark S. Mathews
1999-12-01  4:08     ` Dan Malek
1999-12-02 20:49       ` Mark S. Mathews
1999-12-02 21:10         ` Dan Malek
1999-12-01  4:24     ` Alan Mimms
1999-12-01 17:21       ` Dan Malek
1999-12-01 17:46         ` Alan Mimms [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-12-03  4:31 Brian Kuschak
1999-12-03  6:32 ` Mark S. Mathews

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=38455EFD.1E37B102@packetengines.com \
    --to=alan@packetengines.com \
    --cc=dan@netx4.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mark@absoval.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).