All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel 2.6.x to MPC8540/Microsys Board
Date: Fri, 14 Jan 2005 15:36:39 +0100	[thread overview]
Message-ID: <41E7D8F7.4060901@anagramm.de> (raw)
In-Reply-To: <20050114113126.434C4C108D@atlas.denx.de>

Wolfgang Denk wrote:

>>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.

Thank you, that's what I wanted to hear :-)

>>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.

Well, I don't know how the platform specific things got moved from 2.4 
to 2.6 in the past (yes I am a newbie). I have a working 
2.4.26-pm854-something with a platform/pm854_defconfig (and some changed 
non-official(?) files for the PCI and MTDs) and I want to get the same 
for 2.6.10+ without changing things at the wrong place.

Best greets,

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19

  parent reply	other threads:[~2005-01-14 14:34 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 [this message]
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=41E7D8F7.4060901@anagramm.de \
    --to=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.