From owner-freebsd-arm@freebsd.org Mon Jan 2 11:54:15 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E70E2C9B115 for ; Mon, 2 Jan 2017 11:54:15 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B12121FE4 for ; Mon, 2 Jan 2017 11:54:14 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 17021208B5 for ; Mon, 2 Jan 2017 06:54:13 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 02 Jan 2017 06:54:13 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=qXmnaKW6jyRjzRBOyYkzkPFZey4=; b=FtLbnO h3T9Tz0VJcKKsPzXBRe/SXVGDXaGZG4AbNCSSde6Qn0VwWr1qjY4y9PQQ035IDgu nAMeLvNbD2K+ynSkhdgaZrHls6Ygk5wFz6mb5kSnwoiX2U2H37A0gkU3n0iXdtBq tZWPQbs657mnJxa8FRCDBsv2O/0hXQTWO7CN8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=smtpout; bh=qXmnaKW6jyRjzR BOyYkzkPFZey4=; b=SMj99WeqBNLZvU+SEpQX4PpI2mJm6KNXb181cAet5wt+oR rDnJceK+RX2V6Y4RcTenblsm8rKv5hy2sfvltqtYshYMap+LYy+gpmRJmzRT/8xw xFqn1yBdYmZ1qJlbw0G8WXy9cE4QKUYYiHaM/tjzWpuKz+Ly+T+W5j/mrPM3E= X-ME-Sender: X-Sasl-enc: 2c8NvJtoMZRJxgw87aU97Q7Rs+F7Lbz+VBuS25p7zTco 1483358052 Received: from pumpkin.growveg.org (pumpkin.growveg.org [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id BF7AF7E8D9 for ; Mon, 2 Jan 2017 06:54:12 -0500 (EST) To: freebsd-arm@freebsd.org From: tech-lists Subject: aarch64 on pi3 advice Message-ID: <05fee124-ad8f-43e8-79d9-ccb99bc83214@zyxst.net> Date: Mon, 2 Jan 2017 11:54:10 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2017 11:54:16 -0000 Hello list, I've installed aarch64/pi3 cross-compiling on an i7 via crochet onto a pi3 machine and it seems to work well. Please advise: 0. I've fount a config.txt in /boot/efi. Where can I set the speed & memory/GPU and what's the syntax? 1. Can I mount /usr/ports on say a usb stick, compile from there and expect it to install OK? /usr/ports would be a symlink to /32GB-usbkey/ports. I see that ld & ldd are present, so I guess I can compile from ports? 2. I'd like to strip out WITNESS and friends and recompile the kernel. Can I do this on the rpi3 and expect it to work? Should I? Or should I just do this on the faster i7? 3. If I have to go down the route of cross-compiling another image on the i7, is there a way I can also install a selection of ports to the image before using the image on the pi3? Many thanks -- J.