From: Frank Rowand <frowand.list@gmail.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
"pantelis.antoniou@konsulko.com" <pantelis.antoniou@konsulko.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Hamish Martin <Hamish.Martin@alliedtelesis.co.nz>
Subject: Re: Using device tree overlays in Linux
Date: Tue, 9 Apr 2019 12:19:14 -0700 [thread overview]
Message-ID: <b2e0e55e-38a3-3dfb-3453-f57d7e2e99a3@gmail.com> (raw)
In-Reply-To: <224942bd629e41eaa23ab327b015134e@svr-chch-ex1.atlnz.lc>
On 4/7/19 6:27 PM, Chris Packham wrote:
> Hi Frank,
>
> On 8/04/19 1:05 PM, Frank Rowand wrote:
>> Hi Chris,
>>
>> On 4/3/19 6:50 PM, Chris Packham wrote:
>>> Hi,
>>>
>>> I'm implementing support for some modular Linux based systems using
>>> device tree overlays. The code is working but it seems a little more
>>> fiddly that than it should be so I'm wondering if I'm doing it right.
>>
>> Let me start by saying that I strongly discourage using device tree
>> overlays in the Linux kernel until the support is more baked. For
>> some info on how unbaked overlays are, see:
>>
>> https://elinux.org/Frank%27s_Evolving_Overlay_Thoughts
>>
>> You should consider applying overlays in the Linux kernel to be
>> fragile at best.
>>
>> If you can not figure out how to solve your needs without using
>> overlays, then having the boot loader apply the overlay instead
>> of the kernel applying the overlay avoids most of the issues.
>>
>
> Consider us beta-testers :).
You should read the elinux.org page more carefully. The support
isn't even alpha stage. It is at the level of proof of concept.
I'll update that page to explicitly say the code is proof of
concept.
< snip >
I'll reply to the rest of the email separately.
-Frank
next prev parent reply other threads:[~2019-04-09 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 1:50 Using device tree overlays in Linux Chris Packham
2019-04-06 6:07 ` Rob Herring
2019-04-08 1:05 ` Frank Rowand
2019-04-08 1:27 ` Chris Packham
2019-04-09 19:19 ` Frank Rowand [this message]
2019-04-09 20:54 ` Chris Packham
2019-04-09 19:33 ` Frank Rowand
2019-04-09 20:47 ` Chris Packham
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=b2e0e55e-38a3-3dfb-3453-f57d7e2e99a3@gmail.com \
--to=frowand.list@gmail.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Hamish.Martin@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.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).