Well, including ieee80211_var.h and attempting to compile the code throws dozens of error messages.
In addition, I wonder why IEEE80211_C_BITS is re-defined in ifieee80211.c. ----- Original Message ----- From: Adrian Chadd <adrian.ch...@gmail.com> To: Fehmi Noyan ISI <fnoyan...@yahoo.com> Cc: Freebsd Wireless <firstname.lastname@example.org> Sent: Thursday, November 17, 2016 7:11 PM Subject: Re: Using net80211/IEEE80211_C_BITS macro Hi! Uhm, we could totally break out more bits into separate header files if including ieee80211_var.h doesn't work for you. a On 16 November 2016 at 14:53, Fehmi Noyan ISI via freebsd-wireless <email@example.com> wrote: > Hiya, > > I am working on an API (hopefully will post something about it soon) that, > beyond other stuff, checks wlan driver capabilities (just like ifconfig(1) > does). However, the capabilities macro, which is IEEE80211_C_BITS, is defined > in sys/net80211/ieee80211_var.h and I am not sure whether #include'ing > ieee80211_var.h just for this macro is a good idea or not. > > I have noticed that IEEE80211_C_BITS is re-defined in > sbin/ifconfig/ifieee80211.c to be used by list_capabilities() function; does > this not require update of IEEE80211_C_BITS macro in multiple source files? > > What would be the best approach to use IEEE80211_C_BITS in my source file; > including ieee80211_var.h or re-defining the macro in the source file > (similar to ifconfig(1))? > > Thanks > Fehmi > _______________________________________________ > firstname.lastname@example.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" _______________________________________________ email@example.com mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"