> If we make a library split that sits inside the kernel, their DRM can > stop working if someone busts the interface, hence the idea of having the > core reg/dereg in the kernel, and locking it down, then they can ship a > complete DRM source tree, and do as they wish as long as they interface > properly with the core...
or they just ship their own matching core .c file as well.... Lets face it, for the core there are 2 things that are entirely at conflicts: small interface and core being useful. I rather go for the useful side myself.
signature.asc
Description: This is a digitally signed message part