All of lore.kernel.org
 help / color / mirror / Atom feed
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 09:47:03 -0600	[thread overview]
Message-ID: <891B097E-6643-11D9-A3DB-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <41E7E64F.2080807@anagramm.de>

Clemens,

I would to just use 2.6.10 as starting point and get that working.  The=20=

amount of changes to board code is about 100 lines to go from OCP to=20
platform_device.  I should be releasing patches for this upstream today=20=

and will CC the linuxppc-embedded list, so if you really want them you=20=

can get them, but I dont think its worth the pain for you.

- kumar

On Jan 14, 2005, at 9:33 AM, Clemens Koller wrote:

> Kumar Gala wrote:
>
> > I would suggest 2.6.10 if you want an official kernel release.=A0 Is=20=

> this
> > board generally available to people?
>
>  Yes: www.microsys.de miriac Module: PM854 (and some others)
>
> > Be aware there are some infrastrucal changes I'm working on that=20
> moves
> > the 85xx sub-arch support from using OCP to platform_device.=A0=20
> However,
> > these have minor changes on the board files.
>
> I've read your last mails in this list... therefore I am asking. :-)
>  I just don't want to re-invent the wheel twice. In the pm854 specific
>  things there are also some OCP updates. (Well, I am still reading =
lots
> of code... newland for me)
>  I try to contact the developer Josef Wagner at Microsys who was=20
> working
>  on the 2.4.26-sth.
>
> > I would take a look at how 2.6 is structured for 85xx.=A0 I tried to=20=

> do a
> > better job and provide more common code for a board port to=20
> leverage.=A0
> > So for something like PCI, you should hopefully just have to setup=20=

> your
> > memory map and IRQ routing.
>
> I am comparing 2.4.26-sth with 2.6.10 now. The changes are manageable=20=

> as
> far as I got it. Where can I get the current work from you?!
>
> 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
>  _______________________________________________
> Linuxppc-embedded mailing list
>  Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

      reply	other threads:[~2005-01-14 15:47 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
2005-01-14 15:33   ` Clemens Koller
2005-01-14 15:47     ` Kumar Gala [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=891B097E-6643-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.