public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: rob@osinvestor.com (Rob Radez)
To: Scott Robert Ladd <coyote@coyotegulch.com>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>, linux-kernel@vger.kernel.org
Subject: Re: Testing: What do you want?
Date: Mon, 24 Mar 2003 19:04:51 -0500	[thread overview]
Message-ID: <20030325000450.GA2834@osinvestor.com> (raw)
In-Reply-To: <3E7F40D0.6010202@coyotegulch.com>

On Mon, Mar 24, 2003 at 12:30:56PM -0500, Scott Robert Ladd wrote:
> Jan-Benedict Glaw wrote:
> >sparc32? If you get it to build or even to boot, please drop me a note
> >
> >Last time I looked at it, sparc32 wasn't in any good state (esp. SMP) in
> >2.5.x. This is because Dave S. Miller stopped spending a lot of hacking
> >time (he has to work for other things now and only merges patches he
> >gets sent, where he formerly did tons on active development for
> >sparc32).
> 
> I'll let you know about whether it works or not. What you tell me about 
> SPARC support, however, does not bode well. I was about to say "I'm 
> surprised that Sun isn't providing any support" -- then my senses 
> returned, and I realized I'm not surprised in the least.

I just wanted to let y'all know that I've been trying to keep an
up-to-date status page for sparc32 at http://osinvestor.com/sparc/ with
basic information on 2.4 and 2.5 compiling and booting (or not as may
be.)

And yes, 2.5.65 builds and boots UP on sparc32, for me at least.  SMP is
badly broken.

Regards,
Rob Radez

  reply	other threads:[~2003-03-25  0:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 14:46 Testing: What do you want? Scott Robert Ladd
2003-03-24 15:39 ` Jan-Benedict Glaw
2003-03-24 17:30   ` Scott Robert Ladd
2003-03-25  0:04     ` Rob Radez [this message]
2003-03-25 17:50       ` Craig Thomas
2003-03-24 17:01 ` Alan Cox
2003-03-24 23:06   ` Craig Thomas
2003-03-25  0:16     ` Jörn Engel
2003-03-25 14:18       ` Scott Robert Ladd
2003-03-25 14:18       ` Scott Robert Ladd

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=20030325000450.GA2834@osinvestor.com \
    --to=rob@osinvestor.com \
    --cc=coyote@coyotegulch.com \
    --cc=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.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