Posted Jul 5, 2010 17:50 UTC (Mon) by avik
In reply to: s/driver/documentation/
Parent article: A line in the sand for graphics drivers
If we have full hardware documentation and we're expected to write our own userspace, then we also want to write our own kernel code.
Why? If the driver is good, accept it.
There's no incentive whatsoever for us to merge the upstream provided kernel code.
You get not to write that much code.
If we do then we provide an interface that we're expected to support forever (see the argument over nouveau breaking ABI), and the only consumer of that interface is a closed userspace driver.
Of course we should encourage an open source userspace driver, and with full documentation, there is really no reason not to open source the driver. But as a rule, adding a syscall should not require adding a consumer for that syscall.
to post comments)