Comment 27 for bug 496093

I've looked at the upstream sources (including -next), and I haven't seen anything that appears to fix the issue. At this point, we're likely just waiting for the fix to be merged from the ralink sources into upstream.