All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Danet <odanet@caramail.com>
To: sparclinux@vger.kernel.org
Subject: Re: Time to let sun4m + sun4d RIP?
Date: Sat, 19 Apr 2014 23:31:33 +0000	[thread overview]
Message-ID: <53530755.3000507@caramail.com> (raw)
In-Reply-To: <20140419114802.GA13716@ravnborg.org>

On 19/04/2014 13:48, 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.
> 
> 	Sam

I wish Linux could keep the Sun4m port a bit longer, even if I cannot help much, I just posted a small patch last year.

There is a project for the recreation of Sun4m hardware in a FPGA : http://temlib.org.
Running current Linux kernel on this hardware could be interesting. It would also be preferable as a base for patchs to optimise
the kernel to TEMLIB's CPU which emulates legacy Sun CPUs (MicroSparc) but is not exactly identical to them
(different TLBs organisation, for example).

QEMU currently supports Sun4m quite well, despite some issues with SCSI emulation.
All operating systems can be run, except NextSTEP : Linux, *BSD, Solaris are supported.
It is now much faster than genuine Sun hardware (particulary for disk accesses !).

Regards
O.Danet


  parent reply	other threads:[~2014-04-19 23:31 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 [this message]
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
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=53530755.3000507@caramail.com \
    --to=odanet@caramail.com \
    --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.