From: Patrick Williams <patrick@stwcx.xyz>
To: AKASH G J <akashgj91@gmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: RISC-V Support in OpenBMC
Date: Fri, 28 Oct 2022 06:42:14 -0500 [thread overview]
Message-ID: <Y1vAFpmfGFC0mOtK@heinlein.stwcx.org.github.beta.tailscale.net> (raw)
In-Reply-To: <CAE33tLG4oOjTmNJ=a0jNEEdTj_501offkYUFcEVwk6rAnZYKSw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Fri, Oct 28, 2022 at 07:30:00PM +0530, AKASH G J wrote:
> Whether OpenBMC supports BMC controller with RISC-V architecture? If so,
> how we can generate BMC firmware image for the BMC controller with RISC-V
> architecture.
There is nothing to preclude a RISC-V based BMC being contributed and
running OpenBMC. Yocto already supports RISC-V, so it should not be
difficult other than getting kernel support for whichever SOC you end up
with.
I am not aware of any RISC-V BMC chips at this time.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2022-10-28 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAE33tLG4oOjTmNJ=a0jNEEdTj_501offkYUFcEVwk6rAnZYKSw@mail.gmail.com>
2022-10-28 11:42 ` Patrick Williams [this message]
2022-10-28 11:47 ` RISC-V Support in OpenBMC Zev Weiss
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=Y1vAFpmfGFC0mOtK@heinlein.stwcx.org.github.beta.tailscale.net \
--to=patrick@stwcx.xyz \
--cc=akashgj91@gmail.com \
--cc=openbmc@lists.ozlabs.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 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.