From nobody Sun Apr 10 19:58:16 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id BD39B1A811F5 for ; Sun, 10 Apr 2022 19:58:17 +0000 (UTC) (envelope-from matteo@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Kc2px4x9Vz3F1W for ; Sun, 10 Apr 2022 19:58:17 +0000 (UTC) (envelope-from matteo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1649620697; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=9SGuYha58Ie2RT6wI7X3z9tFQc2NZqaAXaXdPSKVjLA=; b=W4b+a1SdJK8bMRJCQ/r0n94tV7Xv2geomp1N+Ovm7a0QMS5C5dlL9JyZv4/bvrf++nkFDF O6z/qPdiv3FjwLDgKEXn0uFvsFSLB6SsTxHa/exMVMbcTgvinkih1FOYIKKnvxNfcie2WL 5oxVGz8rUW7aNZ40GG+v5avxz7dMfkZtZBKvo3cI595T7us0WRVJmF4fATu+St1EcmNq31 kJV/dB5WglRm+zULuCPwUKflR8mTTM/ZTaOT7n3Drx+SlGT46ClpMNbzSDMyWeGMPVvUuz 0Ak6jHoACN/vOzmccfcou3OwaOFyrSsV68ov8h+a9ZyOvmY1HrE1I0jiftGyYQ== Received: from host-ubertino-mac-24f5a28a9493.wired.10net.amherst.edu (unknown [IPv6:2601:19b:4400:1779::102f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: matteo/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 6DBE02834F for ; Sun, 10 Apr 2022 19:58:17 +0000 (UTC) (envelope-from matteo@freebsd.org) Date: Sun, 10 Apr 2022 15:58:16 -0400 From: Matteo Riondato To: freebsd-arm@freebsd.org Subject: [armv7] dtb specified with FDT_DTS_FILE in kernconf not built when using release.sh Message-ID: <20220410195816.k6qvkagroudas634@host-ubertino-mac-24f5a28a9493.wired.10net.amherst.edu> X-PGP-Key: http://rionda.to/files/matteogpg.asc List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="274se3atambhr2qv" Content-Disposition: inline ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1649620697; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=9SGuYha58Ie2RT6wI7X3z9tFQc2NZqaAXaXdPSKVjLA=; b=SxC9IKASF/IrJ5spQ0x7pia8JxEPamivS2CLLRHNTEdpOdB6gl3kIJDcVc7Z04BEWI6Dxn Lt2pgmQk2PqeyBeQyeVVSiC2D2twfrKS0wdkgTtDEdUML6Mg4ceaiTWlDDmHlmfDiXU4IM u9/ptwOPbQM7/oH7l+Gw2P88N6WTLnBOD5/YI1TVPVynOf5sP6GN9tTIYvGCmkL9IU/t7o AidQynhNbkB9bQog/3hn0fGA8k3qZRvmKLSp8TG4BWcnhFAIBU48AA5u9NAqbXKFFjj7uq MYZLaS0LKgx3bRZ+ZRZfcppxoMxqZbmgnyxFcttdK799AXD8BONWuNjXkuaIgg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1649620697; a=rsa-sha256; cv=none; b=VX2c4mSf5W+5adRM4NyyGbUR+MIeVjyevcYy/T/5kcDmhUD01igMdUHSRETovxlso3UHz/ jPCE1OXhGiZ2qwqDT+Lob+FLRgINf4C99LCRc55XaxiApZlgykmpgT4ZYQgEBpHCNIJNor SyBgV/Og2wHao0HJLxBT52sleYh2cCVHLHvWxtgTrA/zxjyrWh2uuvWcNORYqwvNyhJDbe Ol2dCxpnZofGW3uZNBqTDcfyhJ/Bj11pDY/co9+32dvRMZLs1a9OcXZMDZG3R3waRUCmMg p9BgTAWQuMU2Tr+36JSm5SUSFGBxd6g6mcyJyTyCN8CmHwB0go7Azx5Ac/wldw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N --274se3atambhr2qv Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I'm trying to cross-build (from amd64) a custom -CURRENT armv7 image for=20 my beaglebone enhanced using the release(7) method with a custom=20 release.conf script, which I wrote starting from release/arm/GENERICSD. The only customization that I want to include is to use the appropriate=20 dtb compiled from the dts files for this board. I thought I could=20 achieve this goal by having "makeoptions FDT_DTS_FILE=3D..." in my=20 kernconf, but the dtb does not seem to be compiled in the chrootdir, not=20 to say installed, the image. The kernconf is the following: include GENERIC include "../../conf/std.nodebug" ident GENERIC-ND-BBE makeoptions FDT_DTS_FILE=3Dam335x-sancloud-bbe.dts My release.conf script has a custom buildenv_setup() function to cp the above kernconf to the /usr/src/sys/arm/conf/ directory of the chroot,=20 and the dts to /usr/src/sys/dts/arm of the chroot (from what I could=20 infer, that is the correct path for the dts, but please let me know if=20 that's not the case). I don't see the compiled dtb anywhere in the chroot, nor an error=20 message or a warning that it failed to build, and it is not in the image=20 either. What am I missing? Thanks, Matteo --274se3atambhr2qv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJHBAABCgAxFiEEa9uKZL0hP4E8Nl5vGwL9SVQlVQEFAmJTNtgTGGhrcHM6Ly9w Z3AubWl0LmVkdQAKCRAbAv1JVCVVAWrCD/wLxkrHZoUEYQD0XKsSUWoO+hJzS9Mp TabHInrgerk9YbM0VfUlFWZv9LgiNIBbO2iRbS2U8Y8d1EA6cDeooc2BeKBpTeVx C1OEv5wR5L/hqoBOE4ns2TTkwE9MtF7gRMFAMRJU5B8XBn8obWUOyIttmkOoauJa 85mZFmOfUwlIQW//aQhmlEfxcop2Nf2IbkOIHsM9XLbQsuivblJXj8e5EPwv5xkc BI6a4BVuRPZOtmpSzA7uIZd4Brei9OYx0BTHPUPZapvEPLA0zv70/pS5PH080M/l 9XWU0snGq/X8fa1SHGBI71Tdu1d/pGEP0xo7eBmq2NGCB9yZ0T+Y/pF6i+UcC6Id 76plwlrt384Nge3mscpTD+7YGj2CTEj2XL6aaUA/SHRgdlm8FJVQjxmDA0LFh7m/ DS7U9DXzkqWz2xV24SvKk8m+AirFkNDqCzWy1xonnnxIjO91Mo4NccCJDl/+kiPk hYOsl4K/QaqTnmz7u7fGpf5NlDVPxAG/aojlSv1QW3PpEWNWWeE2zZT1LTNkdHzq 8v9f7S0anYYneSdCsDcbjlV35YhX9y83tpuhodrR5M+JMHTwAyiVvDispQ8kI/fO 5IKyx171fRX7mpQvKQwFTaKb/68xe5xi20Zmr84XMyVvL6093QG/AsMq61oOEBgF 3iue0AEi5kVcjg== =BrDR -----END PGP SIGNATURE----- --274se3atambhr2qv--