Success! .. I backported drivers/bluetooth/bcm203x.c from 2.6.20 to 2.6.18 and recompiled the module within the 2.6.20 source. My BT-120 device is back online in fiesty!
I'll attach a diff here of what I did, it's very straight forward.
I still need to test to see if 2.6.21-rc2 or later already addresses this issue.
Unfortunately, due to a lack of kernel hacking experience, I'm not sure if I can actually debug Marcel Holtmann's original check-in so that it properly loads the firmware using the correct "work queue" way :)
Success! .. I backported drivers/ bluetooth/ bcm203x. c from 2.6.20 to 2.6.18 and recompiled the module within the 2.6.20 source. My BT-120 device is back online in fiesty!
I'll attach a diff here of what I did, it's very straight forward.
I still need to test to see if 2.6.21-rc2 or later already addresses this issue.
Unfortunately, due to a lack of kernel hacking experience, I'm not sure if I can actually debug Marcel Holtmann's original check-in so that it properly loads the firmware using the correct "work queue" way :)