From owner-freebsd-arm@FreeBSD.ORG Tue Nov 5 04:47:36 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7DEEA81E for ; Tue, 5 Nov 2013 04:47:36 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5239E2AFF for ; Tue, 5 Nov 2013 04:47:35 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id fa1so8034738pad.13 for ; Mon, 04 Nov 2013 20:47:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=hNlPZRaeAv3nx5CCnZ0gxj2pX7TD1CfWjEsace09xUs=; b=m8Bug7SpSy+xO9PMlD+IX/0/LV8/WPvirVj8vf4YG+pQUA6vND87cCA3maL+kKx7dU EO46Q2XG6Ww+kTKyCh5I/KMjxQklCPBZFRlHUFhz2UtYy5NQG0kQjAJkjypm3JIvFWXE 3adbZtN2oFjLsU6k94nqAICpTIOyQSjKxk209c4DbaV2El9PUpaGpxqbu7XBm+rHX1yf +aknSBquzK8Huv6ZeaVUDphk1IZloAyX2PUyzUSb5mmI+R/KA1YkWKCfS/mcJcdyrLSE ZO3LzQQZz2oP/UsvGxFAGXjsIglRDVSqTng8cnn7ChIdhi30zC68Q9WtbfeQuMTZzKJW 3Ujw== X-Gm-Message-State: ALoCoQmSlTIKJ+Ji4ifzjsym3NVzOflD+6+baOHfOeVfraMDJ4o/KNj9LppNNfoW+UEu6bnHHJZS X-Received: by 10.68.134.6 with SMTP id pg6mr21139685pbb.67.1383626526600; Mon, 04 Nov 2013 20:42:06 -0800 (PST) Received: from [192.168.1.2] (c-24-6-185-228.hsd1.ca.comcast.net. [24.6.185.228]) by mx.google.com with ESMTPSA id gg10sm31706847pbc.46.2013.11.04.20.42.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Nov 2013 20:42:06 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: freebsd/pandaboard Spurious interrupt detected [0x000003ff] From: Tim Kientzle In-Reply-To: Date: Mon, 4 Nov 2013 20:42:03 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <3FCAE16F-594B-466E-9E78-A847F52F891C@kientzle.com> References: <1383526716.31172.131.camel@revolution.hippie.lan> To: David Cheney X-Mailer: Apple Mail (2.1510) 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: Tue, 05 Nov 2013 04:47:36 -0000 On Nov 3, 2013, at 6:19 PM, David Cheney = wrote: >=20 > As a question to the group, I have the following hardware >=20 > Pandaboard > BeagleBone Black > RPi >=20 > And I am trying to bring up Freebsd/arm so I can get our Go builder > working again[1]. Of these candidates, which is the one you would > recommend ? Either the BBB or the RPi. Both are reasonably well-supported on FreeBSD/ARM right now. Each has issues, but there are enough people using each one that the issues are steadily getting resolved. > ... BBB ... selecting a very low, ~550mhz clock speed Yep. That would be one of the "issues." > =85 build times for ports and go of many hours. If your primary concern is build time for ports, talk to Stacey Son and Baptiste about Stacey's QEMU ARM activator. Basically, they've come up with a technique for running cross-builds on AMD64 hosts targeting ARM and MIPS at nearly native performance and using the native build scripts. It's the most promising approach so far for doing bulk builds targeting ARM and MIPS. Very clever, but hard to explain. Tim