If the module builds OK but doesn't load, you could try loading it manually "modprobe wl" and see if any errors show up on the console/syslog/dmesg.
AFAIK the patch you've applied adds support for 3.8 as well as for lowlatency. If this works OK you could try isolating the lowlatency part, as the patch for 3.8 (and 3.9 and 3.10) is already in the Ubuntu package (I'm using 6.30.223 with kernel 3.10 under Ubuntu 12.04 and it works great).
Note that even if this patch actually makes the module work, its legal situation is, as far as I can judge (without being a judge :), not certain.
Interesting :)
If the module builds OK but doesn't load, you could try loading it manually "modprobe wl" and see if any errors show up on the console/ syslog/ dmesg.
AFAIK the patch you've applied adds support for 3.8 as well as for lowlatency. If this works OK you could try isolating the lowlatency part, as the patch for 3.8 (and 3.9 and 3.10) is already in the Ubuntu package (I'm using 6.30.223 with kernel 3.10 under Ubuntu 12.04 and it works great).
Note that even if this patch actually makes the module work, its legal situation is, as far as I can judge (without being a judge :), not certain.