OpenSBI Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Yao Zi <me@ziyao.cc>
Cc: michael.opdenacker@rootcommit.com, Drew Fustini <drew@pdp7.com>,
	guoren@kernel.org, wefu@redhat.com, inochiama@gmail.com,
	opensbi@lists.infradead.org
Subject: Re: TH1520: broken CPU count detection
Date: Mon, 28 Sep 2026 10:44:47 +0200	[thread overview]
Message-ID: <8a096379-443b-415d-9263-4f4709ba4f49@rootcommit.com> (raw)
In-Reply-To: <7d24d195-02e4-46d3-b0a3-4c48bf6a0d90@rootcommit.com>


On 9/20/26 11:09 AM, Michael Opdenacker wrote:
>
> As you predicted, the issue detecting the number of CPU cores is gone.
> I'm preparing a meta-riscv layer update for Yocto to automate all this.
>

FYI, these are now supported by Yocto's meta-riscv for the BeagleV Ahead 
board:
https://github.com/riscv/meta-riscv/blob/master/docs/BeagleV-Ahead.md

We also have a pull-request under review for LicheePI 4A, with mainline 
DDR training, OpenSBI, U-Boot and Linux:
https://github.com/riscv/meta-riscv/pull/698

Thanks again!
Michael.

-- 
Root Commit
Embedded Linux Training and Consulting. Yocto Ambassador.
https://rootcommit.com


-- 
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi

      parent reply	other threads:[~2026-09-28  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  7:31 TH1520: broken CPU count detection Michael Opdenacker
2026-09-16 16:42 ` Yao Zi
2026-09-17 10:54   ` Michael Opdenacker
2026-09-17 17:36     ` Yao Zi
     [not found]       ` <7d24d195-02e4-46d3-b0a3-4c48bf6a0d90@rootcommit.com>
2026-09-28  8:44         ` Michael Opdenacker [this message]

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=8a096379-443b-415d-9263-4f4709ba4f49@rootcommit.com \
    --to=michael.opdenacker@rootcommit.com \
    --cc=drew@pdp7.com \
    --cc=guoren@kernel.org \
    --cc=inochiama@gmail.com \
    --cc=me@ziyao.cc \
    --cc=opensbi@lists.infradead.org \
    --cc=wefu@redhat.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