Dave Airlie wrote:
This is more about initial development stages. We maintain kernel
API/ABI for all in-tree drivers, however before we put a driver into
mainline, we usually need to redo the crazy interfaces that vendors
have come up with. Like 32/64 alignment, passing userspace addresses
into the kernel, passing phy addresses to userspace etc. If the
userspace binary is closed that process becomes next to impossible.
My 2 cents:
I think we should leave the onus of fixing the userspace to work with
the sane kernel API with the entity trying to get their drivers into the
kernel. I think it's a better approach (as in, more likelihood of
getting device support) than saying, we will only allow fully open
sourced kernel drivers.
-Saravana
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
