From: Wolfgang Denk <wd@denx.de>
To: David Jander <david.jander@protonic.nl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Which kernel tree for future 8xx development?
Date: Thu, 17 Feb 2005 18:48:34 +0100 [thread overview]
Message-ID: <20050217174839.48A3DC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 17 Feb 2005 16:50:53 +0100." <200502171650.53799.david.jander@protonic.nl>
In message <200502171650.53799.david.jander@protonic.nl> you wrote:
>
>
> Now I am observing myself doing apparently absurd things as for example taking
> arch/ppc/8260_io/cpm_spi.c from DENX and putting it into arch/ppc/8xx_io/
> from bitkeeper and hacking until it works (again). It still doesn't. Where on
> earth is the original driver (which was for MPC860, not MPC8260)!??
That's probably arch/ppc/8xx_io/cpm_spi.c from our old linux-2.4
kernelk tree.
> Before we port all of our stuff once again from one tree to another, can
> someone please give me a good advice on which way to go now and in forseeable
> future?
I cannot answer this question - maybe once there is a clear split
between stable and development kernel trees again. At the moment
there is only chaos.
Best regards,
Wolfgang Denk
--
See us @ Embedded World, Nuremberg, Feb 22 - 24, Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Mr. Cole's Axiom:
The sum of the intelligence on the planet is a constant;
the population is growing.
prev parent reply other threads:[~2005-02-17 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 15:50 Which kernel tree for future 8xx development? David Jander
2005-02-17 17:48 ` Wolfgang Denk [this message]
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=20050217174839.48A3DC1430@atlas.denx.de \
--to=wd@denx.de \
--cc=david.jander@protonic.nl \
--cc=linuxppc-embedded@ozlabs.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).