public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Tim Lewis via groups.io" <tim.lewis=insyde.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Alan Weng <alan.weng@insyde.com>, Leon Chen <leon.chen@insyde.com>
Subject: [edk2-devel] SPDM Transports
Date: Tue, 1 Oct 2024 17:31:18 +0000	[thread overview]
Message-ID: <TYSPR02MB8447F6E6AC630637CC5A5F6383772@TYSPR02MB8447.apcprd02.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 905 bytes --]


We are actively implementing generic SPDM support into our codebase, starting with the code in EDK2. However, we are now trying to separate the SPDM code from PCI DoE (to use MCTP, for example). Right now it seems the EDK2 version is hardcoded for PCI DoE. We would like to add some abstraction and are considering adding a separate driver that can sit on top of the MCTP layer. Do you think we should pursue the driver model or do you have another way to support multiple SPDM transports?

Thanks,

Tim Lewis
CTO, Insyde Software


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120589): https://edk2.groups.io/g/devel/message/120589
Mute This Topic: https://groups.io/mt/108763839/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #1.2: Type: text/html, Size: 4257 bytes --]

[-- Attachment #2: image001.gif --]
[-- Type: image/gif, Size: 3386 bytes --]

             reply	other threads:[~2024-10-01 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 17:31 Tim Lewis via groups.io [this message]
2024-10-02  3:38 ` [edk2-devel] SPDM Transports Alistair Francis
2024-10-07 14:51   ` Yao, Jiewen

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-list 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=TYSPR02MB8447F6E6AC630637CC5A5F6383772@TYSPR02MB8447.apcprd02.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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