I also noticed that default XRandR1.2+ implementation is missing in X side. If we can implement one, it would be beneficial for all ARM platforms. By the way, does X driver of TI support XRandR1.2+?<br><br>Regards,<br>Jammy<br>
<br><div class="gmail_quote">On Thu, Feb 17, 2011 at 11:25 PM, Clark, Rob <span dir="ltr"><<a href="mailto:rob@ti.com">rob@ti.com</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;">
Hmm, I was thinking more on the xf86 side of things.. ie. to provide<br>
default implementations of xf86CrtcFuncsRec and xf86OutputFuncsRec<br>
functions..<br>
<br>
BR,<br>
<font color="#888888">-R<br>
</font><div><div></div><div class="h5"><br>
On Wed, Feb 16, 2011 at 7:24 PM, Jammy Zhou <<a href="mailto:jammy.zhou@linaro.org">jammy.zhou@linaro.org</a>> wrote:<br>
><br>
> There is already one KMS abstraction layer (libkms.so) in libdrm, maybe it can serve as what we needed.<br>
><br>
> Regards,<br>
> Jammy<br>
><br>
> On Thu, Feb 17, 2011 at 9:08 AM, Clark, Rob <<a href="mailto:rob@ti.com">rob@ti.com</a>> wrote:<br>
>><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>
>> BR,<br>
>> -R<br>
>><br>
>> On Wed, Feb 16, 2011 at 8:42 AM, Jesse Barker <<a href="mailto:jesse.barker@linaro.org">jesse.barker@linaro.org</a>> wrote:<br>
>> > Speaking for the Linaro graphics working group, I think it's great. And, I<br>
>> > think you're right, that if enough of the KMS support in xf86-video-* is<br>
>> > similar enough (I was only aware of intel and nouveau supporting it properly<br>
>> > at current), pulling it out into a common layer would make it easier to<br>
>> > support in new drivers (including fbdev).<br>
>> ><br>
>> > cheers,<br>
>> > Jesse<br>
>> ><br>
>> > On Wed, Feb 16, 2011 at 4:22 AM, Arnd Bergmann <<a href="mailto:arnd@arndb.de">arnd@arndb.de</a>> wrote:<br>
>> >><br>
>> >> On Tuesday 15 February 2011, Clark, Rob wrote:<br>
>> >> > I'd been experimenting a bit on the side w/ the DRM driver framework (<br>
>> >> ><br>
>> >> > <a href="http://gitorious.com/%7Erobclark/pandaboard/robclarks-kernel-omap4/commits/omap_gpu" target="_blank">http://gitorious.com/~robclark/pandaboard/robclarks-kernel-omap4/commits/omap_gpu</a><br>
>> >> > ), but had to add a good chunk of mostly boilerplate code to our xorg<br>
>> >> > driver in order just to test it. Maybe some generic support for KMS<br>
>> >> > in xf86-video-fbdev would have made this easier to develop the kernel<br>
>> >> > part without in parallel having to implement the userspace part. I'm<br>
>> >> > not sure if this is the sort of thing the linaro-wg has in mind?<br>
>> >><br>
>> >> I'm not sure what the the linaro multimedia wg thinks of this, but the<br>
>> >> kernel code you linked looks like it's doing exactly the right thing.<br>
>> >><br>
>> >> Arnd<br>
>> >><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>
>> ><br>
>> ><br>
>><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>
><br>
</div></div></blockquote></div><br>