Not all OSes support if_printf(), printf(), etc, so start migrating
the printf / log routines into net80211 routines that are implemented
in ieee80211_freebsd.c .
Migrate ic_printf() to ieee80211_ic_printf() via a macro for testing.
Differential D50642
net80211: create ieee80211_vap_printf() / ieee80211_ic_printf() for printing adrian on Mon, Jun 2, 2:11 AM. Authored by Tags Referenced Files
Details
Not all OSes support if_printf(), printf(), etc, so start migrating Migrate ic_printf() to ieee80211_ic_printf() via a macro for testing.
Diff Detail
Event TimelineComment Actions So i was thinking if we can start using ieee80211 for standards things and use a net80211 prefix for our own stuff (at least for anything new or we change)? I am still torn on the vlog(INFO; I know if_log went there but we have a lot of things which will not show up on console that way anymore; I already know from the if_log bit and that's a bit annoying; also re-ordering and overlappig... Almost calls in the future for a version to take a debug bool or foo_debug or something what the things can come out appropriately and the others to go at vprintf; I am just thinking loudly... Comment Actions I think that's a good idea. I'll go update the diff stack.
It would be nice to have an if_vprintf(), device_vprintf(), etc so i didn't have to do these hijinx but we don't, hence why I'm currently rolling my own.
|