From: Wolfgang Denk <wd@denx.de>
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel 2.6.x to MPC8540/Microsys Board
Date: Fri, 14 Jan 2005 12:31:21 +0100 [thread overview]
Message-ID: <20050114113126.434C4C108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 14 Jan 2005 11:50:56 +0100." <41E7A410.6060008@anagramm.de>
In message <41E7A410.6060008@anagramm.de> you wrote:
>
> Now I 've tried the official 2.6.10 Kernel and (cross-)compiled it
> within ELDK 3.1 (btw: is there any difference in between ppc_6xx- and
> ppc_82xx- ?) which works fine, too.
ppc_82xx is a symbolic link ppc_6xx
> Which is the best Kernel source tree to start porting 2.6.x to the pm854
> platform? I would prefer to stuck with the official sources. Is that a
> good idea?
Yes.
> Is it a good idea to just 'copy' the pm854 platform specific files (PCI
> initialization and some MTD driver options) to the 2.6.10 tree and see
> how it works?
Copy from where? from 2.4? No.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
A fail-safe circuit will destroy others. -- Klipstein
next prev parent reply other threads:[~2005-01-14 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 10:50 Kernel 2.6.x to MPC8540/Microsys Board Clemens Koller
2005-01-14 11:31 ` Wolfgang Denk [this message]
2005-01-14 13:18 ` Sam Song
2005-01-14 14:36 ` Clemens Koller
2005-01-14 16:02 ` Wolfgang Denk
2005-01-14 14:43 ` Kumar Gala
2005-01-14 15:33 ` Clemens Koller
2005-01-14 15:47 ` Kumar Gala
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=20050114113126.434C4C108D@atlas.denx.de \
--to=wd@denx.de \
--cc=clemens.koller@anagramm.de \
--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).