[ofw] Expose a vendor defined device in ibbus?

[Deepak Gupta]

Please see the comments below.

Regards
Deepak

On Sat, Dec 20, 2008 at 12:49 AM, Fab Tillier <
ftillier at windows.microsoft.com> wrote:

> > Two comments:
> >
> > The format written in the registry should be extensible.  That is,
> > each vendor ULP will be able to add more fields if it needs them. I
> > guess that the format that Fab has suggested is already such.
>
> How would the bus driver act on these extra fields?  How would the FDO
> driver retrieve these extra parameters form the bus driver?


Nice question.

Since it is the vendor specific application (which will request for device
creation) which wants to associate some extended parameters with the new
child PDO. Hence it can encode these parameters as REG_BINARY in registry
under "extendedparams" value. So bus driver will blindly store these values
as a byte array knowing nothing about their meaning.
Other than normal interface there has to be a extended interface implemented
in bus driver which will return the data upon receiving QUERY_INTERFACE for
extended interface.

Further, since upper FDO is owned by the vendor's driver, it will understand
data format and hence we don't need bus driver to understand anything about
this extended data format.


> > Another thing is that ipoib should also work in this method. This
> > means that the coinstaller that installs the bus filter should also
> > create the needed registry entries for ipoib.
>
> Since the bus driver is an upper filter for the HCA now, it's possible for
> the INF file of the HCA to append the appropriate values to the bus driver's
> child device registry entry when the HCA is installed without a coinstaller
> at all.
>
> -Fab
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20081220/32598037/attachment.html>