From owner-freebsd-sparc64@freebsd.org Fri May 4 13:19:49 2018 Return-Path: Delivered-To: freebsd-sparc64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0F3DFAD71C for ; Fri, 4 May 2018 13:19:49 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 496A77947F for ; Fri, 4 May 2018 13:19:48 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 14186D20; Fri, 4 May 2018 08:19:42 -0500 (CDT) Date: Fri, 4 May 2018 08:19:41 -0500 From: Mark Linimon To: iwama@t3.rim.or.jp Cc: freebsd-sparc64@freebsd.org Subject: Re: Fire V445 support status Message-ID: <20180504131940.GA12497@lonesome.com> References: <000001d3e37e$2c1d52a0$8457f7e0$@t3.rim.or.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001d3e37e$2c1d52a0$8457f7e0$@t3.rim.or.jp> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2018 13:19:49 -0000 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