[ofw] SVN 1494 commit

Smith, Stan stan.smith at intel.com
Thu Aug 21 13:11:12 PDT 2008


 svn.1494 addresses the following issues.

 ulp\nd\user
  makefile.inc - use wnet & wlh specific files for ia64 (actually x86 binaries as ND is
                 not yet supported for ia64).
  fre_svr-03_ia64\ - new files
  fre_svr-08_ia64\ - updated ND files.

 ulp\ipoib\
        added ndinstall.exe as part of the ipoib install.
      Simplifies ND support in Server 2008 HPC/WDM and other OS/arch flavors.
  netipoib.inx
  netipoib-xp32.inf
  ipoib.cdf
  ipoib32.cdf
  ipoib32-xp.cdf

 core\iou\kernel
  ib_iou.inx - IOU specific items extracted from ib_bus.inf
  SOURCES - mods to create and date/timestamp ib_iou.inf file.
  ib_iou.cdf - catalogue file for driver signing.

 etc\makebin.bat - script to setup tree of binaries suitable for WIX installers.
  Mods to support
    ib_iou.inf
    winverbs*
    ND*

 branches\WinOF\WIX\
  wlh\*\wof.wxs
  wnet\*\wof.wxs
  wxp\x86\wof.wxs
    Support for winverbs, ND, signed ibiou.sys driver.

  CustomActions.vbs

HCA install via WIX installer (CustomActions.vbs) has changed to be simpler for the common case, a single HCA, by installing PCI\VEN_15B3 thus allowing the .inf file to deal with matching the correct Device ID.

For multiple mixed HCA installs (mthca & mlx4), VEN_15B3 is not unique, so the install reverts
to the previous WinOF 1.1 install method of installing by device ID; with a small optimization
being applied.
The 1.1 install method was to traverse a hard-coded list of Device IDs installing until success or EOL. Traverse the list once for mlx4 and then again for mthca when both InfiniHost and ConnectX HCAs are install selected.
The optimization is to query and install for the resident Device ID. The idea is to optimize for success instead of accepting install failures until the resident DeviceID is found.
Additionally the installer doesn't have to hard-code newer ConnectX DeviceIDs, although mthca Device Ids are hard coded.  The assumption is InfiniHost(mthca) DeviceIDs are not likely to be changing.
The install method for mlx4 install is to verify the quired Device ID is not mthca and then install the mlx4 driver (future proof w.r.t. hard-coded Device IDs).






More information about the ofw mailing list