Comment 81 for bug 217504

I'd like a bit of clarification:
What needs to be done to solve this bug? An in-kernel driver?
Is there some work being done for that or is it waiting for someone to start?
Why does the proposed patch is not released until the 'perfect' solution is ready?