From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751245AbdKTLoK (ORCPT ); Mon, 20 Nov 2017 06:44:10 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:56236 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751073AbdKTLoJ (ORCPT ); Mon, 20 Nov 2017 06:44:09 -0500 Date: Mon, 20 Nov 2017 11:44:05 +0000 From: Mark Rutland To: Frank Rowand Cc: linux-kernel@emagii.com, LKML , "devicetree@vger.kernel.org" , Rob Herring Subject: Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment Message-ID: <20171120114405.cpsf4xtvvfpuk76u@lakrids.cambridge.arm.com> References: <0b31e22b-202f-6fca-28f2-e16e6af6c6b7@emagii.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Nov 19, 2017 at 11:23:42PM -0500, Frank Rowand wrote: > adding devicetree list, devicetree maintainers > > On 11/18/17 12:59, Ulf Samuelsson wrote: > > I noticed when checking out the OpenWRT support for the board that they have a method to avoid having to pass the device tree address to the kernel, and can thus boot device tree based kernels with U-boots that > > does not support device trees. > > > > Is this something that would be considered useful for including in mainstream: On 32-bit arm, we support an appended DTB for cases like this. The DTB is appended to the end of the kernel image, rather than being embedded. Does mips not support something similar? Thanks, Mark.