[Openib-windows] Added ability to change IPoIB mtu size

[Fabian Tillier]

Hi folks,

On 11/29/06, Yossi Leybovich <sleybo at dev.mellanox.co.il> wrote:
>
> > -----Original Message-----
> > From: Alex Estrin [mailto:alex.estrin at qlogic.com]
> > Sent: Wednesday, November 29, 2006 6:45 PM
> >
> > Hi,
> >
> > > -----Original Message-----
> > > From: Yossi Leybovich [mailto:sleybo at dev.mellanox.co.il]
> > > Sent: Wednesday, November 29, 2006 11:11 AM
> > >
> > > Hi
> > >
> > > Why do we need that?
> > > Just update the inf and the driver will load. ( or you can fake the
> > > registry key ...).
> >
> > - no updated INF file handy.
> > - Intentionally removed key.
>
> That is true for developers and there are also quick ways to solve the
> problems for developers
> Do you think user use driver from one revision and inf from another?
> Do you think user will delete the registry keys ?
> (I assume that we have some keys that we must have so I don't think we can
> be totally foolproof)

I don't see a problem with having settings that are required for the
driver to load.  There are several of these already.  The problem with
adding new required parameters is that you can't simply update the
driver file for the device (via xcopy), you have to actually update
the driver using the updated INF.  This is tedious to do manually, but
there are ways to do automate it.

In the DDK is a tool, devcon, that lets you update devices from the
command line.  All you need to do is stage the new INF and binary
files, and then run devcon using the following command line as a
template.

devcon update <path to netipoib.inf file> IBA\IPoIB

This command will update all IPoIB instances on a machine.

- Fab