From owner-freebsd-arm@FreeBSD.ORG Sat Dec 19 07:30:58 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 66BFF10656A7 for ; Sat, 19 Dec 2009 07:30:58 +0000 (UTC) (envelope-from toshi@ruby.ocn.ne.jp) Received: from smtp.ruby.ocn.ne.jp (ruby.ocn.ne.jp [61.207.12.164]) by mx1.freebsd.org (Postfix) with ESMTP id CE7F08FC0A for ; Sat, 19 Dec 2009 07:30:57 +0000 (UTC) Received: from localhost (p6194-ipadfx01sizuokaden.shizuoka.ocn.ne.jp [219.160.179.194]) by smtp.ruby.ocn.ne.jp (Postfix) with ESMTP id BBCC62C52; Sat, 19 Dec 2009 16:30:55 +0900 (JST) Date: Sat, 19 Dec 2009 16:30:55 +0900 (JST) Message-Id: <20091219.163055.193684234.toshi@ruby.ocn.ne.jp> To: freebsd-arm@freebsd.org From: SAITOU Toshihide In-Reply-To: <26846376.post@talk.nabble.com> References: <1284BB72-0FAC-49E4-86FB-D44D9FD630B0@semihalf.com> <26843206.post@talk.nabble.com> <26846376.post@talk.nabble.com> X-GPG-fingerprint: 34B3 0B6A 8520 F5B0 EBC7 69F6 C055 9F8A 0D49 F8FC X-Mailer: Mew version 6.2.51 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: fetch data corruption on local fs [SOLVED] 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: Sat, 19 Dec 2009 07:30:58 -0000 From: RuiDC Subject: Re: fetch data corruption on local fs [SOLVED] Date: Fri, 18 Dec 2009 09:00:00 -0800 (PST) > 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 It seems the patches are already mainlined. http://www.plugcomputer.org/plugwiki/index.php/Das_U-boot_plug_support So, Has anyone success to build the Open U-Boot with CONFIG_API and booting ubldr? > I'm still curious to learn more about the implications of alternative boot > methods if anyone can point me in the right direction. > > Thanks again! > RuiDC SAITOU Toshihide