linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: imx: Pass 'chosen' and 'memory' nodes
Date: Thu, 19 Jan 2017 14:56:42 +0000	[thread overview]
Message-ID: <20170119145642.GC27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20170119144641.jxj2bqg5uqjol23x@pengutronix.de>

On Thu, Jan 19, 2017 at 03:46:41PM +0100, Uwe Kleine-K?nig wrote:
> On Thu, Jan 19, 2017 at 12:35:40PM -0200, Fabio Estevam wrote:
> > Hi Uwe,
> > 
> > On Thu, Jan 19, 2017 at 12:13 PM, Uwe Kleine-K?nig
> > <u.kleine-koenig@pengutronix.de> wrote:
> > 
> > > Would it be nice to add a comment about why this was added? Something to
> > > prevent a cleanup like "remove empty nodes and invalid memory
> > > configurations".
> > 
> > Do you mean something like this?
> > 
> > /* "chosen" and "memory" nodes are mandatory */
> > chosen {};
> > memory { device_type = "memory"; reg = <0 0>; };
> 
> Not very helpful comment. Something like:
> 
> 	/*
> 	 * The decompressor relies on a pre-existing chosen node to be
> 	 * available to insert the command line and merge other ATAGS
> 	 * info.
> 	 */
> 
> Is it difficult to fix the decompressor?

... and that comment would be wrong.  Yes, the decompressor relies on it,
as do some uboot versions.

> I didn't understood the breakage regarding the memory node good enough
> to suggest a comment for that.

A missing memory node appears to prevent some uboot versions supplying
any kind of memory layout to the kernel, which then causes the kernel to
crash very early during boot.

Again, this is not using appended DTB - this is using a separately loaded
DTB in uboot.  uboot fails to update the dtb if these nodes are missing.

Frankly, I think the original change (removing the skeleton.dtsi include)
was misguided and needs to be reverted - the change is imho built upon an
incorrect assumption that nothing in skeleton.dtsi is required.  That's
clearly false.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2017-01-19 14:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 14:02 [PATCH v2] ARM: dts: imx: Pass 'chosen' and 'memory' nodes Fabio Estevam
2017-01-19 14:13 ` Uwe Kleine-König
2017-01-19 14:35   ` Fabio Estevam
2017-01-19 14:46     ` Uwe Kleine-König
2017-01-19 14:56       ` Russell King - ARM Linux [this message]
2017-01-19 15:57         ` Fabio Estevam
2017-01-19 16:14         ` Uwe Kleine-König
2017-01-25 21:13           ` Frank Rowand
2017-01-25 22:46             ` Rob Herring
2017-01-26  0:30               ` Frank Rowand
2017-01-30 18:54             ` Russell King - ARM Linux
2017-01-30 19:07               ` Fabio Estevam
2017-01-30 19:47               ` Uwe Kleine-König
2017-02-01 13:30               ` Stefan Wahren
2017-02-06 10:49                 ` Stefan Wahren
2017-02-06 11:05                   ` Fabio Estevam
2017-02-07 15:19                     ` Arnd Bergmann

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=20170119145642.GC27312@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).