MCTP protocol support in OpenBMC?

[Supreeth Venkatesh]

On Thu, 2018-11-15 at 16:24 +0000, Rapkiewicz, Pawel wrote:
> Hi,
>  
> We’re interested in MCTP involvement, so please count us in for any
> further discussions, and WG participation.
Thanks Pawel/Sharad/Nilan for your involvement. Anyone else interested
please chime in as well.
I guess the first step is to review initial proposal (Sketches) from
Jeremy and see if we should form a WG or discuss it over the mailing
list.
>  
> Regards,
> Pawel
>  
> From: openbmc [mailto:
> openbmc-bounces+pawel.rapkiewicz=intel.com at lists.ozlabs.org] On
> Behalf Of Supreeth Venkatesh
> Sent: Thursday, November 15, 2018 4:47 PM
> To: Emily Shaffer <emilyshaffer at google.com>
> Cc: openbmc at lists.ozlabs.org; Dong Wei <Dong.Wei at arm.com>; David
> Thompson <dthompson at mellanox.com>
> Subject: RE: MCTP protocol support in OpenBMC?
>  
> Thanks Emily. Based on feedback from others, we can decide whether we
> should form a WG or should use alternate mechanism.
>  
> Supreeth
>  
> From: Emily Shaffer <emilyshaffer at google.com> 
> Sent: Wednesday, November 14, 2018 1:02 PM
> To: Supreeth Venkatesh <Supreeth.Venkatesh at arm.com>
> Cc: Jeremy Kerr <jk at ozlabs.org>; David Thompson <
> dthompson at mellanox.com>; openbmc at lists.ozlabs.org; Dong Wei <
> Dong.Wei at arm.com>
> Subject: Re: MCTP protocol support in OpenBMC?
>  
> Google is interested in investigating MCTP as well. I'd love to join
> the wg.
>  
> Emily
>  
> On Wed, Nov 14, 2018 at 8:14 AM Supreeth Venkatesh <
> Supreeth.Venkatesh at arm.com> wrote:
> > David/Jeremy,
> > 
> > We (@ arm) are also interested in contributing MCTP to OpenBMC.
> > We are in the process of getting CLA signed.
> > We have the same concern regarding duplicating work.
> > We would like to collaborate with OpenBMC folks  who are interested
> > in this topic. (maybe form a Workgroup to discuss this).
> > 
> > Thanks,
> > Supreeth
> > 
> > -----Original Message-----
> > From: openbmc <
> > openbmc-bounces+supreeth.venkatesh=arm.com at lists.ozlabs.org> On
> > Behalf Of Jeremy Kerr
> > Sent: Wednesday, November 14, 2018 8:00 AM
> > To: David Thompson <dthompson at mellanox.com>; 
> > openbmc at lists.ozlabs.org
> > Subject: Re: MCTP protocol support in OpenBMC?
> > 
> > Hi David and Rick,
> > 
> > > Does OpenBMC currently have any support for MCTP protocol layer,
> > or is
> > > there a plan to deliver something like this in the future?  I'd
> > be
> > > very interested to hear about any future plans related to MCTP
> > stack.
> > 
> > Us too! I'm interested in looking at MCTP, and am in the middle of
> > doing a little prototyping with our host firmware stack.
> > 
> > I'd also like to avoid duplicating work though, have you (or
> > others) made progress on this since this initial email? I know
> > there was a presentation on MCTP at the recent hackathon, but I'm
> > not sure if any solid plans came from that.
> > 
> > If not, I'd be happy to sketch out an architecture for this...
> > 
> > Cheers,
> > 
> > 
> > Jeremy
> > IMPORTANT NOTICE: The contents of this email and any attachments
> > are confidential and may also be privileged. If you are not the
> > intended recipient, please notify the sender immediately and do not
> > disclose the contents to any other person, use it for any purpose,
> > or store or copy the information in any medium. Thank you.
> 
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose
> the contents to any other person, use it for any purpose, or store or
> copy the information in any medium. Thank you.
> ---------------------------------------------------------------------
> Intel Technology Poland sp. z o.o.
> ul. Słowackiego 173 | 80-298 Gdańsk | Sąd Rejonowy Gdańsk Północ |
> VII Wydział Gospodarczy Krajowego Rejestru Sądowego - KRS 101882 |
> NIP 957-07-52-316 | Kapitał zakładowy 200.000 PLN.
> Ta wiadomość wraz z załącznikami jest przeznaczona dla określonego
> adresata i może zawierać informacje poufne. W razie przypadkowego
> otrzymania tej wiadomości, prosimy o powiadomienie nadawcy oraz
> trwałe jej usunięcie; jakiekolwiek przeglądanie lub rozpowszechnianie
> jest zabronione.
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). If you are not the
> intended recipient, please contact the sender and delete all copies;
> any review or distribution by others is strictly prohibited.