linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i.MX23/28 framebuffer driver
Date: Thu, 10 Feb 2011 10:22:32 +0100	[thread overview]
Message-ID: <20110210092232.GA4894@vixen> (raw)
In-Reply-To: <20110209153716.GN9041@pengutronix.de>

Hi Sascha,

On Wed, Feb 09, 2011 at 04:37:16PM +0100, ext Sascha Hauer wrote:
> Hi Arnd,
> 
> On Wed, Feb 09, 2011 at 03:47:11PM +0100, Arnd Bergmann wrote:
> > 
> > Did you consider making the driver a KMS driver instead of
> > a frame buffer? I think the recommendation these days is
> > to start out with KMS for new drivers, which will be somewhat
> > simpler and give you a frame buffer device as well. I don't
> > think that there is a need to change over any drivers from
> > fb to kms though, since you've already done the work.
> 
> I tried doing so for the i.MX51 which supports multiple displays on dvi
> and vga outputs and thus could make good use of KMS and friends. Anyway,
> I got stuck quite fast. The KMS stuff is tightly coupled with DRM/DRI
> and needs many many callbacks to implement. Additionally the userspace
> tools expect a nvidia/amd/intel driver and do not have a generic
> fallback. I think this stuff is good for implementing a full blown
> graphics driver, but is lacking support for simple framebuffer grapics.
> I'd love to go this way but it still requires a lot of work.

I will get the i.MX28 EVK within a couple of weeks. I'm curious of KMS,
which I don't know at all, and I would like to work on it. We could
join the efforts. What do you think?

Best regards,
Domenico

      parent reply	other threads:[~2011-02-10  9:22 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
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 [this message]

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=20110210092232.GA4894@vixen \
    --to=cavokz@gmail.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).