OpenSBI Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: opensbi@lists.infradead.org
Subject: Help: commit 6112d58 breaks my kernel boot
Date: Tue, 26 Dec 2023 17:11:00 +0000	[thread overview]
Message-ID: <20231226-apache-lagging-514fe286ce52@spud> (raw)
In-Reply-To: <ZYsGfc/U10S0mKna@errol.ini.cmu.edu>

On Tue, Dec 26, 2023 at 11:59:41AM -0500, Gabriel L. Somlo wrote:
> Hi,
> 
> I recently updated my opensbi sources, and noticed that commit
> 6112d58 ("lib: utils/fdt: Allow to use reg-names when parsing ACLINT")
> breaks booting the (latest upstream) kernel on my LiteX + 4-core Rocket
> setup. Without that commit, the kernel boots fine. With the commit
> applied, I get:

> 		L2: clint at 2000000 {
> 			compatible = "riscv,clint0";
> 			interrupts-extended = <&L4 3 &L4 7 &L14 3 &L14 7 &L24 3 &L24 7 &L34 3 &L34 7>;
> 			reg = <0x2000000 0x10000>;

> 			reg-names = "control";

If you remove this does it boot?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/opensbi/attachments/20231226/e20b3ed6/attachment.sig>

  reply	other threads:[~2023-12-26 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26 16:59 Help: commit 6112d58 breaks my kernel boot Gabriel L. Somlo
2023-12-26 17:11 ` Conor Dooley [this message]
2023-12-26 17:19   ` Gabriel L. Somlo
2023-12-26 17:27     ` Conor Dooley
2023-12-26 17:34       ` Gabriel L. Somlo
2023-12-26 21:54         ` Conor Dooley
2023-12-26 17:28     ` Gabriel L. Somlo
2023-12-26 21:56       ` Conor Dooley
2023-12-26 22:35         ` Gabriel Somlo
2023-12-27  0:50           ` Inochi Amaoto

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=20231226-apache-lagging-514fe286ce52@spud \
    --to=conor@kernel.org \
    --cc=opensbi@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