From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Heyi Guo" <guoheyi@linux.alibaba.com>,
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: Tue, 10 Aug 2021 09:15:37 +0930 [thread overview]
Message-ID: <66dc4dc8-74ca-4ccd-94fe-6d819f71226b@www.fastmail.com> (raw)
In-Reply-To: <f5ec563f-6bbc-9eca-1ee0-77e2c04c4ec9@linux.alibaba.com>
On Mon, 9 Aug 2021, at 16:03, Heyi Guo wrote:
> Hi Andrew,
>
>
> On 2021/8/6 下午1:42, Andrew Jeffery wrote:
> > Hello Heyi!
> >
> > On Fri, 6 Aug 2021, at 14:47, Heyi Guo wrote:
> >> Hi,
> >>
> >> We can see that NVMe sensors in dbus-sensors relies on MCTP to get
> >> hardware information. It is using libmctp interfaces to initialize MCTP
> >> and SMBus.
> > To be clear, it's using a fork of libmctp that implements an SMBus
> > binding via a fork of the kernel that exposes a I2C API that isn't
> > upstream.
>
> Could you point out where I can find these forks, including libmctp and
> kernel? So that we can do some initial test with the current
> implementation of NVMeSensor in dbus-sensors.
The relevant forks are under the Intel-BMC Github org:
https://github.com/Intel-BMC/
Hopefully the Intel folks on Cc can give you pointers on how to get it going.
Cheers,
Andrew
prev parent reply other threads:[~2021-08-09 23:46 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
2021-08-09 6:33 ` Heyi Guo
2021-08-09 23:45 ` Andrew Jeffery [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=66dc4dc8-74ca-4ccd-94fe-6d819f71226b@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=ed@tanous.net \
--cc=guoheyi@linux.alibaba.com \
--cc=iwona.winiarska@intel.com \
--cc=jae.hyun.yoo@linux.intel.com \
--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).