linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Jander <david.jander@protonic.nl>
To: linuxppc-embedded@ozlabs.org
Subject: Which kernel tree for future 8xx development?
Date: Thu, 17 Feb 2005 16:50:53 +0100	[thread overview]
Message-ID: <200502171650.53799.david.jander@protonic.nl> (raw)


Hi,

Which (of the many) is the most recommended 2.4.x tree for mpc8xx devices 
(specially the MPC852T). We are developing our own board-support stuff and 
drivers (it's a custom board designed by us).
Currently we have linuxppc-2_4_devel from DENX cvs and linuxppc-2_4_devel from 
bitkeeper, which seems to be a newer kernel version, but with much less 
different boards supported and less features for motorola powerpc processors. 
What's the status of CPM driver stuff for instance?

We started on DENX kernel sources and switched to bitkeeper because of some 
misinterpreted advice I received from this list about an unrelated problem, 
only to find apparently less mpc8xx support.

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)!??

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? 
One day I'd like to be able to make all our board-support stuff into something 
useful for others and go beg for inclusion in the main sources.... but where?

Greetings,

-- 
David Jander
Protonic Holland.

             reply	other threads:[~2005-02-17 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-17 15:50 David Jander [this message]
2005-02-17 17:48 ` Which kernel tree for future 8xx development? 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=200502171650.53799.david.jander@protonic.nl \
    --to=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).