Garrett D'Amore wrote: > You need a way to register your mac callbacks with Nemo. :-) Probably > you want to have a way to associate the MII with a state structure at > registration time as well... unless you believe that the same soft state > used by the rest of nemo will be sufficient (it might be ... I don't > have experience with NICs that support more than a single MII part on > them to know whether an intermediate state structure would be useful or > not. You'd still need a way to identify *which* MII part is active in > the case where multiple MII devices are present on a single NIC part, > though.)
Hrmm. I'm not sure of the best approach, but what I was thinking was to keep additional state in mac_handle_t and handle registering callbacks in mac_register based on the capab. I don't have any experience with multiple MII's either; is this something that should be kept out of scope initially? -- 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. _______________________________________________ networking-discuss mailing list [email protected]
