From: Andreas Schwab <schwab@suse.de>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: 5.3-rc2: Found incompatible CPU
Date: Wed, 31 Jul 2019 09:33:13 +0200 [thread overview]
Message-ID: <mvmwofy8xqe.fsf@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1907301502240.4874@viisi.sifive.com> (Paul Walmsley's message of "Tue, 30 Jul 2019 15:09:56 -0700 (PDT)")
On Jul 30 2019, Paul Walmsley <paul.walmsley@sifive.com> wrote:
> On Tue, 30 Jul 2019, Andreas Schwab wrote:
>
>> Trying to boot 5.3-rc2 on the HiFive I'm getting "Found incompatible
>> CPU" for each cpu, which means that of_device_is_compatible(node,
>> "riscv") is failing. Any idea?
>
> Here, v5.3-rc2 boots cleanly with upstream DT data, using BBL.
>
> I've noticed problems in the past with some bootloader configurations when
> the DT data is loaded too close to the kernel. When the kernel is
> uncompressed, some or all of the DT data can be overwritten, which can
> cause mysterious DT parsing problems.
Using the latest openSBI (which moved the FDT further away) didn't help.
A fully modular kernel isn't that big anyway. And the fact that the
cpus are found in the first place tells me that the FDT is intact in
general.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-07-31 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 12:51 5.3-rc2: Found incompatible CPU Andreas Schwab
2019-07-30 22:09 ` Paul Walmsley
2019-07-31 7:33 ` Andreas Schwab [this message]
2019-07-31 6:48 ` Atish Patra
2019-07-31 7:36 ` Andreas Schwab
2019-07-31 8:12 ` Anup Patel
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=mvmwofy8xqe.fsf@suse.de \
--to=schwab@suse.de \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.