linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2] video: implement a simple framebuffer driver
Date: Mon, 29 Apr 2013 21:20:43 +0000	[thread overview]
Message-ID: <1461633.kfcPFxva7x@avalon> (raw)
In-Reply-To: <2863648.BDvrAG5uPk@flatron>

Hi Tomasz,

On Monday 29 April 2013 23:15:13 Tomasz Figa wrote:
> On Thursday 11 of April 2013 11:56:31 Laurent Pinchart wrote:
> > On Monday 08 April 2013 17:16:37 Andrew Morton wrote:
> > > On Wed,  3 Apr 2013 20:39:43 -0600 Stephen Warren wrote:
> > > > A simple frame-buffer describes a raw memory region that may be
> > > > rendered to, with the assumption that the display hardware has
> > > > already been set up to scan out from that buffer.
> > > > 
> > > > This is useful in cases where a bootloader exists and has set up the
> > > > display hardware, but a Linux driver doesn't yet exist for the
> > > > display hardware.
> > > > 
> > > > ...
> > > > 
> > > > +config FB_SIMPLE
> > > > +	bool "Simple framebuffer support"
> > > > +	depends on (FB = y) && OF
> > > 
> > > It's sad that this simple little thing requires Open Firmware.  Could
> > > it be generalised in some way so that the small amount of setup info
> > > could be provided by other means (eg, module_param) or does the
> > > dependency go deeper than that?
> > 
> > I second that request. I like the idea of a simple framebuffer driver if
> > it helps deprecating fbdev in the long term, but I don't want it to
> > offer an excuse not to implement a DRM/KMS driver. In particular adding
> > DT bindings would force us to keep supporting the ABI for a (too) long
> > time.
> 
> Well, there is also at least one legitimate use case for this driver.
> 
> I believe there exist embedded devices on which there is no need to
> dynamically control the framebuffer. It needs one time initialization,
> usually in bootloader, and then it is used as is, using constant
> parameters as long as the system is running.
> 
> I doubt there is a need for any KMS (or any other control) driver for such
> devices - dumb framebuffer driver would be everything needed in such case.

As we want to deprecate the fbdev API we would need to move to KMS at some 
point anyway, even if the device can't be controlled. I don't think writting 
such a KMS driver would be that difficult.

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-04-29 21:20 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  2:39 [PATCH V2] video: implement a simple framebuffer driver Stephen Warren
2013-04-09  0:16 ` Andrew Morton
2013-04-09  3:16   ` Stephen Warren
2013-04-09  8:08   ` Geert Uytterhoeven
2013-04-11  9:56   ` Laurent Pinchart
2013-04-11 16:06     ` Stephen Warren
2013-04-11 20:06       ` Laurent Pinchart
2013-04-11 20:38         ` Stephen Warren
2013-04-29 20:56           ` Laurent Pinchart
2013-04-29 21:15     ` Tomasz Figa
2013-04-29 21:20       ` Laurent Pinchart [this message]
2013-04-29 21:31         ` Tomasz Figa
2013-04-29 21:40           ` Laurent Pinchart
2013-04-29 22:04             ` Arnd Bergmann
2013-04-29 22:23               ` Laurent Pinchart
2013-04-29 22:40                 ` Olof Johansson
2013-04-30  9:50                   ` Laurent Pinchart
2013-05-02 18:25               ` Stephen Warren
2013-05-02 18:35                 ` Geert Uytterhoeven
2013-05-03 10:06                 ` Laurent Pinchart
2013-05-07 21:33                   ` Andrew Morton
2013-05-08  2:36                     ` Stephen Warren
2013-05-08 19:28                       ` Olof Johansson
2013-05-08 20:58                       ` Rob Landley
2013-04-30  7:28       ` Tomi Valkeinen
2013-04-11 10:42 ` Geert Uytterhoeven
2013-04-11 16:10   ` Stephen Warren
2013-04-30  7:27 ` Tomi Valkeinen
2013-04-30 10:28   ` Arnd Bergmann
2013-04-30 11:42     ` Laurent Pinchart
2013-04-30 11:48       ` Tomi Valkeinen
2013-04-30 11:49         ` Laurent Pinchart
2013-04-30 11:46     ` Tomi Valkeinen
2013-05-03  5:40       ` Dave Airlie
2013-04-30  7:39 ` Tomi Valkeinen
2013-04-30 10:34   ` Arnd Bergmann
2013-04-30 14:38   ` Re[2]: [PATCH V2] video: implement a simple f =?UTF-8?B?cmFtZWJ1ZmZlciBkc Alexander Shiyan
2013-04-30 15:07     ` Re[2]: [PATCH V2] video: implement a simple framebuffer driver Arnd Bergmann
2013-05-18 10:29 ` Alexandre Courbot
2013-05-20 15:25   ` Stephen Warren

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=1461633.kfcPFxva7x@avalon \
    --to=laurent.pinchart@ideasonboard.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).