linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rob@ti.com (Clark, Rob)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i.MX23/28 framebuffer driver
Date: Thu, 17 Feb 2011 09:25:48 -0600	[thread overview]
Message-ID: <AANLkTim4rsuDLnyLtetMpn_i+x0e8FmyzLvy1Bm0JEAG@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim3iUNHsaCf7387H-X+XW0YDQsQVa1FwDvo0KvH@mail.gmail.com>

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/omap_gpu
>> >> > ), 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 at lists.linaro.org
>> >> http://lists.linaro.org/mailman/listinfo/linaro-dev
>> >
>> >
>>
>> _______________________________________________
>> linaro-dev mailing list
>> linaro-dev at lists.linaro.org
>> http://lists.linaro.org/mailman/listinfo/linaro-dev
>

  reply	other threads:[~2011-02-17 15:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 13:20 [PATCH] i.MX23/28 framebuffer driver Sascha Hauer
2011-02-09 13:20 ` [PATCH 1/2] video: Add " Sascha Hauer
2011-02-09 13:35   ` Lothar Waßmann
2011-02-10  3:16   ` Li Frank-B20596
2011-02-10  8:51     ` Juergen Beisert
2011-02-10  9:15       ` Li Frank-B20596
2011-02-10  9:52         ` Juergen Beisert
2011-02-10 10:37           ` Li Frank-B20596
2011-02-10 11:12             ` Juergen Beisert
2011-02-10 12:23               ` Li Frank-B20596
2011-02-10  9:23   ` Li Frank-B20596
2011-02-10  9:46     ` Juergen Beisert
2011-02-10 10:08       ` Li Frank-B20596
2011-02-10 10:47       ` Wolfram Sang
2011-02-10 11:51         ` Sascha Hauer
2011-02-10 12:32           ` Li Frank-B20596
2011-02-09 13:20 ` [PATCH 2/2] ARM i.MX23/28: Add framebuffer device support Sascha Hauer
2011-02-09 14:33   ` Fabio Estevam
2011-02-10  3:23   ` Li Frank-B20596
2011-02-09 14:47 ` [PATCH] i.MX23/28 framebuffer driver Arnd Bergmann
2011-02-09 15:37   ` Sascha Hauer
2011-02-09 16:31     ` Arnd Bergmann
2011-02-10 17:09       ` Robert Schwebel
2011-02-15 14:13       ` Clark, Rob
2011-02-16 12:22         ` Arnd Bergmann
2011-02-16 14:42           ` Jesse Barker
2011-02-17  1:08             ` Clark, Rob
2011-02-17  1:24               ` Jammy Zhou
2011-02-17 15:25                 ` Clark, Rob [this message]
2011-02-18  2:25                   ` Jammy Zhou
2011-02-18  4:34                     ` Clark, Rob
2011-02-17 16:14               ` James Simmons
2011-02-18  2:19                 ` Jammy Zhou
2011-02-18  4:32                   ` Clark, Rob
2011-02-21  3:12                 ` Dave Airlie
2011-02-10  9:22     ` Domenico Andreoli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTim4rsuDLnyLtetMpn_i+x0e8FmyzLvy1Bm0JEAG@mail.gmail.com \
    --to=rob@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).