Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 5 May 2018 05:59:41 +0900
From:      <iwama@t3.rim.or.jp>
To:        "'Mark Linimon'" <linimon@lonesome.com>
Cc:        <freebsd-sparc64@freebsd.org>
Subject:   RE: Fire V445 support status
Message-ID:  <000001d3e3ea$d2ca92e0$785fb8a0$@t3.rim.or.jp>
In-Reply-To: <20180504131940.GA12497@lonesome.com>
References:  <000001d3e37e$2c1d52a0$8457f7e0$@t3.rim.or.jp> <20180504131940.GA12497@lonesome.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi mcl,

  Thank you for your reply.

  Actually, I also thought that V445 would work without problems as FreeBSD 
supports V125 and V245 as well as you. I have other choices but I believe it
is 
best to use ZFS on FreeBSD to make effective use of the eight disks of V445.
  This problem is more troublesome as I think it is much more difficult than

when I did send PR about Ultra 30(218478). I will try a little more hints
for 
solution.
---
Yoshihiko Iwama

-----Original Message-----
From: Mark Linimon <linimon@lonesome.com> 
Sent: Friday, May 4, 2018 10:20 PM
To: iwama@t3.rim.or.jp
Cc: freebsd-sparc64@freebsd.org
Subject: Re: Fire V445 support status

All that I can offer is that I have run 10.3 and 11.0 on V215s and V245s.
I had assumed that they were similar.

Although a few developers do work on sparc64, unfortunately there is little
support for it in general in the FreeBSD developer community.
I used to do package builds but have not during this year so far.

I am afraid we are in a shrinking minority.

mcl




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000001d3e3ea$d2ca92e0$785fb8a0$>