From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Wed, 13 Apr 2016 18:29:32 -0400 Subject: [U-Boot] [PATCH] jetson-tk1: Set fdtfile environment variable In-Reply-To: <570E84F3.5080806@suse.de> References: <1460551699-30796-1-git-send-email-afaerber@suse.de> <570E41C0.1010904@suse.de> <570E665F.405@wwwdotorg.org> <570E6B19.1090402@suse.de> <570E7B17.9030701@wwwdotorg.org> <570E84F3.5080806@suse.de> Message-ID: <20160413222932.GO13577@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Apr 13, 2016 at 07:42:11PM +0200, Andreas F?rber wrote: [snip] > $fdtfile needs to be the Linux filename. It does not always follow the > same pattern as the U-Boot variables you suggest here. > CONFIG_DEFAULT_DEVICE_TREE ".dtb" might work better, and that was my > question to you. > > It's part of the generic mechanism, so not just select boards. Yet I was > told that all boards are expected to set their cacheline size (although > that is not a board but CPU property), so similarly we can (yes, newly) > desire all boards to provide DT related settings as well. > > If you would supply a feature-complete DT in the first place, we > wouldn't need $fdtfile here, but it seemed that that was not realistic > to expect for the upcoming U-Boot release. So here's the thing. Figuring out what the device tree to load is, and where it's going to reside is a sucky problem. For most of the complex cases we do this today with "run findfdt". Why? Well, check out the implementations in "git grep -l findfdt=" right now. It sounds like we need to figure out how to get EFI in line with everything else that U-Boot does/supports rather than to re-invent the wheel here. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: