On Thu, 2009-09-03 at 12:08 +0530, Sujith wrote: > CHANNEL_G has to be set for 2GHZ channels since > IS_CHAN_G() checks for this in channelFlags and not in > chanmode. To make things messier, ath9k_hw_process_ini() > checks for CHANNEL_G in chanmode and not in channelFlags. > The supreme, brain-searing fix is to set the > flag in both cases. My impression is that's a workaround for a bug that lies elsewhere. I don't think we should apply such patches. chanmode and channelFlags seem to duplicate each other. I would use an enum for distinctive allowed modes and macros to query if the particular mode has a specific feature (band, modulation, bandwidth etc). The enum could use ORed constants for optimization, but such constants should be used only through the macros. -- Regards, Pavel Roskin -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
