From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Date: Wed, 13 Apr 2016 15:17:41 +0200 Subject: [U-Boot] [PATCH] efi_loader: Use system fdt as fallback In-Reply-To: <570E465C.9060205@suse.de> References: <1460386526-10344-1-git-send-email-agraf@suse.de> <570E4268.9080808@suse.de> <570E465C.9060205@suse.de> Message-ID: <570E46F5.5020403@suse.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 13.04.2016 um 15:15 schrieb Alexander Graf: > On 04/13/2016 02:58 PM, Andreas F?rber wrote: >> Am 11.04.2016 um 16:55 schrieb Alexander Graf: >>> When the user did not pass any device tree or the boot script >>> didn't find any, let's use the system device tree as last resort >>> to get something the payload (Linux) may understand. >>> >>> This means that on systems that use the same device tree for U-Boot >>> and Linux we can just share it and there's no need to manually provide >>> a device tree in the target image. >>> >>> While at it, also copy and pad the device tree by 64kb to give us >>> space for modifications. >>> >>> Signed-off-by: Alexander Graf >> Tested-by: Andreas F?rber >> >> It definitely avoids a warning message. However, it does not always >> allow Linux to actually boot, e.g. on jetson-tk1 (patch sent). > > We could give the user a warning in the fallback case as well, but > ideally I'd like to move to a model where all device trees really are > interchangable and work with every component. So then we would warn the > user about the preferred default case. I'm not sure that's a great idea. I'm not saying we need a warning here, just that this solution by itself is not sufficient and other fixes (like supplying $fdtfile) are still necessary today. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton HRB 21284 (AG N?rnberg)