Somebody in the thread at some point said: > Andy Green wrote: >> >> I never heard of a special blessed firmware before, I don't think that >> the driver made any dmesg when given the non-blessed one, if that is >> what it is? I was given this firmware by the traditional "person on >> IRC" and don't know where it came from, but I still have it here if any >> versioning can be extracted from it. > > Just as API's and ABI's change, the writers of firmware can change their > layout, which is what happened here. Nothing "blessed", just one > behavior before, and a second after, the change. The version info can be > gotten from fwcutter. Understood, that is why I consider it a bad thing that functionality that can be done in the mac80211 driver is pushed into the binary-only firmware when there is a choice (otherwise known as "paranoia", apparently). However you stripped some quoting from Michael: ''But it is actually no problem in reality, as the use-it-or-die firmware doesn't have this problem. So if someone uses another firmware than the one we suggest, he will probably run into more problems, as well. The fix is called: Use the correct firmware. For now, at least.'' I would summarize this that Michael is telling me one pariticular version of firmware - "use it or die firmware" - is especially blessed/correct. It might be an idea to let people know they have strayed from the dependency of the required firmware version in dmesg if indeed there is an effective dependency of the driver on it. Can I still get the firmware version from fwcutter if I don't have the original Windows binary the firmware came from? -Andy - 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
