linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Dan Malek <dan@embeddededge.com>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: more questions about 8xx microcode patches
Date: Tue, 27 Jul 2004 17:56:26 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.60.0407271755050.7567@localhost.localdomain> (raw)
In-Reply-To: <81B2FD02-E014-11D8-96F8-003065F9B7DC@embeddededge.com>


On Tue, 27 Jul 2004, Dan Malek wrote:

> On Jul 27, 2004, at 4:23 PM, Robert P. J. Day wrote:

>>   it seems that creating a menu of 8xx microcode patches would be
>> fairly easy:

> Hahahahaha!!!!  You don't know how big of a hole you are digging :-)

   "Now, Ward, don't just tell the Beav he shouldn't do it.  It's
always better when they learn these things on their own."

rday

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

  parent reply	other threads:[~2004-07-27 21:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 20:23 more questions about 8xx microcode patches Robert P. J. Day
2004-07-27 21:07 ` Mark Chambers
2004-07-27 21:27   ` Looking for GT64260 MPSC serial console driver Jeff Domogala
2004-07-27 22:50     ` Mark A. Greer
2004-07-27 23:02       ` Mark A. Greer
2004-07-27 21:38   ` more questions about 8xx microcode patches Robert P. J. Day
2004-07-27 21:32 ` Dan Malek
2004-07-27 21:36   ` Robert P. J. Day
2004-07-27 22:30     ` Wolfgang Denk
2004-07-28 11:21       ` David Ho
2004-07-27 21:56   ` Robert P. J. Day [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-27 21:44 Wells, Charles

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=Pine.LNX.4.60.0407271755050.7567@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).