From: Michel Dänzer <michdaen@iiic.ethz.ch>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: "William H. Schultz" <whschult@uncc.edu>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Xinerama Support?
Date: Fri, 31 Mar 2000 09:14:41 +0200 [thread overview]
Message-ID: <38E45061.2504BA87@iiic.ethz.ch> (raw)
In-Reply-To: Pine.LNX.4.10.10003301218050.20130-100000@opal.biophys.uni-duesseldorf.de
Michael Schmitz wrote:
> > If you only have offb for one head, you might be out of luck :(
I'll add something I forgot: Currently both heads must have the same depth for
Xinerama.
> IIRC the bus ID option is only needed if you have multiple video devices
> to choose from.
No, the X server will deactivate all video devices (it can see) which aren't
claimed. And the fbdev driver can currently only claim the device it uses with
the bus ID specified in the config file.
> If there are multiple devices, and the one using offb maps to the first
> frame buffer device, it should be possible to pass the frame buffer device
> name to the X server for the other one (in the fbdev device option,
> apparently).
Right,
Option "fbdev" "/dev/fb1"
must be added in the Device Section for the second head.
> > > Is there any way to get the fbdev driver to be a bit faster? I'm not
> > > too thrilled about having to wait 5 minutes watching the screen go gray
> > > so that I can log out. (I'm not exagerating very much here.)
> >
> > It's a shortcoming in 4.0's brand new lowlevel framebuffer code. I've
> > reported it to the author, don't know if he's (been) working on it...
>
> What's the problem there? It's been annoying as hell, and I'd like to give
> it a try...
The new code is very slim and mostly faster with HW acceleration, but not very
optimized without yet (especially not on big endian :-/) . BTW this is about
xc/programs/Xserver/fb , the author is Keith Packard <keithp@suse.com> .
Michel
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-03-31 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10003301218050.20130-100000@opal.biophys.uni-duesseldorf.de>
2000-03-31 7:14 ` Michel Dänzer [this message]
[not found] <38E326E2.49A7AD62@iiic.ethz.ch>
2000-03-30 11:49 ` Xinerama Support? Kostas Gewrgiou
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=38E45061.2504BA87@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
--cc=whschult@uncc.edu \
/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).