public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: John Bradford <john@grabjohn.com>
Cc: Markus Pfeiffer <profmakx@profmakx.org>,
	sam@ravnborg.org, lm@work.bitmover.com, mail@hannes-reinecke.de,
	linux-kernel@vger.kernel.org
Subject: Re: Sparc port still maintained in 2.5
Date: Mon, 30 Dec 2002 16:43:42 -0200	[thread overview]
Message-ID: <20021230184342.GE3143@conectiva.com.br> (raw)
In-Reply-To: <200212301827.gBUIRgPH002681@darkstar.example.net>

Em Mon, Dec 30, 2002 at 06:27:42PM +0000, John Bradford escreveu:
> > > > I have a spare Alpha box (in theory I made need it some day if we ever
> > > > decide to support Tru64 but that seems like a small market).  I don't
> > > > know how useful it is but I could put it up outside our firewall if
> > > > that helped.  I'd have to install Linux on it and I'm booked up until
> > > > Jan 9th but if you still need it then let me know.
> > >
> > > Hi Larry, nice offer. But I personally would not have time hacking on
> > > Alpha. Others may find it usefull though.
> > >
> > 
> > Well, I have an Alpha System here myself and am also "hacking" on
> > it. But one has also to ask oneself if there is any demand (apart
> > from my personal demand) for a maintained Linux/Alpha >= 2.5...
 
> I'm certainly going to be interested in Linux/Sparc >= 2.5 when I can get a
> Sparc machine, (I'm hoping to help work on the 'Splack' distribution, which
> is basically an un-official Slackware-like distribution for Sparcs), with the

I'm doing the same for Conectiva Linux, the package recompilation is almost
done :-) But for now I'm using 2.4.20, with some oopses (similar to some
already reported on the sparclinux@vger.kernel.org mailing list that I already
reported to Uzi). 2.5-bk compiles and boots, but I couldn't access the machine
as serial console is not working and I only have a SS10 headless machine, I
plan to look into some of these issues when (if) I find time.

> eventual aim of moving from X86 to Sparc as my default architechture, but I'm
> not really interested in Alpha.
 
> What's the status of the 2.5 Sparc tree?

Zaitcev has sent an status some time ago:

http://marc.theaimsgroup.com/?l=linux-sparc&m=103895559102210&w=2

- Arnaldo

  reply	other threads:[~2002-12-30 18:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-30 15:07 Alpha port still maintained in 2.5 Hannes Reinecke
2002-12-30 15:15 ` Sam Ravnborg
2002-12-30 15:23   ` Larry McVoy
2002-12-30 16:50     ` Sam Ravnborg
2002-12-30 18:13       ` Markus Pfeiffer
2002-12-30 18:16         ` William Lee Irwin III
2002-12-30 18:20         ` Jochen Friedrich
2002-12-30 18:52           ` Larry McVoy
2002-12-30 19:37           ` Hannes Reinecke
2002-12-30 18:27         ` Sparc " John Bradford
2002-12-30 18:43           ` Arnaldo Carvalho de Melo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-30 18:48 Holzrichter, Bruce

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=20021230184342.GE3143@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@work.bitmover.com \
    --cc=mail@hannes-reinecke.de \
    --cc=profmakx@profmakx.org \
    --cc=sam@ravnborg.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