public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Alistair Francis" <alistair23@gmail.com>
To: devel@edk2.groups.io, tim.lewis@insyde.com
Cc: Alan Weng <alan.weng@insyde.com>, Leon Chen <leon.chen@insyde.com>
Subject: Re: [edk2-devel] SPDM Transports
Date: Wed, 2 Oct 2024 13:38:48 +1000	[thread overview]
Message-ID: <CAKmqyKM7pb_aYmc=NZynOWQTJFDSQcMhf5DyW48ehOV-N1N5Dw@mail.gmail.com> (raw)
In-Reply-To: <TYSPR02MB8447F6E6AC630637CC5A5F6383772@TYSPR02MB8447.apcprd02.prod.outlook.com>

Hey Tim,

From my understanding the SPDM support in EDK2 is still very new and
not yet (at least last time I looked) actually connected to anything.

Supporting a range of SPDM transports is important. It's not just MCTP
and DOE, but the storage (ATA, SCSI and NVMe) protocols as well that
should be supported.

It would be great if any abstraction takes into account a range of
transport methods, at least allowing them to be implemented later. I'm
currently slowly working towards DOE support [1], but if you are able
to design a general SPDM abstraction that would be great and I would
be happy to help where I can, although I'm not an EDK2 expert.

1: https://github.com/tianocore/edk2/pull/5715

Alistair

On Wed, Oct 2, 2024 at 3:31 AM Tim Lewis via groups.io
<tim.lewis=insyde.com@groups.io> wrote:
>
> 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 (#120590): https://edk2.groups.io/g/devel/message/120590
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]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-10-02  3:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 17:31 [edk2-devel] SPDM Transports Tim Lewis via groups.io
2024-10-02  3:38 ` Alistair Francis [this message]
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='CAKmqyKM7pb_aYmc=NZynOWQTJFDSQcMhf5DyW48ehOV-N1N5Dw@mail.gmail.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