linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernie Thompson <bernie@plugable.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: conflicts between fbcon and user-mode fbdev clients
Date: Thu, 10 Dec 2009 19:43:31 +0000	[thread overview]
Message-ID: <480988180912101143p1ab40eebr6bdaa10fe3b194c7@mail.gmail.com> (raw)
In-Reply-To: <480988180912091352v77fa9a12s5077b3211c13586b@mail.gmail.com>

On Thu, Dec 10, 2009 at 11:02 AM, James Simmons <jsimmons@infradead.org> wrote:
> That shouldn't happen. In the xorg.conf do you have in the
>
> Option UseFBDev "True"

That option appears to have no effect (have tried both ways).  Do you
know who parses it?  Couldn't find it in core xserver.

The DisplayLink support is still very rough, but it's currently using
its own X server driver
(http://libdlo.freedesktop.org/wiki/xf86-driver-displaylink), which
has some IOCTLs to its framebuffer driver, including a mode setting
IOCTL.

If the arbitration between fbdev clients is intended to happen at the
point of mode setting, rather than at open(), that would explain the
problem.  Are there any old posts or docs which describe how
arbitration is handled for the fbdev driver and multiple clients?

Jaya Kumar has written an alternative DisplayLink fbdev driver that
uses defio and works with the standard fbdev X servers.  That support
will be merged in soon, so then it'll be easy to test what happens
where there's no special mode set paths between X and the framebuffer
driver.

Thanks,
Bernie

  parent reply	other threads:[~2009-12-10 19:43 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
2009-12-10 19:43 ` Bernie Thompson [this message]
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=480988180912101143p1ab40eebr6bdaa10fe3b194c7@mail.gmail.com \
    --to=bernie@plugable.com \
    --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).