From owner-freebsd-arm@FreeBSD.ORG Mon Nov 26 21:59:52 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 13F936E7 for ; Mon, 26 Nov 2012 21:59:52 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 999928FC15 for ; Mon, 26 Nov 2012 21:59:51 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.5/8.14.5) with ESMTP id qAQLxp5G093093 for ; Mon, 26 Nov 2012 14:59:51 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id qAQLxmAX037708; Mon, 26 Nov 2012 14:59:48 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Subject: Re: Dreamplug and eSATA problems From: Ian Lepore To: Dave Hayes In-Reply-To: <50B33C7F.2040303@jetcafe.org> References: <50A150C7.2080805@jetcafe.org> <1353643442.69940.45.camel@revolution.hippie.lan> <50B33C7F.2040303@jetcafe.org> Content-Type: text/plain; charset="us-ascii" Date: Mon, 26 Nov 2012 14:59:48 -0700 Message-ID: <1353967188.69940.125.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 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 21:59:52 -0000 On Mon, 2012-11-26 at 01:55 -0800, Dave Hayes wrote: > 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? This DP has 1001 and 0301 next to the serial number on the label. My other one is 1001N and 0201. The new one has NOR flash, the 1001N had NAND. I heard from someone that only about 50 of the nand-based units were built. Considering how much it costs to layout a board, hand build some units for prototype testing, gear a whole production line up (parts placement, soldering, etc), spin a new bootloader and OS for it, all that stuff, it boggles my mind that they did 50 units then dropped that design. So all in all, I don't know what other differences it might have beyond the nand/nor flash. All the other onboard devices are the same as near as I can tell (not sure about the wifi since we don't have a driver for that). -- Ian