From: Gary Thomas <gary@mlbassoc.com>
To: Cort Dougan <cort@fsmlabs.com>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Support for Arctic platform (405LP based)
Date: 13 Dec 2002 07:26:02 -0700 [thread overview]
Message-ID: <1039789562.7542.14781.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <20021212215126.V23952@duath.fsmlabs.com>
On Thu, 2002-12-12 at 21:51, Cort Dougan wrote:
>
> Would you be able to commit them to _2_4 instead so they're not in the
> wildly divergent _2_4_devel tree? That would definitely be handy when
> trying to find where the working trees are.
>
> } The patch below adds support for IBM's Arctic-II development system,
> } based on the 405LP processor. For now this is just the core support,
> } more drivers coming soon. Are there any objections, or suggestions
> } for doing things better before I commit this to linuxppc_2_4_devel?
> }
This brings up some really good questions. I have support for three new
platforms based on the _2_4_devel tree which I'd like to get submitted
soon [so far, I've just been following along] So,
* Which tree should be best for new development/ports/etc?
* What's the best process for proposing changes? I've seen many
patches come along on this list, but it's not clear to me if/when
they made it to any particular tree.
Thanks.
--
------------------------------------------------------------
Gary Thomas |
MLB Associates | Consulting for the
+1 (970) 229-1963 | Embedded world
http://www.mlbassoc.com/ |
email: <gary@mlbassoc.com> |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-13 14:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 4:36 Support for Arctic platform (405LP based) David Gibson
2002-12-13 4:51 ` Cort Dougan
2002-12-13 14:26 ` Gary Thomas [this message]
2002-12-13 15:16 ` Tom Rini
2002-12-13 16:35 ` Tom Rini
2002-12-16 20:39 ` linuxppc-commit mailing list Hollis Blanchard
2002-12-13 15:18 ` Support for Arctic platform (405LP based) Tom Rini
2002-12-13 15:28 ` Matt Porter
2002-12-15 19:15 ` Cort Dougan
2002-12-15 19:51 ` Tom Rini
2002-12-15 23:43 ` Paul Mackerras
2002-12-16 0:41 ` Cort Dougan
2002-12-16 15:04 ` Tom Rini
2002-12-16 15:08 ` Tom Rini
2002-12-16 16:25 ` Discovery II (was Re: Support for Arctic platform (405LP based)) Roland Dreier
2002-12-16 12:45 ` Mark A. Greer
2002-12-16 19:49 ` Roland Dreier
2002-12-16 14:33 ` Mark A. Greer
2002-12-18 11:01 ` Rabeeh Khoury
2002-12-16 19:49 ` Support for Arctic platform (405LP based) Cort Dougan
2002-12-16 20:13 ` PPC Tree structures (Was, at some point: Re: Support for Arctic platform (405LP based)) Tom Rini
2002-12-16 20:13 ` Cort Dougan
2002-12-16 20:36 ` Tom Rini
2002-12-19 18:06 ` PPC Tree structures (Was, at some point: " Cort Dougan
2002-12-19 18:17 ` Tom Rini
2002-12-16 1:43 ` Support for Arctic platform (405LP based) David Gibson
2002-12-16 15:02 ` Tom Rini
2002-12-13 19:25 ` Todd Poynor
2002-12-15 7:35 ` David Gibson
2002-12-16 1:58 ` David Gibson
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=1039789562.7542.14781.camel@hermes.chez-thomas.org \
--to=gary@mlbassoc.com \
--cc=cort@fsmlabs.com \
--cc=linuxppc-embedded@lists.linuxppc.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 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).