From owner-freebsd-arm@FreeBSD.ORG Mon Nov 26 10:02:51 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15582CB8 for ; Mon, 26 Nov 2012 10:02:51 +0000 (UTC) (envelope-from dave@jetcafe.org) Received: from nahkohe.jetcafe.org (nahkohe.jetcafe.org [205.147.26.32]) by mx1.freebsd.org (Postfix) with ESMTP id E5A768FC08 for ; Mon, 26 Nov 2012 10:02:50 +0000 (UTC) X-Envelope-To: freebsd-arm@freebsd.org Received: from [205.147.26.5] (hokkshideh4.jetcafe.org [205.147.26.5]) by nahkohe.jetcafe.org (8.14.2/8.14.2) with ESMTP id qAQ9tBUF067202 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Nov 2012 01:55:11 -0800 (PST) Message-ID: <50B33C7F.2040303@jetcafe.org> Date: Mon, 26 Nov 2012 01:55:11 -0800 From: Dave Hayes User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120612 Thunderbird/13.0 MIME-Version: 1.0 To: Ian Lepore Subject: Re: Dreamplug and eSATA problems References: <50A150C7.2080805@jetcafe.org> <1353643442.69940.45.camel@revolution.hippie.lan> In-Reply-To: <1353643442.69940.45.camel@revolution.hippie.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 10:02:51 -0000 On 11/22/12 20:04, Ian Lepore wrote: > It'll be a while before I can get back to this and start tracking down > the point at which the problem went away in -current. If you want a > quick workaround for now, the attached patch will set the data cache to > writethrough (the performance hit isn't as bad as you'd think). Thank you! This appears to work fine; I've built several ports including Perl, and they appear to work. Usually if a machine can build ports, it's got fairly solid hardware. As to a performance hit, I'm not really informed enough about the arm architecture to notice. This is the first I've been able to really use this box, so I'm considering that enough for now. Fairly soon I will be doing some network performance tests between the two network interfaces, so maybe the performance issue will show up when that test happens. How new is your DP? I understand the hardware has changed again; I may need to get another one of these so I'm curious when that change occurred? -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< A man who was handsome, intelligent, and elegant, was asked who he was. "I am the Devil", he replied. "But that cannot be," said the questioner, "for the Devil is evil and ugly!" "My friend," was the reply, "you have been listening to my detractors."