From owner-freebsd-arm@FreeBSD.ORG Fri Dec 18 13:23:10 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83D731065670 for ; Fri, 18 Dec 2009 13:23:10 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 63A218FC18 for ; Fri, 18 Dec 2009 13:23:10 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NLcnV-00031X-QQ for freebsd-arm@freebsd.org; Fri, 18 Dec 2009 05:23:09 -0800 Message-ID: <26843206.post@talk.nabble.com> Date: Fri, 18 Dec 2009 05:23:09 -0800 (PST) From: RuiDC To: freebsd-arm@freebsd.org In-Reply-To: <1284BB72-0FAC-49E4-86FB-D44D9FD630B0@semihalf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ruidc@yahoo.com References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> <26811801.post@talk.nabble.com> <4B28FF6F.4090601@semihalf.com> <26813898.post@talk.nabble.com> <1284BB72-0FAC-49E4-86FB-D44D9FD630B0@semihalf.com> Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 13:23:10 -0000 Rafal Jaworowski wrote: > > From our investigations back then disabling clustering should suffice, > forcing sync operation is a bigger hammer (against performance). > ok, i'll try with that initially Rafal Jaworowski wrote: > > It seems loader.conf and .4th are not hooked up to the ARM install > scripting/makefile; they are not required to get the loader initially > working, but you can copy them from i386 world if needed. > I notice some i386 specific "if" statements in .4th, but do not have anywhere near enough knowledge to understand what this is for, but will try this shortly and post back. Rafal Jaworowski wrote: > > Note that running ubldr on ARM requires the underlying U-Boot to be > compiled with CONFIG_API option enabled, which is only available in main > line U-Boot since ver. 1.3.2; what is your version? > I'm running freebsd kernel.bin from usb & FAT32 using: fatload usb 0:1 900000 kernel.bin go 900000 I've read your notes from http://www.bsdcan.org/2008/schedule/attachments/49_2008_uboot_freebsd.pdf but don't understand the implications of the alternative boot methods, but from reading that, I presume the note on ubldr is not relevant to me? Or will switching methods enable me to work around this problem? I'm running the Sheevaplug installer version, which is Marvell's version 3.4.19 which is based on 1.1.4. I'm reluctant to switch to Marvell's Open-Uboot stack due to reported problems here: http://plugcomputer.org/plugforum/index.php?topic=975.0 -- View this message in context: http://old.nabble.com/problem-setting-up-ports-tp26803523p26843206.html Sent from the freebsd-arm mailing list archive at Nabble.com.