<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">We’re interested in MCTP involvement, so please count us in for any further discussions, and WG participation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Pawel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_____replyseparator"></a><b>From:</b> openbmc [mailto:openbmc-bounces+pawel.rapkiewicz=intel.com@lists.ozlabs.org]
<b>On Behalf Of </b>Supreeth Venkatesh<br>
<b>Sent:</b> Thursday, November 15, 2018 4:47 PM<br>
<b>To:</b> Emily Shaffer <emilyshaffer@google.com><br>
<b>Cc:</b> openbmc@lists.ozlabs.org; Dong Wei <Dong.Wei@arm.com>; David Thompson <dthompson@mellanox.com><br>
<b>Subject:</b> RE: MCTP protocol support in OpenBMC?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks Emily. Based on feedback from others, we can decide whether we should form a WG or should use alternate mechanism.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Supreeth<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>From:</b> Emily Shaffer <<a href="mailto:emilyshaffer@google.com">emilyshaffer@google.com</a>>
<br>
<b>Sent:</b> Wednesday, November 14, 2018 1:02 PM<br>
<b>To:</b> Supreeth Venkatesh <<a href="mailto:Supreeth.Venkatesh@arm.com">Supreeth.Venkatesh@arm.com</a>><br>
<b>Cc:</b> Jeremy Kerr <<a href="mailto:jk@ozlabs.org">jk@ozlabs.org</a>>; David Thompson <<a href="mailto:dthompson@mellanox.com">dthompson@mellanox.com</a>>;
<a href="mailto:openbmc@lists.ozlabs.org">openbmc@lists.ozlabs.org</a>; Dong Wei <<a href="mailto:Dong.Wei@arm.com">Dong.Wei@arm.com</a>><br>
<b>Subject:</b> Re: MCTP protocol support in OpenBMC?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Google is interested in investigating MCTP as well. I'd love to join the wg.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Emily<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, Nov 14, 2018 at 8:14 AM Supreeth Venkatesh <<a href="mailto:Supreeth.Venkatesh@arm.com">Supreeth.Venkatesh@arm.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal">David/Jeremy,<br>
<br>
We (@ arm) are also interested in contributing MCTP to OpenBMC.<br>
We are in the process of getting CLA signed.<br>
We have the same concern regarding duplicating work.<br>
We would like to collaborate with OpenBMC folks who are interested in this topic. (maybe form a Workgroup to discuss this).<br>
<br>
Thanks,<br>
Supreeth<br>
<br>
-----Original Message-----<br>
From: openbmc <openbmc-bounces+supreeth.venkatesh=<a href="mailto:arm.com@lists.ozlabs.org" target="_blank">arm.com@lists.ozlabs.org</a>> On Behalf Of Jeremy Kerr<br>
Sent: Wednesday, November 14, 2018 8:00 AM<br>
To: David Thompson <<a href="mailto:dthompson@mellanox.com" target="_blank">dthompson@mellanox.com</a>>;
<a href="mailto:openbmc@lists.ozlabs.org" target="_blank">openbmc@lists.ozlabs.org</a><br>
Subject: Re: MCTP protocol support in OpenBMC?<br>
<br>
Hi David and Rick,<br>
<br>
> Does OpenBMC currently have any support for MCTP protocol layer, or is<br>
> there a plan to deliver something like this in the future? I'd be<br>
> very interested to hear about any future plans related to MCTP stack.<br>
<br>
Us too! I'm interested in looking at MCTP, and am in the middle of doing a little prototyping with our host firmware stack.<br>
<br>
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.<br>
<br>
If not, I'd be happy to sketch out an architecture for this...<br>
<br>
Cheers,<br>
<br>
<br>
Jeremy<br>
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.<o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">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.
<o:p></o:p></span></p>
</div>
<p>---------------------------------------------------------------------<br>
<strong style="line-height: 11.25pt;"><span style="font-size: 9pt; color:
#595959;"><span style="font-family: 'Arial Narrow', sans-serif;">Intel
Technology Poland sp. z o.o.<br></span></span></strong><span style="color:
#595959; font-family: 'Arial Narrow', sans-serif; font-size: 9pt; line-height:
11.25pt;">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.</span></p><p>
<span style="font-size:8.0pt;font-family:"Arial
Narrow","sans-serif";
mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family:Arial;
color:#595959;mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:
AR-SA">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.<br>
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.</span></p><p class="MsoNormal"><o:p></o:p></p>
</body>
</html>