From: "Timothy A. Seufert" <tas@mindspring.com>
To: Holger Bettag <hobold@Informatik.Uni-Bremen.DE>,
Giuliano Pochini <pochini@shiny.it>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 7450 bugs & fixes
Date: Fri, 30 Nov 2001 13:52:18 -0800 [thread overview]
Message-ID: <p05101001b82dab7d495a@[10.0.0.42]> (raw)
In-Reply-To: <8xu1vck03a.fsf@s62.informatik.uni-bremen.de>
At 11:46 AM +0100 11/30/01, Holger Bettag wrote:
>Giuliano Pochini <pochini@shiny.it> writes:
>
>>
>>
>> > After reading the 7450 errata book, I'm now trying to figure out
>> > what need to be done for our kernel to work properly on these. [...]
>>
>> :-((
>> I've never seen so many bugs in a mot cpu before.
>> I hope they are not embracing the Intel's
>>ship-things-asap-regardless-reliability style :(
>>
>To my knowledge, Apple is their only customer that actually delivered the
>buggy revisions to end users. I guess it's not Motorola who's in a hurry.
The 7450 was probably at least a year late (if not more), going by
various Motorola announcements, roadmaps, MPF presentations, and so
forth. I don't think Apple was supposed to get stuck using the 7400
for as long as they did. No doubt Apple put pressure on Motorola to
deliver a shippable version (meaning one whose bugs Apple could
remedy with workarounds) as soon as possible.
--
Tim Seufert
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-30 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 15:00 7450 bugs & fixes Benjamin Herrenschmidt
2001-11-29 18:20 ` Gabriel Paubert
2001-11-30 8:36 ` Giuliano Pochini
2001-11-30 10:46 ` Holger Bettag
2001-11-30 21:52 ` Timothy A. Seufert [this message]
2001-12-10 22:54 ` Jim
2001-12-14 5:17 ` Christopher Murtagh
2001-12-14 9:17 ` Benjamin Herrenschmidt
2001-12-14 16:50 ` Christopher Murtagh
2001-12-14 16:53 ` Benjamin Herrenschmidt
2001-12-14 17:57 ` Gabriel Paubert
2001-12-14 19:19 ` Benjamin Herrenschmidt
2001-12-14 20:02 ` Tom Rini
2001-12-14 20:41 ` Timothy A. Seufert
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='p05101001b82dab7d495a@[10.0.0.42]' \
--to=tas@mindspring.com \
--cc=hobold@Informatik.Uni-Bremen.DE \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@shiny.it \
/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).