Date: Sun, 10 Apr 2022 15:58:16 -0400 From: Matteo Riondato <matteo@freebsd.org> 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>
next in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220410195816.k6qvkagroudas634>