From: Sean D'Epagnier <sean@depagnier.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Multihead support
Date: Sun, 6 Aug 2006 03:35:04 -0600 [thread overview]
Message-ID: <20060806093504.GA30519@inferno.domain.actdsltmp> (raw)
In-Reply-To: <170385E48B041543AC99CCD09E325AD1952C32@mail.elevenonline.com.au>
I think multihead support is slightly broken with fbdev.
I have multihead working with nvidiafb and matroxfb. I had to patch the
kernel to get console text to update on the non-active vt.
In userspace programs, I know how to register signal handlers to notify
a program when it gains or loses the active vt, but I don't think there is
a way to correctly detect when a framebuffer device becomes visible or
hidden. The FBIOGET_CON2FBMAP ioctl provides a means to find which
fbdev devices is mapped to a given console, but as far as I know to do
the reverse lookup (find the vt attached to a given fbdev) can't be done.
There are really 3 states a vt can be in:
1. active/visible
2. inactive/visible (only applies to multihead)
3. inactive/invisible
If it were possible to register a signal handler for visible changes the
same way as active changes, this would fix the problem.
Xorg for example won't run on /dev/fb0 and allow me to run something else
on /dev/fb1 I have in my own programs written hacks to poll con2fb, at
a timed interval. This is a terrible solution, and it has a high probability
of corrupting the screen output (until refresh)
I think in the future this will be come a bigger concern as x11 is slowly
being separated from the hardware, and it will become useful to run
multiple sessions of x11. I would like to discuss all possible solutions,
and hopefully implement a simple working solution.
Thanks,
Sean D'Epagnier
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-08-06 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 1:00 Driver for Sharp LH155BA Richard Wolf
2006-08-06 9:35 ` Sean D'Epagnier [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=20060806093504.GA30519@inferno.domain.actdsltmp \
--to=sean@depagnier.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).