From: James Simmons <jsimmons@infradead.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: conflicts between fbcon and user-mode fbdev clients
Date: Thu, 10 Dec 2009 19:02:37 +0000 [thread overview]
Message-ID: <alpine.LFD.2.00.0912101852180.7053@casper.infradead.org> (raw)
In-Reply-To: <480988180912091352v77fa9a12s5077b3211c13586b@mail.gmail.com>
> Hi fbdevs,
>
> This is probably a FAQ, but I haven't found the answer.
>
> What (if anything) should a driver be doing to prevent fbcon and other
> clients (e.g. X, etc.) from simultaneously opening and rendering to
> the framebuffer?
>
> Running a USB graphics device using the udlfb framebuffer driver
> (in the staging tree of 2.6.32), a common problem is fbcon
> automatically opens the first available framebuffer device (/dev/fb0).
> Then when the user loads an X server, both the X server and fbcon
> continue to merrily render to the device, overwriting each other.
>
> So, typically, the udlfb driver will see this sequence at boot (with
> the xf-video-displaylink X server):
> fb_open(user = 0) fbcon opening the framebuffer
> fb_open(user = 1) X opening the framebuffer
> fb_open(user = 1) Another instance of X opening framebuffer
> * X and fbcon both render to the framebuffer, causing a mess *
> And then any calls to release() later.
That shouldn't happen. In the xorg.conf do you have in the
Option UseFBDev "True"
next prev parent reply other threads:[~2009-12-10 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 21:52 conflicts between fbcon and user-mode fbdev clients Bernie Thompson
2009-12-10 19:02 ` James Simmons [this message]
2009-12-10 19:43 ` Bernie Thompson
2009-12-10 19:55 ` 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=alpine.LFD.2.00.0912101852180.7053@casper.infradead.org \
--to=jsimmons@infradead.org \
--cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).