All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: Matt Porter <porter@cox.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ebony crash fix & 440GP cleanup step one
Date: 30 May 2002 16:00:47 -0700	[thread overview]
Message-ID: <52d6vdnsv4.fsf@topspin.com> (raw)
In-Reply-To: <20020529154551.C3960@home.com>


>>>>> "Matt" == Matt Porter <porter@cox.net> writes:

    Matt> Looks great, pushed.  There's still more work to do in the
    Matt> includes but it's a good start.  I'm moving the PCIX
    Matt> initialization to a common library, so don't overlap there
    Matt> if you wander out of moving headers around.

Cool.  I'm starting to think about the best way to organize the code
in ebony.c.  It seems like maybe ebony.c should become ppc440_setup.c
with the Ebony-specific stuff inside #ifdef CONFIG_EBONY (and if we do
that, maybe ppc4xx_setup.c should be split into ppc40x_setup.c and
really generic stuff in ppc4xx_setup.c).  Another option would be to
keep ebony.c but move most of the code into library functions in a new
ppc440_setup.c file.

My motivation is that I'm going to have a few 440GP-based boards to
deal with soon, and I'd like to minimize the amount of code that has
to be copied or duplicated to support a new board.  I'd like to do
this in a way that fits in well with the kernel so it's easy for me to
keep our kernel tree in sync with the main tree.

What are your thoughts?

Thanks,
Roland

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

  reply	other threads:[~2002-05-30 23:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-24 15:58 ZMII Code Panics on 440GP Ebony Venkatesh Rao
2002-05-24 16:40 ` Roland Dreier
2002-05-24 19:20   ` Matt Porter
2002-05-24 19:17     ` Roland Dreier
2002-05-24 20:47       ` Matt Porter
2002-05-28 22:04         ` Ebony crash fix & 440GP cleanup step one Roland Dreier
2002-05-29 22:45           ` Matt Porter
2002-05-30 23:00             ` Roland Dreier [this message]
2002-06-04  0:44             ` A few more PPC440GP/Ebony cleanups Roland Dreier

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=52d6vdnsv4.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=porter@cox.net \
    /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.