linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: "Darcy Watkins" <DWatkins@tranzeo.com>
Cc: vb <vb@vsbe.com>, Mike Timmons <mike_timmons@trimble.com>,
	Andy Schmidt <andrewgschmidt@gmail.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: PPC to PowerPC Migration
Date: Wed, 11 Jun 2008 13:32:47 -0400	[thread overview]
Message-ID: <20080611133247.0ac8b7c6@zod.rchland.ibm.com> (raw)
In-Reply-To: <D61182AC8012EA4EBC531B3AF23BE109603578@tranzeo-mail2.12stewart.tranzeo.com>

On Wed, 11 Jun 2008 10:15:03 -0700
"Darcy Watkins" <DWatkins@tranzeo.com> wrote:

> Hi Josh,
> 
> I think it would be more helpful if I were to tidy it a bit and add AMCC
> Taihu boot support to it first.  Then submit it.  People are more likely
> to have access to a Taihu than one of our boards.
> 
> What I mean by "AMCC Taihu boot support" is that the board would come up
> just like our Taihushui/Kolsch family of boards, but would not include
> the extra drivers, etc needed for USB gadgets, the LCD and other like
> items that are on the AMCC board.

That sounds like a fine plan.  If you'd like, you can submit both at
the same time (as separate patches).  More board ports are always
welcome, particularly for stock eval boards.

> Once I get this done, I can submit BSP patch sets for kernel 2.6.25 and
> 2.6.26.  If there is demand, I could submit a BSP patch set for 2.6.24
> as well.

Preferably, you'd submit to the tip of the git tree for 4xx.  With the
pace of kernel development, releasing patches for "old" kernels just
means that someone has to forward port them to the latest tree.  That
might be a small effort, but in practice it's best to work with
bleeding edge if you're going to submit a patch for inclusion.

Don't be discouraged by that.  There are those that will help you if
you run into obstacles.

> Please send me (or URL to) summarized patch submission instructions /
> guidelines.

The easiest place to start is Documentation/SubmittingPatches in the
kernel tree.

josh

  reply	other threads:[~2008-06-11 17:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 17:48 PPC to PowerPC Migration Andy Schmidt
2008-06-10 23:59 ` John Linn
2008-06-11  1:19 ` Mike Timmons
2008-06-11 13:55   ` vb
2008-06-11 14:03     ` Jon Loeliger
2008-06-11 15:33       ` vb
2008-06-11 15:45         ` Darcy Watkins
2008-06-11 16:03           ` vb
2008-06-11 16:07         ` Scott Wood
2008-06-11 14:38     ` Darcy Watkins
2008-06-11 16:32       ` Josh Boyer
2008-06-11 17:15         ` Darcy Watkins
2008-06-11 17:32           ` Josh Boyer [this message]
2008-06-11 17:52             ` Darcy Watkins
2008-06-11 17:56               ` Josh Boyer
2008-06-12 15:58                 ` Darcy Watkins
2008-06-11 19:36             ` Andrew Schmidt
2008-06-12  8:14               ` Jens Wirth
2008-06-12 16:02               ` Grant Likely

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=20080611133247.0ac8b7c6@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=DWatkins@tranzeo.com \
    --cc=andrewgschmidt@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mike_timmons@trimble.com \
    --cc=vb@vsbe.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).