From: Wolfgang Denk <wd@denx.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] to support choice of 8xx microcode patch
Date: Sat, 25 Sep 2004 17:27:12 +0200 [thread overview]
Message-ID: <20040925152717.F29D4C108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 25 Sep 2004 11:10:45 EDT." <Pine.LNX.4.60.0409251109150.4235@dell.enoriver.com>
In message <Pine.LNX.4.60.0409251109150.4235@dell.enoriver.com> you wrote:
>
> > Where do you select which CPU type gets used, and adjust for the
> > corresponfding version of the uCode patch?
>
> are you referring to the distinction you make in the DENX 2.4 tree,
> where you distinguish between 850 and non-850 architectures? since
This is one part of what needs to be done. Also, the MPC866 family
handles relocation differently.
> that appears to be done manually, i see no reason why the same
> couldn't be done in the patch i submitted. it would be a trivial
> change to get the same effect.
You are right. But since you wrote "this is a *full* ... patch"
(emphasis by yourself) I somehow expected that you covered this
problem, too.
Sorry if this was a misunderstanding.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"The more data I punch in this card, the lighter it becomes, and the
lower the mailing cost."
- Stan Kelly-Bootle, "The Devil's DP Dictionary"
next prev parent reply other threads:[~2004-09-25 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 12:49 [PATCH] to support choice of 8xx microcode patch Robert P. J. Day
2004-09-25 13:44 ` Wolfgang Denk
2004-09-25 14:35 ` Robert P. J. Day
2004-09-25 15:10 ` Robert P. J. Day
2004-09-25 15:27 ` Wolfgang Denk [this message]
2004-09-25 17:19 ` Robert P. J. Day
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=20040925152717.F29D4C108D@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rpjday@mindspring.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