linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, sl@bplan-gmbh.de, tnt@246tNt.com
Subject: Re: [PATCH] General CHRP/MPC5K2 Platform and drivers support - to comment
Date: Fri, 20 Oct 2006 08:29:29 +0200	[thread overview]
Message-ID: <20061020062929.GC14390@powerlinux.fr> (raw)
In-Reply-To: <77AD49CA-69CB-4ADA-B8F3-3BC3A066BCF9@kernel.crashing.org>

On Fri, Oct 20, 2006 at 01:06:14AM -0500, Kumar Gala wrote:
> 
> On Oct 19, 2006, at 7:39 AM, Nicolas DET wrote:
> 
> >This 'big' patch adds support for CHRP/MPC52xx based platform.  
> >Here, this is the bPlan's Efika computer (http://www.bplan-gmbh.de/ 
> >efika_spec_en.html)
> >
> >We know this patch is not totaly compliant with Documentation/ 
> >CodingStyle/.
> >
> >We would like people to comment and review it. This way we would  
> >provide a new patch with the changes required (if any) for an  
> >upcomming merge in the kernel.
> >
> >This patch has been applied on the kernel 2.6.18.1.
> >
> >Signed-off-by: Nicolas DET <nd@bplan-gmbh.de>
> >Signed-off-by: Sven Luther <sl@bplan-gmbh.de>
> 
> I think it would be extremely useful to get a dump of what the device- 
> tree looks like.  We have to be very careful to device nodes for 52xx  
> components are competed consistent between this 'CHRP' style and a  
> more embedded 52xx boards.

Well, the efika is a CHRP board, and thus more akin to the pegasos or IBM
boxes than the embedded 52xx boards with regard to the device trees. Nico will
provide you an lsprop output.

> Some high level comments:
> 2. PIC code needs to be updated for new interrupt model (as well as  
> remove of pt_regs)

Notice that the efika does not have the interrupt tree bindings in the
firmware. I implemented those on pegasos last month, but linux refused to
boot, and i am currently waiting for comments from benh on the lsprop output.

Friendly,

Sven Luther

  reply	other threads:[~2006-10-20  6:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 12:39 [PATCH] General CHRP/MPC5K2 Platform and drivers support - to comment Nicolas DET
2006-10-19 14:12 ` Jon Loeliger
2006-10-19 16:18 ` Linas Vepstas
2006-10-19 16:26   ` Grant Likely
2006-10-19 23:41   ` Benjamin Herrenschmidt
2006-10-20  5:55     ` Kumar Gala
2006-10-19 17:43 ` Olof Johansson
2006-10-20  6:06 ` Kumar Gala
2006-10-20  6:29   ` Sven Luther [this message]
2006-10-20  6:29   ` Benjamin Herrenschmidt
2006-10-20  8:12   ` Nicolas DET
2006-10-20 14:18     ` Kumar Gala
2006-10-20 14:24       ` Nicolas DET
2006-10-20 14:34         ` Kumar Gala
2006-10-21 23:25           ` Benjamin Herrenschmidt
2006-10-22 12:56       ` Nicolas DET
2006-10-23  6:36         ` Benjamin Herrenschmidt
2006-10-23 14:47           ` Matt Sealey
2006-10-23 15:52             ` Christoph Hellwig
2006-10-23 16:25               ` Matt Sealey
2006-10-23 16:40             ` Segher Boessenkool
2006-10-23 21:38             ` Benjamin Herrenschmidt
2006-10-23 22:57             ` Paul Mackerras
2006-10-24 15:44               ` Matt Sealey
2006-10-24 16:01                 ` Becky Bruce
2006-10-24 23:01                 ` Paul Mackerras
2006-10-25 14:44                   ` Matt Sealey
2006-10-25 14:50                     ` Kumar Gala
2006-10-25 14:56                       ` Matt Sealey
2006-10-25 14:57                     ` Grant Likely
2006-10-25 16:18                       ` Matt Sealey
2006-10-25 17:08                         ` Olof Johansson
2006-10-25 21:29                         ` Paul Mackerras
2006-10-25 21:22                     ` Paul Mackerras

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=20061020062929.GC14390@powerlinux.fr \
    --to=sven.luther@wanadoo.fr \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sl@bplan-gmbh.de \
    --cc=tnt@246tNt.com \
    /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).