Is this bug going to get fixed for Maverick? I tested the kernel at http://people.canonical.com/~ppisati/lp707003/linux-image-2.6.35-903-omap4_2.6.35-903.22_armel.deb and it works fine.
Is this bug going to get fixed for Maverick? I tested the kernel at http:// people. canonical. com/~ppisati/ lp707003/ linux-image- 2.6.35- 903-omap4_ 2.6.35- 903.22_ armel.deb and it works fine.