All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: Time to let sun4m + sun4d RIP?
Date: Tue, 29 Apr 2014 19:03:09 +0000	[thread overview]
Message-ID: <20140429190309.GA31920@ravnborg.org> (raw)
In-Reply-To: <20140419114802.GA13716@ravnborg.org>

On Tue, Apr 29, 2014 at 08:46:11PM +0200, Sam Ravnborg wrote:
> On Sat, Apr 19, 2014 at 01:48:02PM +0200, Sam Ravnborg wrote:
> > Hi all sparc lovers/users.
> > 
> > We all know that is is a long time ago that a sun4m or sun4d machine was produced,
> > and I wonder if there are anyone using these today.
> > The questions pops up as there are still stuff to do before the sparc32 port
> > is in good shape.
> > 
> > So the question to you guys...
> > Shall we keep support for sun4d and sun4m?
> > If yes then why?
> > 
> > LEON is in active use in several applications - so the sparc32 port is
> > as relevant as ever.
> 
> Just a fololow-up to my original question.
> 
> We still have a few brave souls running the kernels on sparc32 based boxes.
> On top of this there are templig.org that looks like a one-man show to implment
> sparc32 in VHDL. But very impressive!
> Then there are qemu that today supports sun4m - if we drop sun4m we also drop
> qemu support for sparc.
> 
> So in total there are still reasons to keep sun4m and sun4d around.
> 
> Thanks everyone for your responses!

And then I read this on LWN:
Debian drops the SPARC architecture - http://lwn.net/Articles/596663/

Which point to: https://bugs.debian.org/cgi-bin/bugreport.cgi?bugt5938

	Sam

  parent reply	other threads:[~2014-04-29 19:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 11:48 Time to let sun4m + sun4d RIP? Sam Ravnborg
2014-04-19 13:53 ` Julian Calaby
2014-04-19 14:55 ` Alan Perry
2014-04-19 18:38 ` Magnus Lindholm
2014-04-19 23:31 ` Olivier Danet
2014-04-23  1:21 ` David Miller
2014-04-23  3:49 ` Jim MacKenzie
2014-04-29 18:46 ` Sam Ravnborg
2014-04-29 19:03 ` Sam Ravnborg [this message]
2014-04-29 21:19 ` Josip Rodin
2014-05-02 10:29 ` Kaj-Michael Lang
2014-05-02 13:53 ` Julian Calaby
2014-05-06  7:04 ` Kaj-Michael Lang

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=20140429190309.GA31920@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.