All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, tnt@246tNt.com, sl@bplan-gmbh.de
Subject: Re: [PATCH] General CHRP/MPC5K2 Platform and drivers support - to comment
Date: Fri, 20 Oct 2006 16:29:37 +1000	[thread overview]
Message-ID: <1161325778.10524.158.camel@localhost.localdomain> (raw)
In-Reply-To: <77AD49CA-69CB-4ADA-B8F3-3BC3A066BCF9@kernel.crashing.org>

On Fri, 2006-10-20 at 01:06 -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.

They should use either the /soc bus or the of_platform stuff (I'm coming
up with some reworked of_platform that can be useful to them).

Ben.

  parent reply	other threads:[~2006-10-20  6:29 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
2006-10-20  6:29   ` Benjamin Herrenschmidt [this message]
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=1161325778.10524.158.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --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 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.