linux-kernel - Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 20 Nov 2017 11:44:05 +0000
From:   Mark Rutland <mark.rutland@....com>
To:     Frank Rowand <frowand.list@...il.com>
Cc:     linux-kernel@...gii.com, LKML <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        Rob Herring <robh+dt@...nel.org>
Subject: Re: RFC: Copying Device Tree File into reserved area of VMLINUX
 before deployment

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.