From: Wolfgang Denk <wd@denx.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linuxppc-dev mailing list <linuxppc-dev@ozlabs.org>
Subject: Re: thoughts and questions on 8xx patches
Date: Tue, 21 Sep 2004 14:52:22 +0200 [thread overview]
Message-ID: <20040921125227.46AE2C108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 21 Sep 2004 08:23:05 EDT." <Pine.LNX.4.60.0409210808250.9449@dell.enoriver.com>
In message <Pine.LNX.4.60.0409210808250.9449@dell.enoriver.com> you wrote:
>
> from list discussions some time back, i already gave up on the idea of
> the configuration being able to detect the exact processor and taking
> that into account. we've already established that, and i'm happy with
> that.
OK.
> all i'm suggesting now is a drop down choice menu of known patches
> relevant to that architecture, that's all. in some cases, there would
> be two choices, as in:
>
> [ ] I2C/SPI for 850
> [ ] I2C/SPI for 8xx (non-850)
Plus there is also the case of "need to relocate parameter RAM on a
MPC852/859/866/... processor". In this case no microcode patch i
sneeded, and the current code will crash the system.
More cases may be necessary.
> i can't imagine that this list would get overly long. from what i can
> see, the denx tree supports the following list of patches:
Please forget this. I asked you several times NOT to use this old
code for reference. It is known to be broken in several configu-
rations.
> and, unless i'm reading this badly, that's the entire list. all of
No, it's not. It will not work on most of the newer MPC8xx
processors.
> so ... why is this such an objectionable thing?
Because it is (1) incomplete and (2) broken.
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
There are two ways to write error-free programs. Only the third one
works.
next prev parent reply other threads:[~2004-09-21 12:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 20:05 thoughts and questions on 8xx patches Robert P. J. Day
2004-09-20 22:10 ` Dan Malek
2004-09-21 0:15 ` Robert P. J. Day
2004-09-21 6:37 ` Dan Malek
2004-09-21 10:13 ` Robert P. J. Day
2004-09-21 10:40 ` Wolfgang Denk
2004-09-21 10:59 ` Robert P. J. Day
2004-09-21 11:49 ` Wolfgang Denk
2004-09-21 12:23 ` Robert P. J. Day
2004-09-21 12:52 ` Wolfgang Denk [this message]
2004-09-21 12:56 ` Robert P. J. Day
2004-09-21 17:21 ` Dan Malek
2004-09-21 11:06 ` Robert P. J. Day
2004-09-21 11:26 ` Wolfgang Denk
2004-09-21 12:07 ` Robert P. J. Day
2004-09-21 12:45 ` Wolfgang Denk
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=20040921125227.46AE2C108D@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).