From owner-freebsd-arm@freebsd.org Thu Mar 28 20:53:09 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7687915695A4 for ; Thu, 28 Mar 2019 20:53:09 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from mout2.freenet.de (mout2.freenet.de [195.4.92.92]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (Client CN "*.freenet.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88D6D8BE96; Thu, 28 Mar 2019 20:53:07 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from [195.4.92.163] (helo=mjail0.freenet.de) by mout2.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.90_1 #2) id 1h9c1G-0002MX-03; Thu, 28 Mar 2019 21:53:02 +0100 Received: from [::1] (port=55150 helo=mjail0.freenet.de) by mjail0.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1h9c1F-0004ax-VR; Thu, 28 Mar 2019 21:53:01 +0100 Received: from sub7.freenet.de ([195.4.92.126]:35416) by mjail0.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1h9bz7-0003jg-LF; Thu, 28 Mar 2019 21:50:49 +0100 Received: from p4fd9f268.dip0.t-ipconnect.de ([79.217.242.104]:14622 helo=freebsd-t450.fritz.box) by sub7.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256) (port 465) (Exim 4.90_1 #2) id 1h9bz7-0002Q4-Eg; Thu, 28 Mar 2019 21:50:49 +0100 Date: Thu, 28 Mar 2019 21:50:48 +0100 From: Manuel =?ISO-8859-1?Q?St=FChn?= To: Kyle Evans Cc: "freebsd-arm@freebsd.org" Subject: Re: efi-loader ignores dtb files? Message-Id: <20190328215048.9dccb364c7ccac59f77bb98f@freenet.de> In-Reply-To: References: <20190327192320.GA64908@freebsd-t450.fritz.box> <20190328190355.1459c85b48211905f8a3e04a@freenet.de> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Originated-At: 79.217.242.104!14622 X-Rspamd-Queue-Id: 88D6D8BE96 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of freebsdnewbie@freenet.de designates 195.4.92.92 as permitted sender) smtp.mailfrom=freebsdnewbie@freenet.de X-Spamd-Result: default: False [-1.82 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[freenet.de]; R_SPF_ALLOW(-0.20)[+ip4:195.4.92.0/23]; MV_CASE(0.50)[]; MX_GOOD(-0.01)[emig.freenet.de,emig.freenet.de,emig.freenet.de,emig.freenet.de]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.43)[-0.433,0]; RCVD_IN_DNSWL_LOW(-0.10)[92.92.4.195.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[freenet.de]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:5430, ipnet:195.4.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[104.242.217.79.zen.spamhaus.org : 127.0.0.10]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.991,0]; RCVD_COUNT_FIVE(0.00)[5]; SUBJECT_ENDS_QUESTION(1.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[freenet.de]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-0.49)[ip: (-0.84), ipnet: 195.4.0.0/16(-0.81), asn: 5430(-0.77), country: DE(-0.01)]; RWL_MAILSPIKE_POSSIBLE(0.00)[92.92.4.195.rep.mailspike.net : 127.0.0.17] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Mar 2019 20:53:09 -0000 On Thu, 28 Mar 2019 14:10:27 -0500 Kyle Evans wrote: > On Thu, Mar 28, 2019 at 1:30 PM Kyle Evans wrote: > > > > On Thu, Mar 28, 2019 at 1:06 PM Manuel St=FChn wrote: > > > > > > On Wed, 27 Mar 2019 14:35:26 -0500 > > > Kyle Evans wrote: > > [... snip ...] > > > > I'm not sure off-hand why fdt_overlays were not recognized. I would > > > > drop to loader prompt and double check that it actually ended up in > > > > the environment, but I don't see any reason off-hand that it wouldn= 't. > > > > > > I tried to load the overlays from loader prompt by hand like this: > > > load -t dtbo sun50i-nanopi-neo2-codec.dtbo > > > load -t dtbo sun50i-nanopi-neo2-sid.dtbo > > > load -t dtbo sun50i-nanopi-neo2-ths.dtbo > > > and they got applied correctly and the corresponding devices appeared= in the OS. > > > > > > As another test I did was to not load the base dtb file via loader.co= nf but to use the one provided by u-boot/EFI. > > > The output looked like this > > > [...] > > > Using DTB provided by EFI at 0x47ef8000. > > > Loading DTB overlays: 'sun50i-nanopi-neo2-codec.dtbo,sun50i-nanopi-ne= o2-sid,sun50i-nanopi-neo2-ths.dtbo' > > > /boot/dtb/overlays/sun50i-nanopi-neo2-codec.dtbo size=3D0x11a > > > /boot/dtb/overlays/sun50i-nanopi-neo2-sid.dtbo size=3D0x1f5 > > > /boot/dtb/overlays/sun50i-nanopi-neo2-ths.dtbo size=3D0x3c5 > > > applying DTB overlay '/boot/dtb/overlays/sun50i-nanopi-neo2-codec.dtb= o' > > > applying DTB overlay '/boot/dtb/overlays/sun50i-nanopi-neo2-sid.dtbo' > > > applying DTB overlay '/boot/dtb/overlays/sun50i-nanopi-neo2-ths.dtbo' > > > failed to apply overlay: FDT_ERR_NOTFOUND > > > [...] > > > In this case the overlays were found and loaded, but did most likely = not match the u-boot dtb file. > > > > > > Is there an issue with loading overlays in conjunction with manually = loading dtb files via loader.conf? > > > > > > > Yes, I see a problem -- try something like [0] (not even compile > > tested, but it should work). I'll start working out a more proper > > solution. >=20 > I've devised a solution that's a little less hacky at [1]. It > separates out the loading of overlays from platform_load_dtb into its > own platform_load_overlays. I've left it as a platform-specific thing > instead of lifting it into the common fdt bits for two reasons: >=20 > 1.) We still technically support setting fdt_overlays in the U-Boot > environment and honoring that, and > 2.) Not all FDT platforms support overlays as they've not been tested, > so it's probably best to nop it there for now just in case... >=20 > If we're ok with dropping #1 (probably not even used, but we don't > have a way of measuring usage there) and OK with adding untested > overlay support to powerpc/{ofw,kboot} then this diff drops > dramatically and the calls to fdt_platform_load_overlays get replaced > with fdt_load_dtb_overlays calls. >=20 > > [0] https://people.freebsd.org/~kevans/overlay-hack.diff >=20 > [1] http://people.freebsd.org/~kevans/overlay-lesshack.diff Thank you for your patches. I've been trying patch[1] but unfortunately it seems to not work for me. Due to my lack of knowledge on how to only build and install /usr/src/stand I've built+installed both kernel+world, but the described behavior did not change; still no overlays when defining a dtb file in loader.conf. --=20 Manuel=20