linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Cort Dougan <cort@fsmlabs.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Support for Arctic platform (405LP based)
Date: Fri, 13 Dec 2002 08:28:26 -0700	[thread overview]
Message-ID: <20021213082826.A7709@home.com> (raw)
In-Reply-To: <20021213151808.GI19456@opus.bloom.county>; from trini@kernel.crashing.org on Fri, Dec 13, 2002 at 08:18:08AM -0700


On Fri, Dec 13, 2002 at 08:18:08AM -0700, Tom Rini wrote:
>
> On Thu, Dec 12, 2002 at 09:51:26PM -0700, 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.
>
> One of my goals for winter break is to try and make the _devel tree less
> divergent, at least w.r.t. 'classic' PPCs.  I'm not sure if 4xx support
> is in a stage yet that Paul is happy to move it to the _2_4 tree and
> then on to Marcelo yet.

At a minimum, the 4xx DBCR handling via thread struct would need to
be finished to make Paul happy, I believe.  Luckily, I don't need
a debugger so I've had no reason to finish the task that he left
"as an exercise for the reader".

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

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

  reply	other threads:[~2002-12-13 15:28 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
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 [this message]
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=20021213082826.A7709@home.com \
    --to=porter@cox.net \
    --cc=cort@fsmlabs.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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).