Johannes Berg <johannes@xxxxxxxxxxxxxxxx> writes: > On Wed, 2009-03-25 at 11:01 +0200, Kalle Valo wrote: > >> > This actually affects the entire stack, take for example the BSS load >> > element, which could potentially change frequently. Unless >> > wpa_supplicant would want to use it for roaming, we could ignore it. >> > >> > However, how do we know which elements the various pieces of the stack >> > need? >> >> I think we can just start with a fixed list and start improving that. >> Or did you think of creating the list dynamically? > > It has to be dynamic, no? Much of the information in there would be > things wpa_supplicant is only interested in. If it was just the kernel > code -- yes, we could just have a static list somewhere -- but much of > the 11k things for instance are only useful for wpa_supplicant. But if we already know what wpa_supplicant needs, can't we do the first implementation with a static list? Sure, the dynamic list is something we should aim for. Do we have any knowledge how different hardware support beacon checksumming? I only know how stlc45xx does it. -- Kalle Valo -- 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
