[Openib-windows] RE: backlog?

[Yossi Leybovich]

> -----Original Message-----
> From: Fab Tillier [mailto:ftillier at silverstorm.com] 
> Sent: Thursday, December 08, 2005 7:10 PM
> To: Yossi Leybovich; Tzachi Dar
> Cc: Gilad Shainer; Erez Cohen; Aviram Gutman
> Subject: RE: backlog?
> 
> > From: Yossi Leybovich [mailto:sleybo at mellanox.co.il]
> > Sent: Thursday, December 08, 2005 6:27 AM
> > 
> > Hi Fab,
> > 
> > two more things:
> > 
> > 1. Tzachi comment about the RC files using the _DEBUG macro 
> instead of 
> > DBR macro
> 
> Oh, thanks, I'd forgotten about that one.
> 
> > 2. The cr space patch . I know that its have security 
> problem , BUT on 
> > the current state of the our stack user can not burn new FW 
> (user must 
> > switch to Linux machine and burn it).
> > There are many bugs that were fixed in the new FW and many 
> performance 
> > enhancement.
> > I think you should reconsider and insert the patch and 
> enable users to 
> > use flint to burn new FW.
> 
> There is an HCA FW update utility in SVN already, under 
> tools\hcafwupdate, so FW update functionality is there.  It 
> is slow, but until we fix the security issues of the CR space 
> mappings I don't feel comfortable putting that functionality in.
> 
> > About security issues , lets wait and solve them with the new low 
> > level driver.
> 
> Is there something that makes the hcafwupdate utility not 
> work properly?
> 

Yes. Mellanox add block type to its new FW and hcafwupdate tool don't
recognize it.
If I remember correctly I tried to burn few months ago and got the msg
of unrecognized socket.
(you can try it yourself with new FW)
That the reason I push to insert the CR space mapping , this will enable
users to use Mellanox flint which is the most updated tool with the
latest FW.


> Thanks,
> 
> - Fab
>