<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You failed to address my concern – will someone downloading the
tools from your website be able to successfully run the tools with binaries
built from the WinOF SVN? Requiring a driver change to update firmware isn’t
really acceptable.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-Fab<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Ishai Rabinovitz
[mailto:ishai@mellanox.co.il] <br>
<b>Sent:</b> Thursday, May 01, 2008 5:10 AM<br>
<b>To:</b> Fab Tillier; Reuven Amitai; ofw@lists.openfabrics.org<br>
<b>Subject:</b> RE: [ofw] RE: Removing MFT tools from svn<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I understand that there is an old decision not to include the
tools as part of the WinOF releases.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Since this is the current state, I do not see a reason to have the
tools code in the SVN. Customers can download the tools from the HCA
manufacturer</span><span style='color:black'> </span><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>site (In any case
they are downloading the firmware from this site) and do not
need to download the code and compile it on their own.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Thanks</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Ishai</span><o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> ofw-bounces@lists.openfabrics.org
[mailto:ofw-bounces@lists.openfabrics.org] <b>On Behalf Of </b>Fab Tillier<br>
<b>Sent:</b> Wednesday, April 30, 2008 8:46 PM<br>
<b>To:</b> Reuven Amitai; ofw@lists.openfabrics.org<br>
<b>Subject:</b> [ofw] RE: Removing MFT tools from svn</span><o:p></o:p></p>
<p class=MsoNormal>Why not have the maintainers do their job and actually
maintain the code? This goes for OpenSM and the FW tools, probably other
bits in the tree too.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Fwupdate I think is obsolete. I don’t know about the
others.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>-Fab<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b>From:</b> Reuven Amitai [mailto:reuven@mellanox.co.il] <br>
<b>Sent:</b> Wednesday, April 30, 2008 10:42 AM<br>
<b>To:</b> Fab Tillier; ofw@lists.openfabrics.org<br>
<b>Subject:</b> RE: Removing MFT tools from svn<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>Please see inline ..<o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b>From:</b> Fab Tillier
[mailto:ftillier@windows.microsoft.com] <br>
<b>Sent:</b> Wednesday, April 30, 2008 8:25 PM<br>
<b>To:</b> Reuven Amitai; ofw@lists.openfabrics.org<br>
<b>Subject:</b> RE: Removing MFT tools from svn<o:p></o:p></p>
<p class=MsoNormal>Will the FW package on the Mellanox downloads page work and
be supported with any binaries built from the WinOF SVN source? Is
Mellanox stepping up to support this, and release new versions whenever a
change to the drivers is checked into SVN would break a previous version? <o:p></o:p></p>
<p class=MsoNormal>[Reuven] The new FW package doesn't work directly with
IBAL. It's independent which has the benefit in case of inability to install
WinOF from any reason.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’m very weary of having the WinOF SVN become (or rather
having already become) a second class repository where members periodically
dump large amounts of code to bring it up to date with their own internal
tree. I wish people would treat the WinOF SVN more as the primary source
repository for Windows. Community members don’t have visibility in the
various vendor’s internal trees to see the detailed change history, and that
information is lost when large patches are merged in to bring things up to date. <o:p></o:p></p>
<p class=MsoNormal>[Reuven] First, you are right that it's more desirable
that WinOF svn will be the primary repository. We are in the middle of movement
toward achieving that goal.<o:p></o:p></p>
<p class=MsoNormal>nevertheless, there is still difficulties to work with it
(just one to mention: lag for every simple command). Tools
directories synchronized less often. (OFED MFT tools are one major
version ahead). <o:p></o:p></p>
<p class=MsoNormal>Is it preferred to leave it like that ? delete stale
directories (which ones except fwupdate)? or live with outdated tools sources
(I don't know how often they will updated)<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>-Fab<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b>From:</b> ofw-bounces@lists.openfabrics.org [mailto:ofw-bounces@lists.openfabrics.org]
<b>On Behalf Of </b>Reuven Amitai<br>
<b>Sent:</b> Wednesday, April 30, 2008 9:51 AM<br>
<b>To:</b> Fab Tillier; ofw@lists.openfabrics.org<br>
<b>Subject:</b> [ofw] RE: Removing MFT tools from svn<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>My intentions were naive. I suggest to remove these tools
because I wonder who uses these tools directly.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>There is different package (for Mellanox HCAs) that
dedicated for fw tasks which is up to date. Why not use it ?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I understand that OFED insist that the code will be part
from the distribution.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Is there need just to maintain and update the code here
only for review ?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Are there tools that no one use and can be removed
(fwupdate, anything else ?)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Reuven.<o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b>From:</b> Fab Tillier
[mailto:ftillier@windows.microsoft.com] <br>
<b>Sent:</b> Wednesday, April 30, 2008 7:05 PM<br>
<b>To:</b> Reuven Amitai; ofw@lists.openfabrics.org<br>
<b>Subject:</b> RE: Removing MFT tools from svn<o:p></o:p></p>
<p class=MsoNormal>Ask yourself this: are you planning on removing the FW
update utility from OFED and let it be provided by vendors only? If not,
why would you treat the Windows release differently?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>FW update functionality should be part of WinOF. Not
everyone uses vendor releases. There are some stale directories, for sure –
fwupdate is one – and those should be deleted. The rest should be kept
current.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>-Fab<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b>From:</b> ofw-bounces@lists.openfabrics.org
[mailto:ofw-bounces@lists.openfabrics.org] <b>On Behalf Of </b>Reuven Amitai<br>
<b>Sent:</b> Wednesday, April 30, 2008 5:16 AM<br>
<b>To:</b> ofw@lists.openfabrics.org<br>
<b>Subject:</b> [ofw] Removing MFT tools from svn<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>Hi,<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I suggest that the following directories will be
removed from svn repository :<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>fwupdate, flint, mread, mwrite, mst, spark (all located under
trunk\tools).<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>These tools aren't part of WinOF release and should be
supplied by the HCA vendor.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Moreover, the tools aren't updated (1.0.1.2676 version while
2.1.0.4337 at OFED - Linux. I got the versions from other svn)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>What do you think about it?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em>Thanks, Reuven.</em><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</blockquote>
</div>
</body>
</html>