From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751716AbdKTQiP (ORCPT <rfc822;w@1wt.eu>);
        Mon, 20 Nov 2017 11:38:15 -0500
Received: from mail-oi0-f65.google.com ([209.85.218.65]:44543 "EHLO
        mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751408AbdKTQiN (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 20 Nov 2017 11:38:13 -0500
X-Google-Smtp-Source: AGs4zMbqullAyHGcs3/nXXcAx1zcRv0b20GtLqSz9gsb41dMILLLKWiWFkpyV/FLB/m/3q3nzRe1rg==
Subject: Re: RFC: Copying Device Tree File into reserved area of VMLINUX
 before deployment
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@emagii.com, LKML <linux-kernel@vger.kernel.org>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        Rob Herring <robh+dt@kernel.org>
References: <0b31e22b-202f-6fca-28f2-e16e6af6c6b7@emagii.com>
 <a0f9d598-04af-fddd-58ad-09db10ec19da@gmail.com>
 <20171120114405.cpsf4xtvvfpuk76u@lakrids.cambridge.arm.com>
From: Frank Rowand <frowand.list@gmail.com>
Message-ID: <eb654f41-c0be-ddb6-b730-22ad3dd451eb@gmail.com>
Date: Mon, 20 Nov 2017 11:38:11 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <20171120114405.cpsf4xtvvfpuk76u@lakrids.cambridge.arm.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Ulf,

On 11/20/17 06:44, Mark Rutland wrote:
> 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.

That is CONFIG_ARM_APPENDED_DTB, if you want to see what it looks like.


> Does mips not support something similar?
> 
> Thanks,
> Mark.
>