All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rasto Sramek <rsramek@inf.ethz.ch>
To: Andrew Lutomirski <luto@mit.edu>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Zaphod mode support?
Date: Wed, 6 Oct 2010 16:50:34 +0200	[thread overview]
Message-ID: <20101006145034.GA28631@element.ksp.sk> (raw)
In-Reply-To: <AANLkTikUEUbSEB-6EeRPVZ4QGwfxeE=8OAJ39nPDCOFf@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1426 bytes --]

> AFAICT Zaphod mode is one device but multiple X servers (presumably
> used independently by different people).  I think very few drivers
> support it these days.
Well, whatever it is called, I am referring to the configuration when I
have a single X server but multiple screens, like screen0 and screen1. 

> The modern approach is one "screen" divided among multiple monitors
> using RandR.  I'm not sure what fglrx and nvidia do.
Anything can of course use RandR, however at least nvidia drivers
support multiple screens. Afaik intel used to support it as well.
With nvidia one simply declares 2 monitors, and 2 screens. 
> 
> In any case, switching workspaces the way you want would be a feature
> of the window manager or compositing manager, not the driver.  If you
> use compiz + GNOME, try installing ccsm.  Then look in Desktop Wall /
> Viewport Switching and change the "Multimonitor behavior" setting.
> (If you're on Fedora and you enable compiz through desktop-effects,
> you'll need to modify /usr/bin/compiz-gtk like this:

I use fluxbox which needs screen0 and screen1. I know that awesome is
aware of xrandr and can simulate separate screen behavior but I do not
know of other WMs that can do so. The reason I prefer having 
multiple screens is that it is in my view a simple and correct behavior 
which has worked for years. 

Thanks for the quick response!
Best regards, 
Rasto

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2010-10-06 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 14:03 Zaphod mode support? Rasto Sramek
2010-10-06 14:29 ` Andrew Lutomirski
2010-10-06 14:50   ` Rasto Sramek [this message]
2010-10-06 14:54     ` Andrew Lutomirski
  -- strict thread matches above, loose matches on Subject: below --
2010-10-07 12:55 Rasto Sramek

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=20101006145034.GA28631@element.ksp.sk \
    --to=rsramek@inf.ethz.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=luto@mit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.