I have identified another regression introduced by commit f04b3787bbce4567e28069a9ec97dcd804626ac7. On my device it shows up as broken transmission after a suspend/resume cycle. The workaround for it is to boot a known good driver (in my case the vendor driver in OSX) and then reboot (without turning the machine off) into the broken driver. It seems like we unintentionally removed some significant initialization step in that patch. I could not identify it, yet. The patch I sent yesterday did fix two other bugs, but not this one. I am trying to find the reason for this. If someone wants to help searching, the best way would be to look at that patch I mentioned above and compare the stuff that it removes to the stuff that it adds. There must be some tiny line that it removes but does not re-add it at another place. Four eyes see more than two. I have no idea how this bug could be related to the few bugreports in the redhat bugzilla. Though, one could test that by trying a kernel that does not include the patch. Sorry for the inconvenience. -- Greetings Michael. - 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
