Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
	linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bernie Thompson <bernie@plugable.com>
Subject: Re: [Patch, RFC] Make struct fb_info ref-counted with kref
Date: Mon, 20 Sep 2010 20:27:57 +0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1009202223450.19429@axis700.grange> (raw)
In-Reply-To: <20100920221424.04150239@neptune.home>

On Mon, 20 Sep 2010, Bruno Prémont wrote:

> On Mon, 20 September 2010 Guennadi Liakhovetski wrote:
> 
> > Of course, the optimal solution would be to design and implement a
> > mechanism to notify framebuffer users about a changed fb configuration,
> > but we're not that far yet...
> 
> This would include ABI change for userspace, hard to get it trough...
> (except maybe if userspace has to opt-in for the notification and kernel
> can thus differentiate the "old" and "new" users)

Yes, something like that...

> But how would you handle userspace apps that can't consume notifications right
> away? Do you timeout or risk long stalls?

In the same way as they're currently [1] handled: as long as there are 
active fb-users, I reconfigure the physical interface but preserve the 
user configuration, i.e., I either display the smaller user framebuffer on 
a part of the larger display or a part of the larger user framebuffer on 
the whole smaller display.

[1] http://thread.gmane.org/gmane.linux.ports.sh.devel/8751

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

  reply	other threads:[~2010-09-20 20:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-19 15:28 [Patch, RFC] Make struct fb_info ref-counted with kref Bruno Prémont
2010-09-19 16:47 ` Florian Tobias Schandinat
2010-09-19 17:02   ` Bruno Prémont
2010-09-20 19:05     ` Florian Tobias Schandinat
2010-09-20 19:32       ` Bruno Prémont
2010-09-20 20:08         ` Florian Tobias Schandinat
2010-09-20 20:36           ` Bruno Prémont
2010-09-20 22:28             ` Florian Tobias Schandinat
2010-09-21  5:56               ` Bruno Prémont
2010-09-21  6:39                 ` Florian Tobias Schandinat
2010-09-21  7:02                   ` Bruno Prémont
2010-09-22 17:31                     ` James Simmons
2010-09-22 18:39                       ` Bruno Prémont
2010-09-22 19:14                         ` James Simmons
2010-09-22 19:35                           ` Bruno Prémont
2010-09-20 19:34       ` Guennadi Liakhovetski
2010-09-20 20:14         ` Bruno Prémont
2010-09-20 20:27           ` Guennadi Liakhovetski [this message]
2010-09-21 10:44       ` Michel Dänzer
2010-09-20  8:27   ` Geert Uytterhoeven

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=Pine.LNX.4.64.1009202223450.19429@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=FlorianSchandinat@gmx.de \
    --cc=bernie@plugable.com \
    --cc=bonbons@linux-vserver.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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