To accommodate the fact of independent display controller and GPU components in ARM SOC, it will be better if we can separate KMS from DRM both in kernel space and user space (i.e, create a new drivers/video/kms directory for kernel side, move KMS related code in libdrm to libkms in user space). Then we can build xrandr1.2+ support based on KMS for ARM platforms, even if DRM is still not supported. Besides, for buffer management part (GEM) in DRM, if possible, we can also make it an independent module leaving DRM just a wrapper, so that the GEM stuff can be used more flexibly.<br>
<br>Regards,<br>Jammy<br><br><div class="gmail_quote">On Fri, Feb 18, 2011 at 12:14 AM, James Simmons <span dir="ltr"><<a href="mailto:jsimmons@infradead.org">jsimmons@infradead.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
> I'm still in the learning-as-I-go phase here, so definitely not ready<br>
> to propose a solution, but it does seem to me like there is room for<br>
> some sort of kms-helper library here to handle more of the boilerplate<br>
> xf86-video-* stuff.. I guess I'll have a better picture once I have a<br>
> chance to add support for the various multi-monitor configurations.<br>
> But certainly would be interested if anyone already has some ideas.<br>
<br>
</div>I have been thinking about this as well. One of the short coming for DRM<br>
on embedded platforms is the lack of a small well defined library that one<br>
could use. Right now libkms only handles buffer allocation. The mode<br>
setting is currently tied to the libdrm library. It would be nice to<br>
seperate the two out more. Move the mode setting code to libkms and then<br>
have libdrm be a wrapper around this. This way libdrm can both support<br>
the legacy drm drivers and the new kms drivers at the same time. It also<br>
makes a clear seperation. Jakob if you are willing to take this work I<br>
will gladly seen you patches.<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
linaro-dev mailing list<br>
<a href="mailto:linaro-dev@lists.linaro.org">linaro-dev@lists.linaro.org</a><br>
<a href="http://lists.linaro.org/mailman/listinfo/linaro-dev" target="_blank">http://lists.linaro.org/mailman/listinfo/linaro-dev</a><br>
</div></div></blockquote></div><br>