From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Garrett, Mike (HPE Server Firmware)" <mike.garrett@hpe.com>,
"Ed Tanous" <edtanous@google.com>
Cc: Jeremy Kerr <jk@codeconstruct.com.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
matt@codeconstruct.com.au
Subject: Re: RDE Enablement
Date: Fri, 11 Jun 2021 08:36:32 +0930 [thread overview]
Message-ID: <d792ca2d-3ec3-4a2e-b7f3-b0efa9a12ca3@www.fastmail.com> (raw)
In-Reply-To: <DF4PR8401MB063429AA13146432E80B43DB8F359@DF4PR8401MB0634.NAMPRD84.PROD.OUTLOOK.COM>
On Fri, 11 Jun 2021, at 06:29, Garrett, Mike (HPE Server Firmware) wrote:
> A requirement for this
> to work would be the ability to discover PLDM devices and assign IDs
> (MCTP EID) in order to interrogate them for RDE capabilities. It is
> unclear to me that the current PLDM and MCTP code handles discovery or
> if it assumes devices.
It's being worked on. Jeremy and Matt are working on the kernel socket-based implementation of MCTP and the associated userspace daemon for managing the networks.
Andrew
next prev parent reply other threads:[~2021-06-10 23:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 20:26 RDE Enablement Garrett, Mike (HPE Server Firmware)
2021-06-10 20:32 ` Ed Tanous
2021-06-10 20:59 ` Garrett, Mike (HPE Server Firmware)
2021-06-10 23:06 ` Andrew Jeffery [this message]
2021-06-11 6:53 ` Deepak Kodihalli
2021-06-11 13:31 ` Garrett, Mike (HPE Server Firmware)
2021-08-09 13:50 ` Garrett, Mike (HPE Server Firmware)
2021-07-21 14:16 ` Ed Tanous
2021-07-21 8:34 ` Deepak Kodihalli
2021-07-21 14:23 ` Ed Tanous
2021-07-26 13:53 ` Garrett, Mike (HPE Server Firmware)
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=d792ca2d-3ec3-4a2e-b7f3-b0efa9a12ca3@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=edtanous@google.com \
--cc=jk@codeconstruct.com.au \
--cc=matt@codeconstruct.com.au \
--cc=mike.garrett@hpe.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 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).