From: "Winiarska, Iwona" <iwona.winiarska@intel.com>
To: "venture@google.com" <venture@google.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"titusr@google.com" <titusr@google.com>
Cc: "tmaimon77@gmail.com" <tmaimon77@gmail.com>
Subject: Re: Introducing PECI support in Qemu
Date: Thu, 16 Dec 2021 17:06:33 +0000 [thread overview]
Message-ID: <00c14e7209eabffd78bc36d3cc4ac0d4b37eba00.camel@intel.com> (raw)
In-Reply-To: <CAO=notwUAezOS58BBPL4-fzENrUj55Tbdi1Lwvjz1Y_vpc69uA@mail.gmail.com>
On Thu, 2021-12-16 at 08:03 -0800, Patrick Venture wrote:
> Hi all;
>
> My team has a working PECI bus/device in Qemu, but we only have internal board
> specifications that enable it. We'd like to upstream it as soon as possible,
> but obviously we can't enable testing for it without an upstream board that uses
> it. We only have it attached to Nuvoton 7xx presently, but are slated to enable
> it for the Aspeed series in the next quarter.
>
> Does anyone have an upstream Nuvoton 7xx series BMC board that has PECI enabled
> in the DTS, where we can enable it to their qemu board to enable the upstream
> testing? (think: qtest).
If you mean Linux kernel or OpenBMC, I don't think any upstream BMC board has
PECI enabled.
In case of Linux, PECI subsystem patches with Aspeed support are still under
review:
https://lore.kernel.org/lkml/20211123140706.2945700-1-iwona.winiarska@intel.com/
(Couple of days ago, Tomer Maimon sent patches that added PECI support for
Nuvoton and were tested on NPCM750 and NPCM845 BMC:
https://lists.ozlabs.org/pipermail/openbmc/2021-December/028602.html)
When it comes to OpenBMC upstream, PECI support was dropped some time ago and,
as far as I know, OpenBMC project won't pull it until it is merged into Linux
upstream.
-Iwona
>
> Patrick
prev parent reply other threads:[~2021-12-16 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 16:03 Introducing PECI support in Qemu Patrick Venture
2021-12-16 17:06 ` Winiarska, Iwona [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=00c14e7209eabffd78bc36d3cc4ac0d4b37eba00.camel@intel.com \
--to=iwona.winiarska@intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=qemu-devel@nongnu.org \
--cc=titusr@google.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.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;
as well as URLs for NNTP newsgroup(s).