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 08:56:30 +0000 [thread overview]
Message-ID: <20170628085540.GB25072@physik.fu-berlin.de> (raw)
In-Reply-To: <alpine.LRH.2.20.1706271559250.28262@math.ut.ee>
On Tue, Jun 27, 2017 at 04:21:16PM +0300, Meelis Roos wrote:
> I have most of my sparclinux testbed in DMZ-s and I can make them
> available to any developers who want it, along with root access and
> built in management (if any).
FWIW, we have more modern hardware available to external developers in
Debian. There is one SPARC-T5 running Debian unstable (sparc64) inside
an LDOM and a Sun Fire T2000 that are available.
I have already provided access to QEMU upstream, glibc upstream, Free
Pascal upstream and others that I forgot. The FPC people, for example,
already made great progress on adding sparc64 support to their
compiler ;).
So, if anyone needs faster sparc64 hardware running a current version
of Linux for testing, please let me know.
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
next prev parent reply other threads:[~2017-06-28 8:56 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 [this message]
2017-06-28 16:32 ` chase rayfield
2017-06-28 17:03 ` John Paul Adrian Glaubitz
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=20170628085540.GB25072@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.