From owner-freebsd-arm@FreeBSD.ORG Sun Feb 21 21:28:20 2010 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 3339C1065672 for ; Sun, 21 Feb 2010 21:28:20 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id B751D8FC12 for ; Sun, 21 Feb 2010 21:28:19 +0000 (UTC) Received: (qmail 26858 invoked by uid 399); 21 Feb 2010 21:01:37 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 21 Feb 2010 21:01:37 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B819F21.70907@FreeBSD.org> Date: Sun, 21 Feb 2010 13:01:21 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.7) Gecko/20100218 Thunderbird/3.0.1 MIME-Version: 1.0 To: Olivier Houchard , freebsd-arm@FreeBSD.org References: <20100221152824.GA58060@ci0.org> In-Reply-To: <20100221152824.GA58060@ci0.org> X-Enigmail-Version: 1.0.1 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: bind on arm 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: Sun, 21 Feb 2010 21:28:20 -0000 On 02/21/10 07:28, Olivier Houchard wrote: > Hi Doug, > > I'd like to get the attached patch committed. It fixes the bind arm atomic > stuff in -CURRENT and RELENG_8. Some times ago, the RAS address was changed, > but it was hardcoded in the bind code and the change was never reflected. > The patch uses a macro, so that even if it happens again it won't be a problem. First question (and I think the answer is yes, but I need to double-check) is it the consensus of the ARM gurus that this is the right solution? Second question, is this solution something that I can send upstream, both in the sense that I have permission to do so, and that it would be generally applicable to ARM on other OSs? Thanks, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-arm@FreeBSD.ORG Sun Feb 21 21:46:17 2010 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 B7A23106566B; Sun, 21 Feb 2010 21:46:17 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 62C768FC15; Sun, 21 Feb 2010 21:46:17 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id 3A2E1C42D9; Sun, 21 Feb 2010 22:48:17 +0100 (CET) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id dWYufPzL25GT; Sun, 21 Feb 2010 22:48:16 +0100 (CET) Received: from [192.168.133.14] (nat3-102.ghnet.pl [91.150.222.102]) by smtp.semihalf.com (Postfix) with ESMTPSA id 9500AC42D3; Sun, 21 Feb 2010 22:48:16 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Rafal Jaworowski In-Reply-To: <4B819F21.70907@FreeBSD.org> Date: Sun, 21 Feb 2010 22:46:14 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20100221152824.GA58060@ci0.org> <4B819F21.70907@FreeBSD.org> To: Doug Barton X-Mailer: Apple Mail (2.1077) Cc: freebsd-arm@FreeBSD.org, Olivier Houchard Subject: Re: bind on arm 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: Sun, 21 Feb 2010 21:46:17 -0000 On 2010-02-21, at 22:01, Doug Barton wrote: > On 02/21/10 07:28, Olivier Houchard wrote: >> Hi Doug, >>=20 >> I'd like to get the attached patch committed. It fixes the bind arm = atomic >> stuff in -CURRENT and RELENG_8. Some times ago, the RAS address was = changed, >> but it was hardcoded in the bind code and the change was never = reflected. >> The patch uses a macro, so that even if it happens again it won't be = a problem. >=20 > First question (and I think the answer is yes, but I need to > double-check) is it the consensus of the ARM gurus that this is the > right solution? Second question, is this solution something that I can > send upstream, both in the sense that I have permission to do so, and > that it would be generally applicable to ARM on other OSs? I believe the desired direction here is to make the cmpxchg atomic op a = CPU-level routine, rather than it being part of the application code. = I'm not sure what is a wider context of such a change for BIND or = whether this code is FreeBSD-only, but I thought the posted changes were = just a quick fix to verify that we have a problem around RAS, and = there's more insight needed before considering it a final fix. Rafal From owner-freebsd-arm@FreeBSD.ORG Sun Feb 21 22:27:03 2010 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 0CB81106566B; Sun, 21 Feb 2010 22:27:03 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id A4F0E8FC1C; Sun, 21 Feb 2010 22:27:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o1LMP7HZ015742; Sun, 21 Feb 2010 15:25:07 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 21 Feb 2010 15:25:18 -0700 (MST) Message-Id: <20100221.152518.366306193186912981.imp@bsdimp.com> To: dougb@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <4B819F21.70907@FreeBSD.org> References: <20100221152824.GA58060@ci0.org> <4B819F21.70907@FreeBSD.org> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org, cognet@ci0.org Subject: Re: bind on arm 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: Sun, 21 Feb 2010 22:27:03 -0000 In message: <4B819F21.70907@FreeBSD.org> Doug Barton writes: : On 02/21/10 07:28, Olivier Houchard wrote: : > Hi Doug, : > : > I'd like to get the attached patch committed. It fixes the bind arm atomic : > stuff in -CURRENT and RELENG_8. Some times ago, the RAS address was changed, : > but it was hardcoded in the bind code and the change was never reflected. : > The patch uses a macro, so that even if it happens again it won't be a problem. : : First question (and I think the answer is yes, but I need to : double-check) is it the consensus of the ARM gurus that this is the : right solution? Second question, is this solution something that I can : send upstream, both in the sense that I have permission to do so, and : that it would be generally applicable to ARM on other OSs? The patch isn't quite right yet. First, there are no atomic operations on ARM ISA (prior to some of the really recent ones that we don't yet have support in our binutils for). In order to get atomic operations to work right, you have to have some variation of RAS (restartable atomic sequences). RAS is OS specific, as there's no standards what-so-ever for it. These sequences will generate atomic operations, but only if the OS restarts them if the OS preempts the thread. The code that's there now is very FreeBSD specific. In fact, it is explicitly tagged as such in the source. These patches don't change that. The code broke because we moved the RAS scratchpad area between revisions of FreeBSD. I think between 7 and 8, but I've not done the software archeology to be sure. At the very least, the code should be ifdef'd for the RAS address. Sadly, neither version exported the RAS constant in any useful way. While it is true it would be nicer of the application used FreeBSD atomic operations in the same way that all other applications do, this isn't easy in the case of Bind. Bind defined its own set of atomic operations, and all the other architectures conformed to bind's usage. On most other platforms, the atomic operations aren't OS dependent, just CPU dependent, so there wasn't a problem with Bind defining its own. After all, atomic operations haven't been standardized and there's a number of different ways to skin this cat. The fanciest way to cope would be to have a run-time check to see which address to use. This likely isn't worth the bother since the user base is still relatively small (and none of the other atomics do this). The next best approach would be to include and use the value defined there for ARM_RAS_START and ARM_RAS_END. Again, I've not double checked to make sure they are defined before, but I think they are (or at least if they aren't defined, we know to use the old value). Warner From owner-freebsd-arm@FreeBSD.ORG Sun Feb 21 23:54:06 2010 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 D42BF106568D; Sun, 21 Feb 2010 23:54:05 +0000 (UTC) (envelope-from doginou@kanar.ci0.org) Received: from kanar.ci0.org (unknown [IPv6:2a01:e0b:1:50:40:63ff:feea:93a]) by mx1.freebsd.org (Postfix) with ESMTP id 726B28FC1A; Sun, 21 Feb 2010 23:54:04 +0000 (UTC) Received: from kanar.ci0.org (pluxor@localhost [127.0.0.1]) by kanar.ci0.org (8.14.2/8.14.3) with ESMTP id o1LNs8gP065353; Mon, 22 Feb 2010 00:54:08 +0100 (CET) (envelope-from doginou@kanar.ci0.org) Received: (from doginou@localhost) by kanar.ci0.org (8.14.2/8.14.3/Submit) id o1LNs8cP065352; Mon, 22 Feb 2010 00:54:08 +0100 (CET) (envelope-from doginou) Date: Mon, 22 Feb 2010 00:54:08 +0100 From: Olivier Houchard To: "M. Warner Losh" Message-ID: <20100221235408.GA65302@ci0.org> References: <20100221152824.GA58060@ci0.org> <4B819F21.70907@FreeBSD.org> <20100221.152518.366306193186912981.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100221.152518.366306193186912981.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-arm@FreeBSD.org, dougb@FreeBSD.org Subject: Re: bind on arm 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: Sun, 21 Feb 2010 23:54:06 -0000 On Sun, Feb 21, 2010 at 03:25:18PM -0700, M. Warner Losh wrote: > In message: <4B819F21.70907@FreeBSD.org> > Doug Barton writes: > : On 02/21/10 07:28, Olivier Houchard wrote: > : > Hi Doug, > : > > : > I'd like to get the attached patch committed. It fixes the bind arm atomic > : > stuff in -CURRENT and RELENG_8. Some times ago, the RAS address was changed, > : > but it was hardcoded in the bind code and the change was never reflected. > : > The patch uses a macro, so that even if it happens again it won't be a problem. > : > : First question (and I think the answer is yes, but I need to > : double-check) is it the consensus of the ARM gurus that this is the > : right solution? Second question, is this solution something that I can > : send upstream, both in the sense that I have permission to do so, and > : that it would be generally applicable to ARM on other OSs? > > The fanciest way to cope would be to have a run-time check to see > which address to use. This likely isn't worth the bother since the > user base is still relatively small (and none of the other atomics do > this). The next best approach would be to include > and use the value defined there for ARM_RAS_START and ARM_RAS_END. > Again, I've not double checked to make sure they are defined before, > but I think they are (or at least if they aren't defined, we know to > use the old value). > Actually, the patch I sent Doug does just that, it uses ARM_RAS_START (because it includes machine/atomic.h, which includes machine/sysarch.h). It should work for 7 as well, as ARM_RAS_START was defined too (but in machine/atomic.h) Regards, Olivier From owner-freebsd-arm@FreeBSD.ORG Sun Feb 21 23:59:32 2010 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 6ECFC106566B; Sun, 21 Feb 2010 23:59:32 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id E81A38FC12; Sun, 21 Feb 2010 23:59:31 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o1LNxPH4084220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 22 Feb 2010 00:59:25 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.3/8.14.3) with ESMTP id o1LNxHSu040966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Feb 2010 00:59:17 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o1LNxHfR008012; Mon, 22 Feb 2010 00:59:17 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o1LNxEhv008011; Mon, 22 Feb 2010 00:59:14 +0100 (CET) (envelope-from ticso) Date: Mon, 22 Feb 2010 00:59:14 +0100 From: Bernd Walter To: Olivier Houchard Message-ID: <20100221235914.GE43625@cicely7.cicely.de> References: <20100221152824.GA58060@ci0.org> <4B819F21.70907@FreeBSD.org> <20100221.152518.366306193186912981.imp@bsdimp.com> <20100221235408.GA65302@ci0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100221235408.GA65302@ci0.org> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: freebsd-arm@freebsd.org, dougb@freebsd.org Subject: Re: bind on arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Feb 2010 23:59:32 -0000 On Mon, Feb 22, 2010 at 12:54:08AM +0100, Olivier Houchard wrote: > On Sun, Feb 21, 2010 at 03:25:18PM -0700, M. Warner Losh wrote: > > In message: <4B819F21.70907@FreeBSD.org> > > Doug Barton writes: > > : On 02/21/10 07:28, Olivier Houchard wrote: > > : > Hi Doug, > > : > > > : > I'd like to get the attached patch committed. It fixes the bind arm atomic > > : > stuff in -CURRENT and RELENG_8. Some times ago, the RAS address was changed, > > : > but it was hardcoded in the bind code and the change was never reflected. > > : > The patch uses a macro, so that even if it happens again it won't be a problem. > > : > > : First question (and I think the answer is yes, but I need to > > : double-check) is it the consensus of the ARM gurus that this is the > > : right solution? Second question, is this solution something that I can > > : send upstream, both in the sense that I have permission to do so, and > > : that it would be generally applicable to ARM on other OSs? > > > > The fanciest way to cope would be to have a run-time check to see > > which address to use. This likely isn't worth the bother since the > > user base is still relatively small (and none of the other atomics do > > this). The next best approach would be to include > > and use the value defined there for ARM_RAS_START and ARM_RAS_END. > > Again, I've not double checked to make sure they are defined before, > > but I think they are (or at least if they aren't defined, we know to > > use the old value). > > > > Actually, the patch I sent Doug does just that, it uses ARM_RAS_START > (because it includes machine/atomic.h, which includes machine/sysarch.h). > It should work for 7 as well, as ARM_RAS_START was defined too (but in > machine/atomic.h) I'm also running a 7.0-CURRENT system and can do a test if required. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Mon Feb 22 00:10:51 2010 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 63E24106566C; Mon, 22 Feb 2010 00:10:51 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 248CF8FC12; Mon, 22 Feb 2010 00:10:51 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o1M06H20016655; Sun, 21 Feb 2010 17:06:17 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 21 Feb 2010 17:06:28 -0700 (MST) Message-Id: <20100221.170628.163350101932654503.imp@bsdimp.com> To: cognet@ci0.org From: "M. Warner Losh" In-Reply-To: <20100221235408.GA65302@ci0.org> References: <4B819F21.70907@FreeBSD.org> <20100221.152518.366306193186912981.imp@bsdimp.com> <20100221235408.GA65302@ci0.org> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org, dougb@freebsd.org Subject: Re: bind on arm 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: Mon, 22 Feb 2010 00:10:51 -0000 In message: <20100221235408.GA65302@ci0.org> Olivier Houchard writes: : On Sun, Feb 21, 2010 at 03:25:18PM -0700, M. Warner Losh wrote: : > In message: <4B819F21.70907@FreeBSD.org> : > Doug Barton writes: : > : On 02/21/10 07:28, Olivier Houchard wrote: : > : > Hi Doug, : > : > : > : > I'd like to get the attached patch committed. It fixes the bind arm atomic : > : > stuff in -CURRENT and RELENG_8. Some times ago, the RAS address was changed, : > : > but it was hardcoded in the bind code and the change was never reflected. : > : > The patch uses a macro, so that even if it happens again it won't be a problem. : > : : > : First question (and I think the answer is yes, but I need to : > : double-check) is it the consensus of the ARM gurus that this is the : > : right solution? Second question, is this solution something that I can : > : send upstream, both in the sense that I have permission to do so, and : > : that it would be generally applicable to ARM on other OSs? : > : > The fanciest way to cope would be to have a run-time check to see : > which address to use. This likely isn't worth the bother since the : > user base is still relatively small (and none of the other atomics do : > this). The next best approach would be to include : > and use the value defined there for ARM_RAS_START and ARM_RAS_END. : > Again, I've not double checked to make sure they are defined before, : > but I think they are (or at least if they aren't defined, we know to : > use the old value). : > : : Actually, the patch I sent Doug does just that, it uses ARM_RAS_START : (because it includes machine/atomic.h, which includes machine/sysarch.h). : It should work for 7 as well, as ARM_RAS_START was defined too (but in : machine/atomic.h) Hmmm, missed that part of it... Then yes, it is ready to go. Warner From owner-freebsd-arm@FreeBSD.ORG Mon Feb 22 11:06:53 2010 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 D1504106566B for ; Mon, 22 Feb 2010 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C053F8FC1D for ; Mon, 22 Feb 2010 11:06:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id o1MB6r2k039638 for ; Mon, 22 Feb 2010 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o1MB6reJ039636 for freebsd-arm@FreeBSD.org; Mon, 22 Feb 2010 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 22 Feb 2010 11:06:53 GMT Message-Id: <201002221106.o1MB6reJ039636@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-arm@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-arm@FreeBSD.org 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: Mon, 22 Feb 2010 11:06:53 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o arm/134368 arm [patch] nslu2_led driver for the LEDs on the NSLU2 o arm/134338 arm [patch] Lock GPIO accesses on ixp425 o arm/134092 arm [patch] NSLU.hints contains wrong hints for on board n 3 problems total. From owner-freebsd-arm@FreeBSD.ORG Mon Feb 22 22:30:30 2010 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 7660B1065694; Mon, 22 Feb 2010 22:30:30 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 4709F8FC1A; Mon, 22 Feb 2010 22:30:30 +0000 (UTC) Received: from compute2.internal (compute2 [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 668B3E16D6; Mon, 22 Feb 2010 17:30:29 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 22 Feb 2010 17:30:29 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:from:to:cc:subject:message-id:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=smtpout; bh=fj0KjfT21wQB6U5xzk9SSXO9amM=; b=uvgojQEEP461xsPI07t/jxGxa6qD/Qypy7qf4MPlYKg2KuchLyh7NU36wFt5AfXSPOq557F8fhPdkKMsnM/t9ueQiII2WwynCVzLZSW78UexMd8VTwc5vaYpPfjNb6BLHeb8d7IHeHwNWqJ/VD0lALSoYAZpEntbjlLSGhbf0HA= X-Sasl-enc: o2zp/OY/dI1uS7Er85q4uASBDuZSiXYnCzWc8w/NoVhS 1266877828 Received: from localhost (unknown [202.6.116.238]) by mail.messagingengine.com (Postfix) with ESMTPA id 0A8384BBA19; Mon, 22 Feb 2010 17:30:27 -0500 (EST) Date: Tue, 23 Feb 2010 11:30:33 +1300 From: Andrew Turner To: "M. Warner Losh" Message-ID: <20100223113033.7803a8fe@fubar.geek.nz> In-Reply-To: <20100212.095104.655406241961872938.imp@bsdimp.com> References: <20100211223402.621a8c89@fubar.geek.nz> <4B7409B2.3040107@freebsd.org> <20100212151043.2e62ca78@fubar.geek.nz> <20100212.095104.655406241961872938.imp@bsdimp.com> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.7; amd64-portbld-freebsd8.0) X-Pirate: Arrrr Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org, rpaulo@FreeBSD.org Subject: Re: New S3C24x0 patch 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: Mon, 22 Feb 2010 22:30:30 -0000 On Fri, 12 Feb 2010 09:51:04 -0700 (MST) "M. Warner Losh" wrote: > Hey Andrew, > > These patches look better. They are looking pretty good, but I'd like > a few days to look them over and comment on them. There's a number of > little things I'd like to see fixed and maybe one or two big things > (or maybe not, I just need to think through some of the stuff I saw). Hi Warner, I'm checking on the status of this. Is there anything that I need to fix for the patch to be accepted? Andrew From owner-freebsd-arm@FreeBSD.ORG Mon Feb 22 23:09:45 2010 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 47128106566B; Mon, 22 Feb 2010 23:09:45 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 0A2AD8FC0A; Mon, 22 Feb 2010 23:09:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o1MN02v9030601; Mon, 22 Feb 2010 16:00:02 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 22 Feb 2010 16:00:10 -0700 (MST) Message-Id: <20100222.160010.460114267390213937.imp@bsdimp.com> To: andrew@fubar.geek.nz From: "M. Warner Losh" In-Reply-To: <20100223113033.7803a8fe@fubar.geek.nz> References: <20100212151043.2e62ca78@fubar.geek.nz> <20100212.095104.655406241961872938.imp@bsdimp.com> <20100223113033.7803a8fe@fubar.geek.nz> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org Subject: Re: New S3C24x0 patch 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: Mon, 22 Feb 2010 23:09:45 -0000 In message: <20100223113033.7803a8fe@fubar.geek.nz> Andrew Turner writes: : On Fri, 12 Feb 2010 09:51:04 -0700 (MST) : "M. Warner Losh" wrote: : > Hey Andrew, : > : > These patches look better. They are looking pretty good, but I'd like : > a few days to look them over and comment on them. There's a number of : > little things I'd like to see fixed and maybe one or two big things : > (or maybe not, I just need to think through some of the stuff I saw). : : Hi Warner, : : I'm checking on the status of this. Is there anything that I need to : fix for the patch to be accepted? Keep nagging me :) I'll write up a review this week. Warner From owner-freebsd-arm@FreeBSD.ORG Tue Feb 23 12:00:51 2010 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 5F548106568B for ; Tue, 23 Feb 2010 12:00:51 +0000 (UTC) (envelope-from matthias.rampke@googlemail.com) Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com [209.85.218.216]) by mx1.freebsd.org (Postfix) with ESMTP id E7D498FC08 for ; Tue, 23 Feb 2010 12:00:50 +0000 (UTC) Received: by bwz8 with SMTP id 8so2617654bwz.3 for ; Tue, 23 Feb 2010 04:00:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=+u+U35DmsTMQXoL/1A9pgwhZNzG/M0Chbu87Fec0Amk=; b=VV/dlfVLzIAX9S8uIMI8f4qiGZkESbN0EUpb4sYK4FDOFPHIPrNK873juYIhA4giS8 8fsy958CMo7E5ed+SNMprdBv2XDP5WtQVB4KoSLBzYuLKTfZGMBluuEAkaHc669Q8FYp Q19H7iogK4GVSnNO3wzJSH73BbWBLLMtXOwKA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=HGhXV6dQsvCdeVz3sygUsphOutqGV4mojKH48+leNupXaHF48YR/pO8BltLeKwQFaH leEQOtH35PUUfyIkQrCpBxJVz5rb/oO5Wlskh+QZhgvmkci/wIivWbYf+Rxmyv4UqEEo rYFM7PN/nyO4w9qbMd5PYVm5L/pGYU7VOxZEc= MIME-Version: 1.0 Sender: matthias.rampke@googlemail.com Received: by 10.204.48.144 with SMTP id r16mr1602983bkf.176.1266924883399; Tue, 23 Feb 2010 03:34:43 -0800 (PST) From: Matthias Rampke Date: Tue, 23 Feb 2010 12:34:23 +0100 X-Google-Sender-Auth: 3a3a8257c5d9b9d4 Message-ID: <31d643301002230334h17c03d0dg9f61b4ed9ae6724b@mail.gmail.com> To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: What is the state of FreeBSD on the SheevaPlug? 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: Tue, 23 Feb 2010 12:00:51 -0000 Hello, I've been considering installing FreeBSD on the Marvell SheevaPlug for some time, but I can't seem to find any recent info on what works and what doesn't. The various wiki pages [1][2][3] all seem to be more or less out-of-date. So, I'd especially like to know which devices work and where installation is possible, both in 8-STABLE and 9-CURRENT, and if someone already made a binary distribution of some kind. thanks, Matthias [1] http://www.plugcomputer.org/plugwiki/index.php/FreeBSD_8.0_%28current%29_Plug_Computer_Distribution [2] http://www.openplug.org/plugwiki/index.php/FreeBSD_9.x_%289-current%29_Plug_Computer_Distribution [3] http://wiki.freebsd.org/FreeBSDMarvell -- Matthias Rampke +49 179 - 166 09 18 http://rampke.de/ From owner-freebsd-arm@FreeBSD.ORG Tue Feb 23 14:01:04 2010 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 553991065670 for ; Tue, 23 Feb 2010 14:01:04 +0000 (UTC) (envelope-from kristof@sigsegv.be) Received: from yorgi.telenet-ops.be (yorgi.telenet-ops.be [195.130.133.69]) by mx1.freebsd.org (Postfix) with ESMTP id 168A88FC18 for ; Tue, 23 Feb 2010 14:01:03 +0000 (UTC) Received: from georges.telenet-ops.be (georges.telenet-ops.be [195.130.137.68]) by yorgi.telenet-ops.be (Postfix) with ESMTP id 233F35885E8 for ; Tue, 23 Feb 2010 14:49:33 +0100 (CET) Received: from triton.sigsegv.be ([213.119.65.102]) by georges.telenet-ops.be with bizsmtp id lRpW1d00B2CNSFp06RpWLo; Tue, 23 Feb 2010 14:49:31 +0100 Received: from nereid (nereid.neptune.sigsegv.be [IPv6:2001:470:c8f4:0:200:ff:fe00:8]) by triton.sigsegv.be (Postfix) with SMTP id 967D71C1F0; Tue, 23 Feb 2010 14:50:43 +0100 (CET) Received: by nereid (sSMTP sendmail emulation); Tue, 23 Feb 2010 14:49:29 +0100 Date: Tue, 23 Feb 2010 14:49:28 +0100 From: Kristof Provost To: Matthias Rampke Message-ID: <20100223134928.GJ3631@nereid> References: <31d643301002230334h17c03d0dg9f61b4ed9ae6724b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <31d643301002230334h17c03d0dg9f61b4ed9ae6724b@mail.gmail.com> X-PGP-Fingerprint: 6B6E 5EED 8ECF FAE7 1F61 7458 5046 7D0E 11B0 0EE8 User-Agent: Mutt/1.5.14 (2007-03-31) Cc: freebsd-arm@freebsd.org Subject: Re: What is the state of FreeBSD on the SheevaPlug? 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: Tue, 23 Feb 2010 14:01:04 -0000 On 2010-02-23 12:34:23 (+0100), Matthias Rampke wrote: > Hello, > > I've been considering installing FreeBSD on the Marvell SheevaPlug for > some time, but I can't seem to find any recent info on what works and > what doesn't. The various wiki pages [1][2][3] all seem to be more or > less out-of-date. > > So, I'd especially like to know which devices work and where > installation is possible, both in 8-STABLE and 9-CURRENT, and if > someone already made a binary distribution of some kind. I tried a little while ago with 9-CURRENT and got it to boot with an NFS mounted rootfs (loading the kernel over tftp, from U-boot). The network interface obviously works but I haven't tested anything else. As far as I'm aware there are no binary distributions for it. Regards, Kristof From owner-freebsd-arm@FreeBSD.ORG Tue Feb 23 14:22:00 2010 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 AB0DD1065679 for ; Tue, 23 Feb 2010 14:22:00 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 577E28FC15 for ; Tue, 23 Feb 2010 14:22:00 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id 63EBBC427C; Tue, 23 Feb 2010 15:24:03 +0100 (CET) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id LxKNRpdpXH-Q; Tue, 23 Feb 2010 15:24:02 +0100 (CET) Received: from [10.0.0.34] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id B8F3FC427A; Tue, 23 Feb 2010 15:24:02 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Rafal Jaworowski In-Reply-To: <31d643301002230334h17c03d0dg9f61b4ed9ae6724b@mail.gmail.com> Date: Tue, 23 Feb 2010 15:21:57 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <2CEFFBB0-CE3B-4157-B8BE-1DE5459BF663@semihalf.com> References: <31d643301002230334h17c03d0dg9f61b4ed9ae6724b@mail.gmail.com> To: Matthias Rampke X-Mailer: Apple Mail (2.1077) Cc: freebsd-arm@freebsd.org Subject: Re: What is the state of FreeBSD on the SheevaPlug? 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: Tue, 23 Feb 2010 14:22:00 -0000 On 2010-02-23, at 12:34, Matthias Rampke wrote: > Hello, >=20 > I've been considering installing FreeBSD on the Marvell SheevaPlug for > some time, but I can't seem to find any recent info on what works and > what doesn't. The various wiki pages [1][2][3] all seem to be more or > less out-of-date. The current state of FreeBSD on the plug is the following: - all connectivity of the device is supported (Ethernet, USB), except = for SD/MMC (the driver is already written and works, but has not been = committed to the public tree, as it needs to be cleaned up a bit, which = I haven't gotten around to yet) - the above applies to both 8-STABLE and HEAD > So, I'd especially like to know which devices work and where > installation is possible, both in 8-STABLE and 9-CURRENT, and if > someone already made a binary distribution of some kind. The wiki [3] fully applies, it only shows example snippets from some dev = boards; all other details are valid for the SP case. The wiki only shows = netbooting approach, but this should give you a starting point. BTW: the last BSD Magazine issue had an article by Don Hayford about = running FreeBSD on the plug. HTH. Rafal > [1] = http://www.plugcomputer.org/plugwiki/index.php/FreeBSD_8.0_%28current%29_P= lug_Computer_Distribution > [2] = http://www.openplug.org/plugwiki/index.php/FreeBSD_9.x_%289-current%29_Plu= g_Computer_Distribution > [3] http://wiki.freebsd.org/FreeBSDMarvell From owner-freebsd-arm@FreeBSD.ORG Tue Feb 23 14:55:33 2010 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 4E07F106568D for ; Tue, 23 Feb 2010 14:55:33 +0000 (UTC) (envelope-from matthias.rampke@googlemail.com) Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com [209.85.218.216]) by mx1.freebsd.org (Postfix) with ESMTP id B84148FC14 for ; Tue, 23 Feb 2010 14:55:32 +0000 (UTC) Received: by bwz8 with SMTP id 8so2778685bwz.3 for ; Tue, 23 Feb 2010 06:55:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=Zo5eQB1QCM058wKwj/j5VIy7K+lJdH6RyykALBmxWXo=; b=k6ct5l1aX3dHDCesdOaGx2udBVtT9XQeW+k45HAsUfXF0kQNiGOZDYg76JlZfPXE/B 6xo03nIRajIEl6yIgKTA/K+5d2Ql5ApcU8PyyZM8zxTy0ogY3xJSgvGzl/kvLAAkgkch M9cAiJ8NXrCcXR0zCTd7BbJbFRA5E65IEc+qA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=mSjgY0heM+WU82XD/+UyUh0c0nbvMKDjFb4ig6BJQc2Hm47puHpSAWsO8d8nEAN4p8 iA8rjdNIXeAu0OC4zGHqNy0t64WsJaOlGk+1dLJRL0rkxkbY0J14vl+UJG3LY75TPAz4 srOr6oWEhgl9VqkW+MCYrV1E5UtQRorLP7q6s= MIME-Version: 1.0 Received: by 10.204.32.15 with SMTP id a15mr4009226bkd.142.1266936926422; Tue, 23 Feb 2010 06:55:26 -0800 (PST) In-Reply-To: <2CEFFBB0-CE3B-4157-B8BE-1DE5459BF663@semihalf.com> References: <31d643301002230334h17c03d0dg9f61b4ed9ae6724b@mail.gmail.com> <2CEFFBB0-CE3B-4157-B8BE-1DE5459BF663@semihalf.com> From: Matthias Rampke Date: Tue, 23 Feb 2010 15:55:06 +0100 Message-ID: <31d643301002230655u6fd16d66wfedc6fb33f0d87dc@mail.gmail.com> To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: What is the state of FreeBSD on the SheevaPlug? 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: Tue, 23 Feb 2010 14:55:33 -0000 On Tue, Feb 23, 2010 at 15:21, Rafal Jaworowski wrote: > - the above applies to both 8-STABLE and HEAD > So in terms of SheevaPlug-support, there is no reason not to use 8-STABLE? Netbooting is not really a (permanent) solution for me, since if I had a NFS server permanently on, I'd have no need for a SheevaPlug ... I'll see what I can get to USB-wise. Rafal: is the SD driver available as a patch, as long as it's not in the main tree? Being able to boot from SD cards would be an almost ideal solution, second only to internal flash (which is still way off due to lack of a NAND filesystem, I know). Thanks Rafal for the quick answer (and for porting FreeBSD in the first place)! thx, Matthias From owner-freebsd-arm@FreeBSD.ORG Tue Feb 23 15:45:06 2010 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 597321065670 for ; Tue, 23 Feb 2010 15:45:06 +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 C03A98FC0A for ; Tue, 23 Feb 2010 15:45:05 +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 D09692AD8; Wed, 24 Feb 2010 00:45:02 +0900 (JST) Date: Wed, 24 Feb 2010 00:45:01 +0900 (JST) Message-Id: <20100224.004501.193683767.toshi@ruby.ocn.ne.jp> To: matthias.rampke@googlemail.com From: SAITOU Toshihide In-Reply-To: <31d643301002230655u6fd16d66wfedc6fb33f0d87dc@mail.gmail.com> References: <31d643301002230334h17c03d0dg9f61b4ed9ae6724b@mail.gmail.com> <2CEFFBB0-CE3B-4157-B8BE-1DE5459BF663@semihalf.com> <31d643301002230655u6fd16d66wfedc6fb33f0d87dc@mail.gmail.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 Cc: freebsd-arm@freebsd.org Subject: Re: What is the state of FreeBSD on the SheevaPlug? 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: Tue, 23 Feb 2010 15:45:06 -0000 In message: <31d643301002230655u6fd16d66wfedc6fb33f0d87dc@mail.gmail.com> Matthias Rampke writes: > Netbooting is not really a (permanent) solution for me, since if I had > a NFS server permanently on, I'd have no need for a SheevaPlug ... > I'll see what I can get to USB-wise. 1. put a kernel.bin into the FAT partition of a USB stick then Marvell>> usb start Marvell>> usb part Marvell>> fatls usb 0:1 Marvell>> fatload usb 0:1 0x900000 kernel.bin Marvell>> go 0x900000 2. You can boot the kernel from ffs partition if you reflash your u-boot with the followings: http://blog.springdaemons.com/2008/10/31/u-boot-ffs-ufs-support http://www.naobsd.org/sheeva/u-boot-rd88f6281Sheevaplug_400db_nand.bin Marvell>> usb start Marvell>> ffsload usb 0:2 0x900000 kernel.bin Marvell>> go 0x900000 in case of eSATA Sheeva: Marvell>> ide reset Marvell>> ffsls ide 1 / Marvell>> ffsload ide 1 0x900000 kernel.bin Marvell>> go 0x900000 And also, apply the pach to boot into multiuser mode. http://www.plugcomputer.org/plugwiki/index.php/File:Disable_forcedsingle.diff.gz SAITOU Toshihide From owner-freebsd-arm@FreeBSD.ORG Tue Feb 23 16:49:36 2010 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 B5EF0106566B for ; Tue, 23 Feb 2010 16:49:36 +0000 (UTC) (envelope-from naoki@fukaumi.org) Received: from mail.naobsd.org (w250181.ppp.asahi-net.or.jp [121.1.250.181]) by mx1.freebsd.org (Postfix) with ESMTP id 4E3E68FC19 for ; Tue, 23 Feb 2010 16:49:36 +0000 (UTC) Received: from sh8.naobsd.org ([192.168.1.183]) (authenticated bits=0) by mail.naobsd.org (8.13.6.20060614/8.13.6) with ESMTP id o1NGNAON024970 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 24 Feb 2010 01:23:14 +0900 (JST) Date: Wed, 24 Feb 2010 01:22:19 +0900 Message-ID: <871vgbvs5g.wl%naoki@fukaumi.org> From: FUKAUMI Naoki To: freebsd-arm@freebsd.org In-Reply-To: <31d643301002230655u6fd16d66wfedc6fb33f0d87dc@mail.gmail.com> References: <31d643301002230334h17c03d0dg9f61b4ed9ae6724b@mail.gmail.com> <2CEFFBB0-CE3B-4157-B8BE-1DE5459BF663@semihalf.com> <31d643301002230655u6fd16d66wfedc6fb33f0d87dc@mail.gmail.com> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.3 (i386--netbsdelf) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: Re: What is the state of FreeBSD on the SheevaPlug? 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: Tue, 23 Feb 2010 16:49:36 -0000 hello just FYI, At Tue, 23 Feb 2010 15:55:06 +0100, Matthias Rampke wrote: > Netbooting is not really a (permanent) solution for me, since if I had > a NFS server permanently on, I'd have no need for a SheevaPlug ... > I'll see what I can get to USB-wise. > > Rafal: is the SD driver available as a patch, as long as it's not in > the main tree? Being able to boot from SD cards would be an almost > ideal solution, second only to internal flash (which is still way off > due to lack of a NAND filesystem, I know). Some SheevaPlug variants have eSATA port. http://www.newit.co.uk/store/index.php?main_page=product_info&products_id=13 http://www.kuroutoshikou.com/modules/display/?iid=1440 (out of stock) If you have SheevaPlug rev. 1.3, you can add eSATA port :) http://plugcomputer.org/plugforum/index.php?topic=927.0 to use eSATA port, add following lines to kernel config. +device ata +device atadisk of course, don't forget "noclusterr" and "noclusterw" mount options. -- FUKAUMI Naoki From owner-freebsd-arm@FreeBSD.ORG Tue Feb 23 21:25:17 2010 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 1FFA91065672 for ; Tue, 23 Feb 2010 21:25:17 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id C10FA8FC14 for ; Tue, 23 Feb 2010 21:25:16 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id 87339C427C; Tue, 23 Feb 2010 22:27:20 +0100 (CET) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id e5Tw4ZceopKd; Tue, 23 Feb 2010 22:27:20 +0100 (CET) Received: from [172.16.9.100] (acjj128.neoplus.adsl.tpnet.pl [83.10.59.128]) by smtp.semihalf.com (Postfix) with ESMTPSA id 42BD2C4273; Tue, 23 Feb 2010 22:27:19 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Rafal Jaworowski In-Reply-To: <31d643301002230655u6fd16d66wfedc6fb33f0d87dc@mail.gmail.com> Date: Tue, 23 Feb 2010 22:25:04 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <31d643301002230334h17c03d0dg9f61b4ed9ae6724b@mail.gmail.com> <2CEFFBB0-CE3B-4157-B8BE-1DE5459BF663@semihalf.com> <31d643301002230655u6fd16d66wfedc6fb33f0d87dc@mail.gmail.com> To: Matthias Rampke X-Mailer: Apple Mail (2.1077) Cc: freebsd-arm@freebsd.org Subject: Re: What is the state of FreeBSD on the SheevaPlug? 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: Tue, 23 Feb 2010 21:25:17 -0000 On 2010-02-23, at 15:55, Matthias Rampke wrote: > On Tue, Feb 23, 2010 at 15:21, Rafal Jaworowski = wrote: >=20 >> - the above applies to both 8-STABLE and HEAD >>=20 >=20 > So in terms of SheevaPlug-support, there is no reason not to use = 8-STABLE? It's supposed to work on 8-STABLE. > Netbooting is not really a (permanent) solution for me, since if I had > a NFS server permanently on, I'd have no need for a SheevaPlug ... > I'll see what I can get to USB-wise. >=20 > Rafal: is the SD driver available as a patch, as long as it's not in > the main tree? Being able to boot from SD cards would be an almost > ideal solution, second only to internal flash (which is still way off > due to lack of a NAND filesystem, I know). There isn't ready to apply patch, sorry; while the SD/MMC driver itself = is a pretty self-contained piece of code = (http://people.freebsd.org/~raj/misc/mv_sdio.c), there are extensions = and updates required to the GPIO code to make it work (some MMC lines go = through the GPIO, we need to handle debouncing for presence detect = signals and so on); we have other local GPIO modifications, and this is = where some work is required to distill, clean up and reintagrate with = HEAD. Keep nagging me about it and I'll finally complete the integration :-) Rafal From owner-freebsd-arm@FreeBSD.ORG Thu Feb 25 16:47:20 2010 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5EA78106566C; Thu, 25 Feb 2010 16:47:19 +0000 (UTC) (envelope-from nork@FreeBSD.org) Date: Fri, 26 Feb 2010 01:47:18 +0900 From: Norikatsu Shigemura To: Alexander Motin Message-Id: <20100226014718.c0a07c84.nork@FreeBSD.org> In-Reply-To: <4B7EF63C.7030008@FreeBSD.org> References: <20100218023945.848cd01a.nork@FreeBSD.org> <4B7EF63C.7030008@FreeBSD.org> X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.5; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org, freebsd-current@FreeBSD.org, nork@FreeBSD.org Subject: Re: ATA_CAM-ed mvsata(4) on OpenRD-client 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: Thu, 25 Feb 2010 16:47:20 -0000 Hi mav. On Fri, 19 Feb 2010 22:36:12 +0200 Alexander Motin wrote: > > xpt_sim_opened() at 0xc0904048 = xpt_sim_opened+0x218 > > scp=0xc0904048 rlv=0xc0905940 (0xc0905940 = xpt_register_async+0xd0) > > rsp=0xc0d62d8c rfp=0xc0d62e34 > > xpt_register_async() at 0xc0905880 = xpt_register_async+0x10 > > scp=0xc0905880 rlv=0xc090d484 (0xc090d484 = ata_get_xport+0x2198) > > rsp=0xc0d62e38 rfp=0xc0d62e44 > > r10=0x00000000 r9=0x00000000 > > r8=0x005fffcc r7=0xc35593c0 r6=0xc0b62170 r5=0xc0be74d0 > > r4=0x0000001c > Even more unexpected. I've searched all sources for xpt_sim_opened() > call and found only one place - in atapi-cam.c, which shouldn't be used > in your case. You are using different sources, or there is a garbage in > stack? I tried to printf-debug, so I got what's happen. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - module_register_init: MOD_LOAD(elf32) called in module_register_init: MOD_LOAD(elf32 on elf kernel/elf kernel) called out module_register_init: MOD_LOAD(shell) called in module_register_init: MOD_LOAD(shell on elf kernel/elf kernel) called out module_register_init: MOD_LOAD(if_lo) called in module_register_init: MOD_LOAD(if_lo on elf kernel/elf kernel) called out lo0: bpf attached [DEBUG] xpt_config called #4501@/usr/src/sys/cam/cam_xpt.c [DEBUG] xpt_config #4532@/usr/src/sys/cam/cam_xpt.c [DEBUG] xpt_config #4538@/usr/src/sys/cam/cam_xpt.c [DEBUG] periphdriver_init(1), init = 1 #132@/usr/src/sys/cam/cam_periph.c [DEBUG] periphdriver_init:, i = 0, driver_name = ada [DEBUG] periphdriver_init:, i = 1, driver_name = probe [DEBUG] periphdriver_init:, i = 2, driver_name = pmp spin lock 0xc3789100 () held by 0xc3632348 (tid 0) too long panic: spin lock held too long KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at 0xc09dede0 = kdb_enter+0x48: ldrb r15, [r15, r15, ror r15]! db> show lock 0xc3789100 class: spin mutex name: flags: {SPIN, RECURSE} state: {OWNED} owner: 0xc3632348 (tid 0, pid 0, "") recursed: -251133952 db> bt Tracing pid 0 tid 100000 td 0xc0be6ab0 kdb_enter() at 0xc09deda8 = kdb_enter+0x10 scp=0xc09deda8 rlv=0xc09b572c (0xc09b572c = panic+0xcc) rsp=0xc0d6ec10 rfp=0xc0d6ec24 r4=0x00000100 panic() at 0xc09b5674 = panic+0x14 scp=0xc09b5674 rlv=0xc09a99fc (0xc09a99fc = _thread_lock_flags+0x170) rsp=0xc0d6ec38 rfp=0xc0d6ec80 _thread_lock_flags() at 0xc09a989c = _thread_lock_flags+0x10 scp=0xc09a989c rlv=0xc09ec7c0 (0xc09ec7c0 = turnstile_claim+0x16c) rsp=0xc0d6ec84 rfp=0xc0d6eca0 r10=0xc0bf244c r9=0x00000000 r8=0xc3562000 r7=0x00000044 r6=0xc3562000 r5=0xc3789100 r4=0xc0b68548 turnstile_claim() at 0xc09ec768 = turnstile_claim+0x114 scp=0xc09ec768 rlv=0xc09ecad8 (0xc09ecad8 = turnstile_wait+0x23c) rsp=0xc0d6eca4 rfp=0xc0d6eccc r7=0xc0be6ab0 r6=0xc3789100 r5=0xc0b68548 r4=0x00000000 turnstile_wait() at 0xc09ec8ac = turnstile_wait+0x10 scp=0xc09ec8ac rlv=0xc09a9568 (0xc09a9568 = _mtx_lock_sleep+0x11c) rsp=0xc0d6ecd0 rfp=0xc0d6ed00 r10=0xc0b4aa58 r9=0x00000000 r8=0x00000000 r7=0x00000000 r6=0xc0be6ab0 r5=0xc3562000 r4=0xc35fe974 _mtx_lock_sleep() at 0xc09a945c = _mtx_lock_sleep+0x10 scp=0xc09a945c rlv=0xc09a9650 (0xc09a9650 = _mtx_lock_flags+0x88) rsp=0xc0d6ed04 rfp=0xc0d6ed2c r10=0xc0d6ed60 r9=0xc0903a68 r8=0x00000000 r7=0x000007c7 r6=0xc0b4aa58 r5=0x00000000 r4=0xc35fe974 _mtx_lock_flags() at 0xc09a95d8 = _mtx_lock_flags+0x10 scp=0xc09a95d8 rlv=0xc0903e98 (0xc0903e98 = xpt_unlock_buses+0x148) rsp=0xc0d6ed30 rfp=0xc0d6ed58 r8=0xc0be33fc r7=0xc090e838 r6=0xc3788880 r5=0xc0b4aa58 r4=0xc3788b80 xpt_unlock_buses() at 0xc0903e28 = xpt_unlock_buses+0xd8 scp=0xc0903e28 rlv=0xc0903f54 (0xc0903f54 = xpt_unlock_buses+0x204) rsp=0xc0d6ed5c rfp=0xc0d6ed78 r10=0xc0be3410 r9=0xc0b4aa58 r8=0x00000000 r7=0xc090e838 r6=0x00000080 r5=0x00000000 r4=0x00000001 xpt_unlock_buses() at 0xc0903f34 = xpt_unlock_buses+0x1e4 scp=0xc0903f34 rlv=0xc0905d5c (0xc0905d5c = xpt_register_async+0xd0) rsp=0xc0d6ed7c rfp=0xc0d6ee24 xpt_register_async() at 0xc0905c9c = xpt_register_async+0x10 scp=0xc0905c9c rlv=0xc090e818 (0xc090e818 = ata_get_xport+0x2d54) rsp=0xc0d6ee28 rfp=0xc0d6ee34 r10=0x00000000 r9=0x00000000 r8=0x005fffcc r7=0xc3584460 r6=0xc0b4aa58 r5=0x00000002 r4=0x00000008 ata_get_xport() at 0xc090e808 = ata_get_xport+0x2d44 scp=0xc090e808 rlv=0xc09008a4 (0xc09008a4 = periphdriver_init+0x9c) rsp=0xc0d6ee38 rfp=0xc0d6ee50 periphdriver_init() at 0xc0900818 = periphdriver_init+0x10 scp=0xc0900818 rlv=0xc0904620 (0xc0904620 = xpt_alloc_ccb+0xbc) rsp=0xc0d6ee54 rfp=0xc0d6ee74 r5=0xc0b4ab9c r4=0x00000000 xpt_alloc_ccb() at 0xc09045a0 = xpt_alloc_ccb+0x3c scp=0xc09045a0 rlv=0xc09d4e84 (0xc09d4e84 = vaccess_acl_posix1e+0x628) rsp=0xc0d6ee78 rfp=0xc0d6eee0 r6=0xc0b660a4 r5=0xc0bebfe0 r4=0x00000000 vaccess_acl_posix1e() at 0xc09d4e2c = vaccess_acl_posix1e+0x5d0 scp=0xc09d4e2c rlv=0xc097dac4 (0xc097dac4 = mi_startup+0xdc) rsp=0xc0d6eee4 rfp=0xc0d6eef4 r7=0x00900040 r6=0x00000002 r5=0x0090004c r4=0xc0b82d94 mi_startup() at 0xc097d9f8 = mi_startup+0x10 scp=0xc097d9f8 rlv=0xc09000e4 (0xc09000e4 = btext+0xe4) rsp=0xc0d6eef8 rfp=0x00000000 r4=0x00900124 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I disabled all Giant lock, and added printf-debug code to cam/cam_xpt.c, cam/cam_periph.c. As result, varnished on pmp driver. I'll try to research where varnish point on pmp. Thank you.