linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alan Mimms <alan@packetengines.com>
To: "Richard Hendricks" <ra6353@email.sps.mot.com>,
	Alan Mimms <alanm@unforgettable.com>
Cc: Geir Frode Raanes <geirfrs@invalid.ed.ntnu.no>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: What is the catch with IDMA on MPC860?
Date: Fri, 17 Mar 2000 13:35:10 -0800	[thread overview]
Message-ID: <00031713360201.02646@alan> (raw)
In-Reply-To: <38D29F6F.4B425B09@email.sps.mot.com>


So THAT's why these big companies never tell us when they find their
junk sucks.  They have it in the fine print at the front of every manual!

a

On Fri, 17 Mar 2000, Richard Hendricks wrote:
> Alan Mimms wrote:
> >
> > Regarding the "where does the manual say that the performance stinks"
> > comment: even though people like Richard are VERY forthcoming with
> > "issues" with chips (THANKS Richard), I doubt a company like MOT will
> > EVER admit in a manual or other official document they built something
> > that stinks even a little bit.  See the MPC801 for an example of this
> > where virtually EVERYTHING about the chip stinks (including the crappy
> > inaccurate manual) and nothing is ever said in written form to that
> > effect.  (For those unused to my cynical style, I love MOT and my
> > company has even made a bunch of money selling devices built on the
> > MPC801.  But they are NOT perfect - as I'm sure Richard and numerous
> > will attest - and they will rarely admit it in writing.)
>
> I think this issue is covered quite well in the boilerplate at the
> beginning of the MPC823 manual.
>
> "Motorola makes no warranty, representation or guarantee regarding
> the suitability of its products for any particular purpose..."
>
--
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:[~2000-03-17 21:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <38D2530F.3417D5BA@email.sps.mot.com>
2000-03-17 16:22 ` Best embedded PPC eval board for Linux Tom Shaver
2000-03-17 18:05   ` Jo-Ellen F. Mathews
2000-03-17 17:02 ` What is the catch with IDMA on MPC860? Geir Frode Raanes
2000-03-17 17:23   ` Alan Mimms
2000-03-17 17:50     ` Dan Malek
2000-03-17 21:20       ` Richard Hendricks
2000-03-17 21:46         ` Dan Malek
2000-03-17 21:11     ` Richard Hendricks
2000-03-17 21:35       ` Alan Mimms [this message]
2000-03-17 21:09   ` Richard Hendricks
2000-03-20 10:11     ` Geir Frode Raanes
2000-03-22 16:49       ` Richard Hendricks
2000-03-22 22:59         ` Noah Misch
2000-03-23  2:34           ` Graham Stoney
2000-03-23 13:30             ` Claude Robitaille
2000-03-23 22:49           ` Richard Hendricks
2000-03-17 12:18 Geir Frode Raanes

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=00031713360201.02646@alan \
    --to=alan@packetengines.com \
    --cc=alanm@unforgettable.com \
    --cc=geirfrs@invalid.ed.ntnu.no \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=ra6353@email.sps.mot.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).