<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" XMLNS:Z =
"urn:schemas-microsoft-com:" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" XMLNS:D = "DAV:" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:z = "#RowsetSchema" xmlns:rs
= "urn:schemas-microsoft-com:rowset" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:x =
"urn:schemas-microsoft-com:office:excel" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:v =
"urn:schemas-microsoft-com:vml"><HEAD><!--[if !mso]>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<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-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle18 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle19 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle21 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
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]-->
<META content="MSHTML 6.00.2900.3243" name=GENERATOR></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=388090617-01052008><FONT face=Arial color=#0000ff size=2>Yes,
because the tools have their own driver.</FONT></SPAN></DIV>
<DIV><SPAN class=388090617-01052008><FONT face=Arial color=#0000ff size=2>One
can work with tools without WinOF and one can use WinOF and the tools
simultaneously.</FONT></SPAN></DIV>
<DIV><SPAN class=388090617-01052008><FONT face=Arial color=#0000ff size=2>(the
latter is needed while debugging firmware-related bugs, for
example)</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> ofw-bounces@lists.openfabrics.org
[mailto:ofw-bounces@lists.openfabrics.org] <B>On Behalf Of </B>Fab
Tillier<BR><B>Sent:</B> Thursday, May 01, 2008 7:10 PM<BR><B>To:</B> Ishai
Rabinovitz; Reuven Amitai; ofw@lists.openfabrics.org<BR><B>Subject:</B> RE:
[ofw] RE: Removing MFT tools from svn<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>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: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;>-Fab<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " color:#1F497D?
Calibri?,?sans-serif?;><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
Tahoma?,?sans-serif??>From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; 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: 10pt; FONT-FAMILY: " color:blue?
Arial?,?sans-serif?;>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: 10pt; FONT-FAMILY: " color:blue?
Arial?,?sans-serif?;>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: 10pt; 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: 10pt; FONT-FAMILY: " color:blue?
Arial?,?sans-serif?;>Thanks</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: " color:blue?
Arial?,?sans-serif?;>Ishai</SPAN><o:p></o:p></P></DIV>
<BLOCKQUOTE
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal><o:p> </o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: "
Tahoma?,?sans-serif??>From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; 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-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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 style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><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-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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 style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><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-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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></BLOCKQUOTE></BODY></HTML>