On page 7-111, the last paragraph under the description for MSMReRegisterHardwareOptions should read
as follows:
Upon successful return from MSMReRegisterHardwareOptions, the HSM is responsible for putting the adapter
in a functional state. The HSM must call MSMSetHardwareInterrupt if the HSM is interrupt driven (uses the
interrupt).
On page 3-31, bit 0 should read as follows:
Set to 1 if this logical board is currently shut down.
On page 3-28, the caption for Table 3.4 should say:
... MLIDFlags ...
not
... MLIDSFlags ...
This error also appears in the Revision History.
On page 5-45, in DriverShutdown under Partial Shutdown, add the following note:
Note: The adapter has been disabled at this point, so the only transmissions that will complete are those that
have already been sent to the adapter.
On page 5-45, in DriverShutdown, Complete Shutdown should be changed to read as follows:
A zero value in ECX indicates a complete shutdown. As with a partial shutdown, the MSM sets MLIDStatusFlag, waits
for transmissions in progress to complete and returns the transmit ECBs, and also will return all resources not
allocated directly by the HSM. If the HSM allocated memory using MSMAlloc, it must be returned using MSMFree before
disabling the hardware.
Note: The adapter has been disabled at this point, so the only transmissions that will complete are those that
have already been sent to the adapter.
On page 5-46, in DriverShutdown, under OP_SCOPE_ADAPTER, replace the first sentence of the second paragraph
with:
The MSM disables the adapter's interrupt immediately prior to calling DriverShutdown and does not subsequently
re-enable it.
Every place that the spec says "MSMStatusFlags" should read "MLIDStatusFlags". This occurs
in sections 4, 5 and 7.
On page 4-3, between MSMVirtualBoardLink and MSMStatusFlags, add a new section called MSMDefaultVirtualBoard.
This section should read as follows:
MSMDefaultVirtualBoard is a pointer to the configuration table that contains the identity of the first frame type
loaded. If the frame type is not important, using MSMDefaultVirtualBoard will allow quick access to the configuration
table of the first frame type loaded. Care must be taken to use this only to reference information that is the
same in all configuration tables associated with an adapter.