In message <[EMAIL PROTECTED]>, Brooks Davis writes: >> Somebody please explain how this would work for non-hardware >> interfaces like if_loop, if_tun, if_tap etc ? > >if_dev would be NULL when a device_t was not available. Code which used >this feature would be required to either check that if_dev was non-NULL >before trying to use it or have special knowldege that it only gets >called with struct ifnet instances which have a non-NULL if_dev member. >For instance, driver routines which take a struct ifnet would know that >they are only called on their own ifnet so they could assume they had >filled it in.
So you'd still have to keep the if_name + if_unit around for the drivers which do not have a device_t ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
