From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Steven Scholz <steven.scholz@imc-berlin.de>,
LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: board specific defines in commproc.h !?!?
Date: Mon, 17 Jun 2002 22:23:02 +0200 [thread overview]
Message-ID: <20020617202307.DD107102FB@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 17 Jun 2002 10:35:50 PDT." <20020617173550.GV13541@opus.bloom.county>
Dear Tom,
in message <20020617173550.GV13541@opus.bloom.county> you wrote:
>
> > You shouldbe aware of all the problems with 2.5 for 8xx systems
>
> Yes. There's 2 right now. The tlb miss handlers need to be updated
> because the pmd is now a physical address rather than a virtual one, and
> the exception handling needs to be updated for some changes Paul made
> recently. Everything else should be OK.
There is one central problem: this source tree is an experimental
tree, and it's far from being stable.
It makes no sense to me to use 2.5 as base for any of our daily work.
> Well, for the moment I'd like to try that. Considering there's really 4
> (kernel.org, linuxppc_2_4, linuxppc_2_4_devel, DENX) trees people use right
> now, I'd like to try and remove at least one of those.
Agreed. I would be more than happy to get rid of the effort to
maintain our tree. But there are so many things I've submitted again
and again that never got acceepted that I gave up. [And I am NOT
talking about obviouslu controversial stuff like our old flash
drivers.]
> And since we're stuck between a rock and a hard place, wrt killing
> 2_4_devel right now, lets use linuxppc-2.5 (or linux-2.5) which has
> 98% of the changes in _devel (and I think 100%, wrt 8xx).
This does not work. When we port Linux to any new board, we need a
stable base in the first place. Right now we're in the process of
switching to 2_4_devel, because this finally seems mature enough. 2.5
is nice for trying out new features and stuff like that, but for
cleanup, and regular extensions (like new board support stuff etc.)
it's a wasto of time to get an instable tree like 2.5 running on a
new system just to get the patches into the "real" tree where we need
them - which also may take a LONG time (or forever), judging from
previous experience.
> Fixing 2 things. And it will be a lot less painful now trying to fix 2,
> recently broken things, rather than waiting 6 months to fix 5 or 10
> broken things spanning 6-8 months.
For my purposes, 2.5 is not usable (yet). It's a playground.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Old programmers never die, they just branch to a new address.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-17 20:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 9:20 board specific defines in commproc.h !?!? Steven Scholz
2002-06-17 14:05 ` John W. Linville
2002-06-17 15:32 ` Tom Rini
2002-06-17 15:37 ` Steven Scholz
2002-06-17 15:49 ` Tom Rini
2002-06-17 16:01 ` Steven Scholz
2002-06-17 16:28 ` Tom Rini
2002-06-17 17:25 ` Wolfgang Denk
[not found] ` <20020617173550.GV13541@opus.bloom.county>
2002-06-17 17:46 ` Steven Scholz
2002-06-17 20:23 ` Wolfgang Denk [this message]
[not found] ` <3D106922.7026437A@imc-berlin.de>
2002-06-19 15:05 ` Tom Rini
2002-06-19 15:18 ` Steven Scholz
2002-06-19 15:25 ` Tom Rini
2002-06-19 15:33 ` Steven Scholz
2002-06-19 15:41 ` Tom Rini
2002-06-19 15:47 ` Steven Scholz
2002-06-19 15:51 ` Tom Rini
2002-06-19 21:11 ` Dan Malek
2002-06-19 21:22 ` Tom Rini
2002-06-20 16:32 ` Dan Malek
2002-06-19 22:15 ` Wolfgang Denk
2002-06-19 23:26 ` Conn Clark
2002-06-20 16:40 ` Dan Malek
[not found] ` <3D12F140.23BA447F@imc-berlin.de>
[not found] ` <15635.12386.415897.593660@argo.ozlabs.ibm.com>
2002-06-21 14:18 ` John Traill
[not found] <20020617214339.GZ13541@opus.bloom.county>
2002-06-17 22:28 ` 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=20020617202307.DD107102FB@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
--cc=trini@kernel.crashing.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).