All,

In a nutshell: What is the correct usage of the m_instance member in 
mac_register_t?

The Nemo design docs seem to suggest this can be used for multi-port 
(multiple MAC's per dev_info_t?) devices, however I am not sure how this 
should be implemented.

Does the use of this member require multiple invocations of 
mac_register() ? If so, does this mean tracking multiple mac_handle_t 
instances in the driver soft state?

Thanks in advance,

Steve

-- 
Yet magic and hierarchy
arise from the same source,
and this source has a null pointer.

Reference the NULL within NULL,
it is the gateway to all wizardry.
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to