All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: paulus@samba.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: The Plan
Date: Thu, 08 Nov 2001 12:08:52 -0700	[thread overview]
Message-ID: <3BEAD844.380F227A@mvista.com> (raw)
In-Reply-To: 15337.62287.965562.545296@cargo.ozlabs.ibm.com


Paul Mackerras wrote:

> Mark A. Greer writes:
>
> > I would move harrier.c and pplus_common.c to the "kernel" dir since they
> > are both bridge related files (kinda like the mpc10x_common.c file).
>
> I wondered about pplus_common.c, actually.  Are pplus_common.c and
> harrier.c likely to be used by more than one or two platforms in the
> future?

Depends what  you mean by "platform".

Basically, most of the older MCG boards will use pplus_common.c (supports
falcon/raven and hawk); most of the newer ones will use the harrier.  It
depends on whether the MCG boards are supported by one or two "board ports"
or if each board has its own "board port".  Lately, we've been separating
them out because there have been more significant differences between the
various boards and having things like residual data are not assured anymore
(or residual data that's close to correct).

Any comments Matt?

> If we leave them in kernel then we need to move the
> corresponding header files to include/asm-ppc.

> BTW, I would love to find a way to move all the platform-specific
> files (mvme5100.h, for instance) from include/asm-ppc to
> arch/ppc/platforms too.  The obstacle at the moment is the serial
> stuff.

Sounds like the right place to me too.

Mark


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-11-08 19:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07 11:35 The Plan Paul Mackerras
2001-11-07 11:47 ` Geert Uytterhoeven
2001-11-07 11:50   ` Paul Mackerras
2001-11-07 22:19     ` Frank Rowand
2001-11-07 20:41   ` Val Henson
2001-11-08  0:24     ` Mark A. Greer
2001-11-08  0:26       ` Mark A. Greer
2001-11-07 12:09 ` Matt Porter
2001-11-07 17:44 ` Mark A. Greer
2001-11-08  0:41 ` Mark A. Greer
2001-11-08  2:51   ` Paul Mackerras
2001-11-08 19:08     ` Mark A. Greer [this message]
2001-11-08  0:48 ` Mark A. Greer
2001-11-08  1:12   ` Tom Rini
2001-11-08 11:14 ` Chris Emerson
2001-11-08 12:07   ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2009-03-24 22:35 David Miller
2009-03-24 22:43 ` Ramkrishna Vepa
2009-03-24 22:48   ` David Miller
2009-03-25  2:03 ` Vlad Yasevich
2009-03-25  2:06   ` David Miller

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=3BEAD844.380F227A@mvista.com \
    --to=mgreer@mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@samba.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.