<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>tools support</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Hi Fab,</FONT>
<BR><FONT SIZE=2>We are going to add support for a number of utilities, managing HCA cards.</FONT>
<BR><FONT SIZE=2>In the first place it's 'flint', which downloads FW into the card.</FONT>
<BR><FONT SIZE=2>There are 2 ways of doing that: via gateway in PCI config space of the HCA cards,</FONT>
<BR><FONT SIZE=2>which is supported by the driver, but is slow, and by direct writing into CR space of the card after mapping it to the address space of the process.</FONT></P>
<P><FONT SIZE=2>The latter way is not suppported now and i'm going to implement it by adding a new vendor call of subtype MAP_CRSPACE (0x0a), which will perform the mapping and return a virtual address to the application.</FONT></P>
<P><FONT SIZE=2>What do you think about it ?</FONT>
</P>
<P><FONT SIZE=2>Another requirement - support of "live fishes" (flash burner devices). </FONT>
<BR><FONT SIZE=2>Any our device can be jumpered to work without CR-space in case when it has an invalid (or doesn't have at all) FW on it. In that case it has device_id greater by one than its original one (e.g. 23109 - for Tavor).</FONT></P>
<P><FONT SIZE=2>The burning is performed by configuration cycles.</FONT>
<BR><FONT SIZE=2>How would you suggest to add support for those devices ?</FONT>
</P>
<P><FONT SIZE=2>Thank you in advance.</FONT>
</P>
<P><FONT SIZE=2>Leonid</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>openib-windows mailing list</FONT>
<BR><FONT SIZE=2>openib-windows@openib.org</FONT>
<BR><FONT SIZE=2><A HREF="http://openib.org/mailman/listinfo/openib-windows" TARGET="_blank">http://openib.org/mailman/listinfo/openib-windows</A></FONT>
</P>
</BODY>
</HTML>