From: Kumar Gala <kumar.gala@freescale.com>
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 08:43:47 -0600 [thread overview]
Message-ID: <B29E7784-663A-11D9-A3DB-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <41E7A410.6060008@anagramm.de>
[snip]
> My questions are now:
> Which is the best Kernel source tree to start porting 2.6.x to the=20
> pm854
> platform? I would prefer to stuck with the official sources. Is that a
> good idea?
I would suggest 2.6.10 if you want an official kernel release. Is this=20=
board generally available to people? If so, and you want support for=20
this board in the official kernel, send me your patches for review. =20
I'll then push them up stream.
Be aware there are some infrastrucal changes I'm working on that moves=20=
the 85xx sub-arch support from using OCP to platform_device. However,=20=
these have minor changes on the board files.
> Is it a good idea to just 'copy' the pm854 platform specific files =
(PCI
> =A0 initialization and some MTD driver options) to the 2.6.10 tree and=20=
> see
> how it works?
I would take a look at how 2.6 is structured for 85xx. I tried to do a=20=
better job and provide more common code for a board port to leverage. =20=
So for something like PCI, you should hopefully just have to setup your=20=
memory map and IRQ routing.
> As there anybody who has already a working 2.6.10-something for =
MPC8540
> (well, non mpc8540ads).
I'm not aware of anyone else with another MPC8540 port, I know of other=20=
MPC8560's, and MPC8555/41 ports.
- kumar
next prev parent reply other threads:[~2005-01-14 14:43 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
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 [this message]
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=B29E7784-663A-11D9-A3DB-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.