linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux console project <linuxconsole-dev@lists.sourceforge.net>,
	Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	DRI development list <dri-devel@lists.sourceforge.net>
Subject: Re: My goal
Date: Thu, 18 Mar 2010 00:05:32 +0000	[thread overview]
Message-ID: <21d7e9971003171705mbd61603n4c8a998108d1b227@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1003110341550.21470@casper.infradead.org>

On Thu, Mar 11, 2010 at 1:51 PM, James Simmons <jsimmons@infradead.org> wrote:
>
> Okay all the discussion about multiple display brings me to why I'm doing
> this. I'm attempting to revive the linux console project. I'm in a
> position to again work on this project. About 4 years ago the eproject
> managed to get multi-seat working. My goal is to get there again. My first
> goal is to get my netbook to act has a multiseat system for two. With a plugged
> in external montior and a USB keyboard run two concurrent X sessions both
> running OpenGL applications at the same time. I set out to do this 10
> years ago and I want to finally accomplish this.

Okay I took an afternoon to flesh out my design and got something working here,
I'll try and setup a videod demo later (if I can find a camera).

But I can now run two *separate* X servers on different outputs of the same GPU.

http://people.freedesktop.org/~airlied/multiseat/

has the kernel + libdrm patch, this is hacked for *my* X1900 (the radeon driver
hardcodes a seat -> crtc/connector/encoder mapping that should be dynamically
setup from userspace via the drm control node.

The libdrm patches adds an env var to pick device node (probably needs to be
secured).

With this I can and some proper xorg.conf to pick the correct input devices

DRM_DEVICE_PATH=/dev/dri/renderD128 /opt/xorg/bin/Xorg -retro
DRM_DEVICE_PATH=/dev/dri/renderD129 /opt/xorg/bin/Xorg :1 -sharevts
-novtswitch -retro

I can run two independent X servers on the same GPU.

Hopefully this gives you some idea of where I was planning on heading with this.

Dave.

      parent reply	other threads:[~2010-03-18  0:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11  3:51 My goal James Simmons
2010-03-11  4:47 ` Dave Airlie
2010-03-11  6:46 ` aivils
2010-03-11 14:57   ` Bernie Thompson
2010-03-18  0:05 ` Dave Airlie [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=21d7e9971003171705mbd61603n4c8a998108d1b227@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linuxconsole-dev@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).