On Sat, 2005-01-15 at 16:38, Roland Dreier wrote: > Hal> 1. PortInfo::CapabilityMask starts off as 0x500a68, which is: > Hal> Trap, APM, SLMapping, SystemImageGUID, VendorClass, and > Hal> CapabilityMaskNotice supported. > > Hal> Is that how it should be ? > > Obviously it depends on your device but that seems to be a reasonable > set of capabilities for an HCA.
In terms of CapabilityMaskNotice, what causes/is supposed to cause the trap/notice to be generated when the capability mask is set (e.g. issm) ? (I know it is the SMA's responsibility but am asking in terms of how OpenIB is/is to be implemented). I ddidn't see this trap sent when issm was set. I think we may be better off turning this off at least in the short term although it is likely only a minor conformance issue. APM will be supported but isn't right now (either in CM or the driver) but this won't cause an issue until CM is on. > Hal> 2. Also, if and when we get to them, is issm a precedent for > Hal> CM, device management, boot management, SNMP tunneling, ... ? > > I guess so, although I think CM is going to be handled in the kernel. > Of course if someone has a better idea for an interface, now would be > a good time to suggest it. Is this the reason for the request for additional device IDs ? Are you envisioning others ? -- Hal _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
