From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 04:40:46 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 E46BE229; Sat, 25 Jan 2014 04:40:46 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BA1341DAA; Sat, 25 Jan 2014 04:40:46 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 0CB1712FC6; Sat, 25 Jan 2014 04:40:45 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 0CB1712FC6 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Fri, 24 Jan 2014 23:40:43 -0500 From: Glen Barber To: freebsd-arm@FreeBSD.org Subject: Rasbperry Pi, what should TARGET_ARCH be? Message-ID: <20140125044043.GT52955@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xPLL5cPndR2UZ7Mw" Content-Disposition: inline X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) 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: Sat, 25 Jan 2014 04:40:47 -0000 --xPLL5cPndR2UZ7Mw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I've been working on adding support for embedded systems to the release scripts, which set up a chroot to ensure a clean build environment, then runs Tim's Crochet scripts. For the RPI-B, recent updates to the build scripts work fine for 11.0-CURRENT and 10.0-STABLE. However, 10.0-RELEASE images fail to boot. I showed output from 'uname -pm' out-of-band of an 11.0-CURRENT image, and was suspicious that the output showed 'arm arm', not 'arm armv6'. Warner had the same impression it should be 'arm armv6'. Hiren poked around the Crochet code, and saw that 'TARGET_ARCH=arm' is set for the RaspberryPi board by default. As a "just in case" experiment, I retried the 10.0-RELEASE code (release/10.0.0/) with TARGET_ARCH=armv6, and sure enough, it works. But, I don't know *why*. Is this a change between head/ and stable/10/ versus releng/10.0/ ? I can handle a differentiation between the branches with regard to this (sort of), but I want to make sure the correct TARGET_ARCH is being set across the different branches, so it can be handled properly in the build scripts, and usable images can be produced. So, what should be used? And where? Thanks for any input, Glen --xPLL5cPndR2UZ7Mw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS40BLAAoJELls3eqvi17Q4ooQAIzRhVxImuQIyS27wxL4q3d0 gPBZYU4V4GpbKa8ZJXXsyHZSjanDPQw0mZ5L8g3edJVeHb/PRk97T5N2/quirar+ vFzY2XNXOPBCIX1EyJuRAGp2VYTT/3+Rzw4MLj2exSgqTzi/HM15QQBBYQJGP+3t Jk4hQcQEyuRlP5GR6QR7OWLj9js6oJFY1rPMLOAkceH6deKArQ6gYUvdquZF0uJQ Sc8tuOQWUKo+wcnS3ysouwY7jZllBOjeBofSV8/Wgaqjc+2aGqKQC/WtxzJm9jGH IrN2CdaqBT/FyM2sOjR54W+Xzka9qNidWqTlvzLBlvFX6CnGSVzCCtZIFVmzM1nf UtM+I/nqAlwwhlaOfMaZ8FIMNid+J6SAd4vD9dlZzuNf9JXWZ8f6ImH7GLqXHEHd dWlsYhgxg0uffHSbIssY+DzxOrYjO8+voxHwf/asonZAlvw1CTkxpB3sSRPecsM0 M/DdMcLuaZbSTgTAjJj/EhoVL+D1W32ttPqQlKGWr3bXbXPJTtA1E33c/FlZz8y6 XXZNYOTZRGYGiFrl+5rdWhg937qrghjws/mtQE4K7dHDfXjMYmou6hUOv0dB6vCB pJm/HNRM6IeHclWnhSc32yfBXPFCPnTQB6ce7sxO85NdjpgM4OsMOf4a4QESewXs fHT96tVM2CFLeCQzNhAn =LiZo -----END PGP SIGNATURE----- --xPLL5cPndR2UZ7Mw--