From: "Cheshire Cat Fish" <cat_fish@hotmail.com>
To: cat_fish@hotmail.com, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Questions on more than one framebuffer device
Date: Tue, 13 May 2003 17:23:52 -0700 [thread overview]
Message-ID: <Law15-F104wY6YHkidc00013e45@hotmail.com> (raw)
>The problem comes when I run X with two cards in the system. I can run X
>on either card ok. When I try to run X on both devices at the same time,
>some things don't get drawn, and the screen doesn't always repaint right.
>What does get drawn, is drawn to the correct screen, just some drawing
>operations seem to be dropped.
One further piece of information. The drawing errors always happen on the
second screen.
It doesn't matter which screen (0 or 1) I map to which framebuffer (/dev/fb0
or /dev/fb1), the drawing on screen 0 is correct, the drawing on screen 1 is
corrupted.
I am wondering if it is even a problem with my driver now. Xfree86 should
be able to run with multiple fbdev drivers, right?
Thanks,
Noel.
--
A precariously balanced mixture of myopic optimism and rampant paranoia.
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
next reply other threads:[~2003-05-14 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 0:23 Cheshire Cat Fish [this message]
2003-05-14 22:44 ` Questions on more than one framebuffer device James Simmons
2003-05-14 23:07 ` Michel Dänzer
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 22:06 Cheshire Cat Fish
2003-05-15 6:46 Cheshire Cat Fish
2003-05-13 23:23 Cheshire Cat Fish
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=Law15-F104wY6YHkidc00013e45@hotmail.com \
--to=cat_fish@hotmail.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).