On Wednesday 10 of April 2013 17:21:57 Eugene Krasnikov wrote: Hi, > Thanx for reply. That also works. > But is it a solution or workaround? May be there should be smarter > check than just a kernel version? Note that android kernel is not vanilla kernel. If you have custom kernel (e.g android kernel) with extra features backported you need to enable support for those features in compat-drivers for your kernel i.e. mark it as applicable for lower kernel version (comparing to vanilla kernel which introduced this feature) The 'proper' solution would be to have support for Android (or CM) kernel in compat-drivers (same as eg. RH kernel would). But Android kernels varies heavily among devices and it could be hard to support all of them. It is also worth noting that often custom non-mainlined code doesn't even build when configured as module e.g. bluesleep driver from grouper kernel. This is extra obstacle as one would have to fix or disable such offending code. -- BR Szymon Janc -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
