All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: sparclinux@vger.kernel.org
Subject: Re: Access to older 64-bit sparcs for developers
Date: Wed, 28 Jun 2017 17:03:04 +0000	[thread overview]
Message-ID: <b889d378-ebc3-1fd6-6fff-b86e25a9797e@physik.fu-berlin.de> (raw)
In-Reply-To: <alpine.LRH.2.20.1706271559250.28262@math.ut.ee>

On 06/28/2017 06:32 PM, chase rayfield wrote:
> Testing on old hardware is important... because there are differences
> and stuff breaks. I still haven't figured out how to get an X server
> going on my Ultra45 for instance... perhaps fbdev but that is
> decidedly bleh. It's happily running Gentoo and my Homepage etc in the
> meantime...

There is currently no native display driver for these old framebuffers
as far as I know but I am happy to be corrected.

> I can provide access to just about any 32bit hardware except
> TurboSparc (working on that ;-) ), an Ultra 1E, 10, U45 and T2000, for
> anyone wanting to dork around with that as well.... on a 100/10 link.

UltraSparcs are 64 bits, not 32 bits. 32 bit SPARC is currently out of
scope as most people focus on UltraSparcs. No idea what the current
state of affairs is though. Have you tried a recent kernel on the
TurboSparc?

> I don't have a fancy setup to power cycle them at the moment though I
> can easily wire up serial consoles. I could stick a Radeon RX560 in
> the U45 if someone wants to try getting mesa + X11 acceleration
> working on Sparc64 on that specific hardware at least.

Having access to a serial console is always essential as networking
might not always work. Having remote power cycle control is even
better, although the T2000 does that through ALOM.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  parent reply	other threads:[~2017-06-28 17:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27 13:21 Access to older 64-bit sparcs for developers Meelis Roos
2017-06-27 18:42 ` David Miller
2017-06-28  8:43 ` Julian Calaby
2017-06-28  8:56 ` John Paul Adrian Glaubitz
2017-06-28 16:32 ` chase rayfield
2017-06-28 17:03 ` John Paul Adrian Glaubitz [this message]
2017-06-28 19:42 ` David Miller
2017-06-28 20:32 ` chase rayfield
2017-06-28 20:35 ` John Paul Adrian Glaubitz
2017-06-28 20:37 ` David Miller
2017-06-29  7:18 ` Mark Cave-Ayland
2017-06-29 15:23 ` David Miller
2017-06-29 19:32 ` Mark Cave-Ayland
2017-06-29 20:10 ` David Miller
2017-06-29 22:09 ` Mark Cave-Ayland
2017-06-30  0:36 ` David Miller
2017-06-30 19:06 ` Mark Cave-Ayland

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=b889d378-ebc3-1fd6-6fff-b86e25a9797e@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --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.