Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Brian Murphy <brian@murphy.dk>
Cc: Kip Walker <kwalker@broadcom.com>, linux-mips@linux-mips.org
Subject: Re: 2.5 crash on boot
Date: Wed, 2 Jul 2003 02:46:59 +0200	[thread overview]
Message-ID: <20030702004659.GA3824@linux-mips.org> (raw)
In-Reply-To: <3F01F524.8050608@murphy.dk>

On Tue, Jul 01, 2003 at 10:55:00PM +0200, Brian Murphy wrote:

> Has anyone booted 32 bit 2.5 fully into userspace?

People have done it - but degree off success greatly varies.  I'm
optimistic to have 2.5 stable enough for basic use pretty soon.

  Ralf

  reply	other threads:[~2003-07-02  0:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01 17:56 2.5 crash on boot Brian Murphy
2003-07-01 18:05 ` Kip Walker
2003-07-01 20:55   ` Brian Murphy
2003-07-02  0:46     ` Ralf Baechle [this message]
2003-07-01 21:32   ` Brian Murphy
2003-07-01 21:32     ` Brian Murphy
     [not found] ` <3F01CCAA.9050307@mac.com>
2003-07-01 20:36   ` Brian Murphy

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=20030702004659.GA3824@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=brian@murphy.dk \
    --cc=kwalker@broadcom.com \
    --cc=linux-mips@linux-mips.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