From: Paul Cercueil <paul@crapouillou.net>
To: Rob Herring <robh@kernel.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
od@zcrc.me, MIPS <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: boot/compressed: Copy DTB to aligned address
Date: Wed, 03 Mar 2021 20:57:56 +0000 [thread overview]
Message-ID: <KKVEPQ.TT4PXOZ85QWA1@crapouillou.net> (raw)
In-Reply-To: <CAL_JsqLfkjC4c4PYfm6yJLZMH-5WaKA_mr9ziJ1J63UohcgRCw@mail.gmail.com>
Hi Rob,
Le mer. 3 mars 2021 à 14:37, Rob Herring <robh@kernel.org> a écrit :
> On Wed, Mar 3, 2021 at 1:33 PM Paul Cercueil <paul@crapouillou.net>
> wrote:
>>
>> Since 5.12-rc1, the Device Tree blob must now be properly aligned.
>
> I had checked the other built-in cases as microblaze broke too, but
> missed some of the many ways MIPS can have a dtb. Appended and
> built-in DTBs were supposed to be temporary. :(
Actually I'm glad these options are here, they make debugging much
easier, when working on new SoCs.
-Paul
>> Therefore, the decompress routine must be careful to copy the blob
>> at
>> the next aligned address after the kernel image.
>>
>> This commit fixes the kernel sometimes not booting with a Device
>> Tree
>> blob appended to it.
>>
>> Fixes: c4d5e638d6e9 ("scripts/dtc: Update to upstream version
>> v1.6.0-51-g183df9e9c2b9")
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> ---
>> arch/mips/boot/compressed/decompress.c | 8 ++++++++
>> arch/mips/kernel/vmlinux.lds.S | 2 ++
>> 2 files changed, 10 insertions(+)
>
> Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-03-04 0:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 19:33 [PATCH] MIPS: boot/compressed: Copy DTB to aligned address Paul Cercueil
2021-03-03 20:37 ` Rob Herring
2021-03-03 20:57 ` Paul Cercueil [this message]
2021-03-04 22:53 ` Maciej W. Rozycki
2021-03-06 8:45 ` Thomas Bogendoerfer
2021-03-06 21:35 ` Rob Herring
2021-03-06 22:58 ` Thomas Bogendoerfer
2021-03-08 17:04 ` Rob Herring
2021-03-08 17:45 ` Thomas Bogendoerfer
2021-03-08 10:53 ` Thomas Bogendoerfer
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=KKVEPQ.TT4PXOZ85QWA1@crapouillou.net \
--to=paul@crapouillou.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=od@zcrc.me \
--cc=robh@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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