Andy Green wrote:
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).
Unfortunately, that is a necessary result of this type of reverse-engineering. If Broadcom put some function in the firmware, we have to leave it there as we have no idea what would break.
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.
It isn't that it is blessed or correct, but that it has been tested. Your version has not. Who knows what else might have changed? Once we know the version with the different behavior, a warning message can be prepared. I don't think anyone knew about this problem until you submitted your patch.
Can I still get the firmware version from fwcutter if I don't have the original Windows binary the firmware came from?
AFAIK, fwcutter can only get the version from the foreign driver. It can be gotten from the dmesg output of your inlaws computer, or if you have the extracted firmware files here, you can bundle them up and email them to me privately.
Larry - 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
