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+?
Regards, Jammy
On Thu, Feb 17, 2011 at 11:25 PM, Clark, Rob rob@ti.com wrote:
Hmm, I was thinking more on the xf86 side of things.. ie. to provide default implementations of xf86CrtcFuncsRec and xf86OutputFuncsRec functions..
BR, -R
On Wed, Feb 16, 2011 at 7:24 PM, Jammy Zhou jammy.zhou@linaro.org wrote:
There is already one KMS abstraction layer (libkms.so) in libdrm, maybe
it can serve as what we needed.
Regards, Jammy
On Thu, Feb 17, 2011 at 9:08 AM, Clark, Rob rob@ti.com wrote:
I'm still in the learning-as-I-go phase here, so definitely not ready to propose a solution, but it does seem to me like there is room for some sort of kms-helper library here to handle more of the boilerplate xf86-video-* stuff.. I guess I'll have a better picture once I have a chance to add support for the various multi-monitor configurations. But certainly would be interested if anyone already has some ideas.
BR, -R
On Wed, Feb 16, 2011 at 8:42 AM, Jesse Barker jesse.barker@linaro.org
wrote:
Speaking for the Linaro graphics working group, I think it's great.
And, I
think you're right, that if enough of the KMS support in xf86-video-*
is
similar enough (I was only aware of intel and nouveau supporting it
properly
at current), pulling it out into a common layer would make it easier
to
support in new drivers (including fbdev).
cheers, Jesse
On Wed, Feb 16, 2011 at 4:22 AM, Arnd Bergmann arnd@arndb.de wrote:
On Tuesday 15 February 2011, Clark, Rob wrote:
I'd been experimenting a bit on the side w/ the DRM driver
framework (
http://gitorious.com/~robclark/pandaboard/robclarks-kernel-omap4/commits/oma...
), but had to add a good chunk of mostly boilerplate code to our
xorg
driver in order just to test it. Maybe some generic support for
KMS
in xf86-video-fbdev would have made this easier to develop the
kernel
part without in parallel having to implement the userspace part.
I'm
not sure if this is the sort of thing the linaro-wg has in mind?
I'm not sure what the the linaro multimedia wg thinks of this, but
the
kernel code you linked looks like it's doing exactly the right thing.
Arnd
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev