From owner-freebsd-sparc64@FreeBSD.ORG Sun Feb 15 22:02:12 2015 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 73387D4A for ; Sun, 15 Feb 2015 22:02:12 +0000 (UTC) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "alchemy.franken.de", Issuer "alchemy.franken.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ECBEFDD9 for ; Sun, 15 Feb 2015 22:02:11 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.9/8.14.9/ALCHEMY.FRANKEN.DE) with ESMTP id t1FM28NV023109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 15 Feb 2015 23:02:08 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.9/8.14.9/Submit) id t1FM28h5023108; Sun, 15 Feb 2015 23:02:08 +0100 (CET) (envelope-from marius) Date: Sun, 15 Feb 2015 23:02:08 +0100 From: Marius Strobl To: Rob J Subject: Re: upd lite broken on sparc64 with vimage Message-ID: <20150215220208.GA23088@alchemy.franken.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (alchemy.franken.de [0.0.0.0]); Sun, 15 Feb 2015 23:02:08 +0100 (CET) Cc: freebsd-sparc64@freebsd.org X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2015 22:02:12 -0000 On Thu, Jan 22, 2015 at 02:11:27PM -0600, Rob J wrote: > Any body? May be I will ask the power-pc folks to see if they found a > solution to the same problem. This isn't a matter of the architecture, the fix simply hadn't be merged to stable/10 before. Done in r278812. Marius