From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 12/13] ARM: dts: ti: add dra71-evm FIT description file
Date: Tue, 29 May 2018 23:51:14 +0100 [thread overview]
Message-ID: <20180529225114.GO17671@n2100.armlinux.org.uk> (raw)
In-Reply-To: <a43ce521-ed7f-6126-4ebf-5e0e303d00a3@gmail.com>
On Tue, May 29, 2018 at 03:45:12PM -0700, Frank Rowand wrote:
> If the kernel applies the overlay, an alternative to drivers is that the
> kernel could receive the overlay(s) in a similar manner as the method it
> currently receives the base devicetree. (The overlay(s) could be
> appended to the base devicetree, a wrapper could be placed around the
No wrappers, sorry. We already have too many places in the Linux
kernel and its decompressor that try to work out whether a device
tree or ATAGs are present and how large, and that is done in assembly
code. We don't need more complexity to deal with some kind of
wrapping of device trees as well.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up
prev parent reply other threads:[~2018-05-29 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1523956215-28154-1-git-send-email-t-kristo@ti.com>
[not found] ` <1523956215-28154-13-git-send-email-t-kristo@ti.com>
[not found] ` <20180417092924.GB20335@flint.armlinux.org.uk>
[not found] ` <ad5ef67d-d566-0034-a7cd-09a549cbd6d7@ti.com>
[not found] ` <20180417144913.GD5669@atomide.com>
2018-05-21 6:57 ` [RFC 12/13] ARM: dts: ti: add dra71-evm FIT description file Tero Kristo
2018-05-22 20:01 ` Rob Herring
2018-05-23 5:55 ` Tero Kristo
2018-05-23 14:13 ` Rob Herring
2018-05-23 18:37 ` Tony Lindgren
2018-05-29 17:05 ` Frank Rowand
2018-05-29 17:33 ` Russell King - ARM Linux
2018-05-29 22:45 ` Frank Rowand
2018-05-29 22:51 ` Russell King - ARM Linux [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180529225114.GO17671@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).