All of lore.kernel.org
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: sparclinux@vger.kernel.org
Subject: Access to older 64-bit sparcs for developers
Date: Tue, 27 Jun 2017 13:21:16 +0000	[thread overview]
Message-ID: <alpine.LRH.2.20.1706271559250.28262@math.ut.ee> (raw)

I see a lot of new development activity on sparclinux, that is great.

I also see different views on supporting older hardware on current 
kernels, and testing on old ultrasparcs seens to be one of the issues.

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).

Site 1: Ultra 1 143 MHz and Blade 100.

Third one is slowly rotating between E3500/E250/E450 because of power 
constraints so it is not stable at the moment.

Site 2: Ultra 2 (2x400), E220R (2 CPUs), T1-105, T1-200, V120, V210, 
V240, V440, V245, T1000, T2000, T5120.

I can add Netra X1 and V100 with some effort (relocating to the DMZ).

Planning to set up and add V445, T5140, E280R, Blade 1500.

In the queue of getting fixed (or rebuilt from parts of multiple 
machines): U5, U10, Blade 150, E3000, E3800, V480, V880, Netra T2000, 
Netra T5220 and Netra 240. These are all future stuff but if there is 
any recommendation on order of these, I might reshuffle them.

Remote managenet access is also possible for the machines that have a 
RSC/LOM/ALOM. For the machines that are without hardware management 
interface, restart is possible in site 2, site 1 is slow with respect to 
hands-on.

Both sites are behind IPv4 NAT and have native IPv6, so for IPv4 access, 
SSH through the gateway is needed and that requires key based access.

Please refer to ther prtconf repo for sample configs of the models, to 
see what CPUs and OF stuff there are (most models have a fixed CPU 
family but not all).

-- 
Meelis Roos (mroos@linux.ee)

             reply	other threads:[~2017-06-27 13:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27 13:21 Meelis Roos [this message]
2017-06-27 18:42 ` Access to older 64-bit sparcs for developers 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
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=alpine.LRH.2.20.1706271559250.28262@math.ut.ee \
    --to=mroos@linux.ee \
    --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.