From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Mark Chambers <markc@mail.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:38:59 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0407271736520.7534@localhost.localdomain> (raw)
In-Reply-To: <015b01c4741d$aca87010$0301a8c0@chuck2>
On Tue, 27 Jul 2004, Mark Chambers wrote:
> Robert,
>
> I know I've never had a need to use a microcode patch. Maybe a quick
> survey - has anybody ever had a need to use two patches at once? I'm
> suspecting you may be putting a lot of effort into something that's rarely
> needed. Also, as Motorola updates their silicon the patches will likely
> become less relevant (less likely that new users will need the patches).
on my project alone, we've needed two different selections of those
patches. so while it's not an earth-shattering modification, it
doesn't hurt and it sometimes helps. and it makes the addition of any
future patches really trivial, if that ever happens.
rday
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-27 21:38 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 ` Robert P. J. Day [this message]
2004-07-27 21:32 ` more questions about 8xx microcode patches 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
-- 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.0407271736520.7534@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=markc@mail.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).