LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: "Cameron, Steve" <Steve.Cameron@COMPAQ.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: tlbwe, rfci instructions and gcc cross assembler
Date: Fri, 12 Apr 2002 08:25:52 -0700	[thread overview]
Message-ID: <20020412152552.GR759@opus.bloom.county> (raw)
In-Reply-To: <45B36A38D959B44CB032DA427A6E10640167CFB2@cceexc18.americas.cpqcorp.net>


On Fri, Apr 12, 2002 at 10:10:39AM -0500, Cameron, Steve wrote:

> I'm using linuxppc_2_4.  I thought that'd be more
> stable than linuxppc_2_4_devel.  Maybe that wasn't
> such a good choice.

No, since linuxppc_2_4 doesn't have working 40x support in it.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

  reply	other threads:[~2002-04-12 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12 15:10 tlbwe, rfci instructions and gcc cross assembler Cameron, Steve
2002-04-12 15:25 ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-12 14:43 Cameron, Steve
2002-04-12 15:05 ` Tom Rini
2002-04-11 21:53 Cameron, Steve
2002-04-11 22:10 ` Tom Rini

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=20020412152552.GR759@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=Steve.Cameron@COMPAQ.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