From owner-freebsd-arm@FreeBSD.ORG Mon Feb 3 02:59:39 2014 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 ESMTPS id 29F40A8A for ; Mon, 3 Feb 2014 02:59:39 +0000 (UTC) Received: from mail-ig0-f181.google.com (mail-ig0-f181.google.com [209.85.213.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E38761113 for ; Mon, 3 Feb 2014 02:59:38 +0000 (UTC) Received: by mail-ig0-f181.google.com with SMTP id j1so3395192iga.2 for ; Sun, 02 Feb 2014 18:59:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=+yk9YzY1ekJBWfJ/P9hPpnJYmQA43GWyfdZpUzE8Exg=; b=Nn31Uvans1Q1qIuvg/epdasEMV7UWrOG0wqGi5CTycKHnB+Hgw6/vo0Xt4dQ8P53hE rMopn1+iQ5IELkeq9UyD9K39w0t7wD8mnAsRnoALTKWt5I2p/Oot1bso5sz3raFqWi/c BMXIe2QTObGGyGHKVVN3n+kkn7XlXhNdo4Tcung0E+ciaWjJEF/yorA2qG2IdWaAJ3/i 3UrtoZDGQwIwlbVGPQfAPYYpfxplTBc8o8BdarL3AEtZcC0KCXhb0EvlwHZl9bfAVyJe xyOzLrroPBWQIyOQnkl3LYv57CK39WDff7wNY7dBckVnnxFIkfwvv/qDvYQhLHvmfexw r3LA== X-Gm-Message-State: ALoCoQnXA+p3+1M3Bab3sDFp2+9Ii3j7fmn3+kQO1L8GywNOvVG5Qn2UIvVUtSH8UUmCqvRQ3+oS X-Received: by 10.42.227.195 with SMTP id jb3mr24925029icb.27.1391396377796; Sun, 02 Feb 2014 18:59:37 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id x13sm25932716igp.2.2014.02.02.18.59.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Feb 2014 18:59:37 -0800 (PST) Sender: Warner Losh Subject: Re: wandboard / imx6 / exynos4 / cortex-a9 "wrong-endian bug" fixed Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <1391395062.13026.69.camel@revolution.hippie.lan> Date: Sun, 2 Feb 2014 19:59:37 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <1584FD9C-581F-4BCF-8153-E381693887DB@bsdimp.com> References: <1391371204.13026.43.camel@revolution.hippie.lan> <20140202230450.GA42331@cicely7.cicely.de> <1391395062.13026.69.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1085) Cc: Bernd Walter , freebsd-arm , ticso@cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Feb 2014 02:59:39 -0000 On Feb 2, 2014, at 7:37 PM, Ian Lepore wrote: > On Sun, 2014-02-02 at 18:25 -0700, Tom Everett wrote: >> I can confirm that a crochet image for Wandboard no longer crashes = after >> this fix. It doesn't mount the FS yet, but that's a known issue, = noted >> here: >>=20 >> https://github.com/kientzle/crochet-freebsd/issues/29 >=20 > That thread mentions needing to build a u-boot for wandboard. Here's = a > patchset for doing that. Apply this in your ports/sysutils dir, = using: >=20 > patch -p0 =20 > This was copied from Tim's beaglebone work and changed a bit for > wandboard. =20 >=20 > I've been meaning to ask about how we should handle this. Do we want = a > u-boot port for every board, or is there some way to parameterize a > single port so that it applies the right set of patches, or what? I'm > not very savvy about ports. Usually there's a master port, and slave ports that parameterize. When = we talked about this at BSDcan, I believe that was the model that was = suggested for this problem.. Warner