From: Heyi Guo <guoheyi@linux.alibaba.com>
To: Jeremy Kerr <jk@codeconstruct.com.au>,
Andrew Jeffery <andrew@aj.id.au>,
openbmc <openbmc@lists.ozlabs.org>
Cc: Zhikui Ren <zhikui.ren@intel.com>,
Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>,
"Winiarska, Iwona" <iwona.winiarska@intel.com>,
Vernon Mauery <vernon.mauery@linux.intel.com>,
Ed Tanous <ed@tanous.net>,
"Thomaiyar,
Richard Marian" <richard.marian.thomaiyar@linux.intel.com>,
"sumanth.bhat@linux.intel.com" <sumanth.bhat@linux.intel.com>
Subject: Re: Question about NVMe MCTP in dbus-sensors
Date: Sun, 8 Aug 2021 15:10:18 +0800 [thread overview]
Message-ID: <debba2ae-88c0-c133-328a-92fe4c2b1d09@linux.alibaba.com> (raw)
In-Reply-To: <556ea2925e85d84f296211cce9ef3572647e9e80.camel@codeconstruct.com.au>
On 2021/8/6 下午5:46, Jeremy Kerr wrote:
> Hi Heyi,
>
>> BTW, when will MCTP be ready in openbmc mainline, including SMBus
>> binding and PCIe binding? Do you have any plan in the future openbmc
>> release?
> We're mostly working on the generic infrastructure components at the
> moment; those are based on their relevant upstream projects rather than
> as parts of OpenBMC specifically. However, the upstream work is going
> well, and the OpenBMC integration shouldn't be too difficult there;
> we'll get that done as necessary.
>
> As for interfaces: I currently have i2c and serial transports working,
> but have no specific plans for PCIe - no hardware to test on. If this
> is something you'd be interested in working on yourself, I can provide
> some pointers.
Yes, we are both interested in SMBus binding and PCIe VDM binding, and
we have supporting hardware platforms (servers with Aspeed 2600 as BMC).
It's my pleasure to make contribution to the community :)
Thanks,
Heyi
>
> Regards,
>
>
> Jeremy
next prev parent reply other threads:[~2021-08-08 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 5:17 Question about NVMe MCTP in dbus-sensors Heyi Guo
2021-08-06 5:40 ` Jeremy Kerr
2021-08-06 5:42 ` Andrew Jeffery
2021-08-06 6:35 ` Heyi Guo
2021-08-06 9:46 ` Jeremy Kerr
2021-08-08 7:10 ` Heyi Guo [this message]
2021-08-09 6:33 ` Heyi Guo
2021-08-09 23:45 ` Andrew Jeffery
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=debba2ae-88c0-c133-328a-92fe4c2b1d09@linux.alibaba.com \
--to=guoheyi@linux.alibaba.com \
--cc=andrew@aj.id.au \
--cc=ed@tanous.net \
--cc=iwona.winiarska@intel.com \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=jk@codeconstruct.com.au \
--cc=openbmc@lists.ozlabs.org \
--cc=richard.marian.thomaiyar@linux.intel.com \
--cc=sumanth.bhat@linux.intel.com \
--cc=vernon.mauery@linux.intel.com \
--cc=zhikui.ren@intel.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).