From owner-freebsd-arm@FreeBSD.ORG Fri Apr 18 04:17:55 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 616EC8AE for ; Fri, 18 Apr 2014 04:17:55 +0000 (UTC) Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32FC619A1 for ; Fri, 18 Apr 2014 04:17:54 +0000 (UTC) Received: by mail-pb0-f46.google.com with SMTP id rq2so1081996pbb.19 for ; Thu, 17 Apr 2014 21:17:48 -0700 (PDT) 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=t9c5zY80iTIHxGNZujKDhZoyEhtjSnoxwLPVxBldQzE=; b=MqjGVYjq9tO3MGCfBJRNkgXYhG57sdU3A+JazNIhkB/T90aLVYF6wl+4HQAu6bvyTP Ep4rJOpvyF9yYLWL1tFiebNljmkm8nKjPuqamwZjuJxRI6QbTxXpgn0rJ8TRdFSoVeKd KbKx7CVFMRSRVB9dVk2WSczCYEBLqyNxek1MvJo3/mtZN0QHoyM3SrMzCM2dxoIeh/tX q/2mKdkXv2lll3akFoxr3apmehkPsBuD7HmHhLw3skq6rFosCdOIUdL8eCtKpSjGLUJR qyRf/8C45HFGAheufgQb7iVBC9ZaERiq9b00ikd7bDpwmH9dKAIRGKGJKph63foZ21sl QUog== X-Gm-Message-State: ALoCoQmDehzriWqFuEc8beE6F4fSSFVxVPDiMsTG+q06pJp9UHkcNzNs8jyScRCgW9wWi8Rfp3F5 X-Received: by 10.66.66.202 with SMTP id h10mr19764354pat.70.1397794668441; Thu, 17 Apr 2014 21:17:48 -0700 (PDT) Received: from [192.168.1.2] (c-50-156-22-189.hsd1.ca.comcast.net. [50.156.22.189]) by mx.google.com with ESMTPSA id iq10sm56981350pbc.14.2014.04.17.21.17.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 21:17:47 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: Building an ARM/RPI-B release (hacked) on CURRENT/AMD64. From: Tim Kientzle In-Reply-To: <4B9FEF94-9912-4861-9FE2-E8EC7BE3509C@grondar.org> Date: Thu, 17 Apr 2014 21:17:45 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <44685985-BD5A-4D5F-B6DB-99A7252F8C8C@kientzle.com> References: <9FDD6F0E-B2A9-48D9-A3E4-181868995FDA@grondar.org> <4B9FEF94-9912-4861-9FE2-E8EC7BE3509C@grondar.org> To: Mark R V Murray X-Mailer: Apple Mail (2.1874) Cc: freebsd-arm 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: Fri, 18 Apr 2014 04:17:55 -0000 On Apr 17, 2014, at 12:23 AM, Mark R V Murray wrote: >=20 > How much hacking does u-boot need for 1) FreeBSD and 2) RPI? 1) standard patches to enable API and ELF support for ubldr. Crochet = has in-tree patches for several different target boards; look for the = part that=92s the same across all of them. ;-) 2) Oleksandr=92s hacked RPi version of U-Boot is on github >=20 > Should its head-of-trunk =93just work=94? They have apparently sorted = out the R8/R9 business which should make it CLANG-ready, IIUC. As noted elsewhere, clang and U-Boot need more reconciliation. Plus standard patches for FreeBSD to enable API and ELF support for = ubldr. Plus various board-specific patches: * the hard-coded U-boot start scripts vary enormously across different = boards and are almost always very Linux-specific; * some U-Boot start scripts read additional startup scripts from disk = which allows you to tweak without overriding the hard-coded portion, but = not all, and those that do don=92t always do it the same way. Tim