From: "Bartosz Biłas" <b.bilas@grinn-global.com>
To: Marcin Niestroj <m.niestroj@grinn-global.com>,
barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: i.MX6UL: liteSOM: depend on DDR controller settings
Date: Tue, 26 Feb 2019 19:35:13 +0100 [thread overview]
Message-ID: <d89907aa-6202-352b-a228-40365519665a@grinn-global.com> (raw)
In-Reply-To: <20190226130529.12517-1-m.niestroj@grinn-global.com>
Tested-by: Bartosz Bilas <b.bilas@grinn-global.com>
On 26.02.2019 14:05, Marcin Niestroj wrote:
> Initially we depended on DDR controller settings for liteSOM and liteboard. With
> 33fdc89d4cbd ("dts: update to v5.0-rc1") a `device_type = "memory";` property
> was added to imx6ul-litesom.dtsi file, which causes "ram0" to be added with
> 512MB size (value in dtsi) instead of the real 256MB size that is configured in
> barebox-grinn-liteboard-256mb.img. As a result Linux kernel fails to boot.
>
> Lets depend on DDR controller settings, by removing whole `/memory` node from
> device tree. This makes barebox-grinn-liteboard-256mb.img able to boot Linux
> kernel once again.
>
> Reported-by: Bartosz Bilas <b.bilas@grinn-global.com>
> Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
> ---
> arch/arm/dts/imx6ul-liteboard.dts | 1 +
> arch/arm/dts/imx6ul-litesom.dtsi | 8 ++++++++
> 2 files changed, 9 insertions(+)
> create mode 100644 arch/arm/dts/imx6ul-litesom.dtsi
>
> diff --git a/arch/arm/dts/imx6ul-liteboard.dts b/arch/arm/dts/imx6ul-liteboard.dts
> index 03a4bfc78..eb34e11dd 100644
> --- a/arch/arm/dts/imx6ul-liteboard.dts
> +++ b/arch/arm/dts/imx6ul-liteboard.dts
> @@ -42,6 +42,7 @@
> */
>
> #include <arm/imx6ul-liteboard.dts>
> +#include "imx6ul-litesom.dtsi"
>
> / {
> chosen {
> diff --git a/arch/arm/dts/imx6ul-litesom.dtsi b/arch/arm/dts/imx6ul-litesom.dtsi
> new file mode 100644
> index 000000000..8b73bfdd6
> --- /dev/null
> +++ b/arch/arm/dts/imx6ul-litesom.dtsi
> @@ -0,0 +1,8 @@
> +/*
> + * Include file to switch board DTS from using hardcoded memory node
> + * to dynamic memory size detection based on DDR controller settings
> + */
> +
> +/ {
> + /delete-node/ memory@80000000;
> +};
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-02-26 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 13:05 Marcin Niestroj
2019-02-26 18:35 ` Bartosz Biłas [this message]
2019-02-27 7:46 ` Sascha Hauer
2019-02-27 10:04 ` Marcin Niestrój
2019-03-07 7:24 ` Sascha Hauer
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=d89907aa-6202-352b-a228-40365519665a@grinn-global.com \
--to=b.bilas@grinn-global.com \
--cc=barebox@lists.infradead.org \
--cc=m.niestroj@grinn-global.com \
/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