From: Bernie Thompson <bernie@plugable.com>
To: aivils@latnet.lv, James Simmons <jsimmons@infradead.org>,
DRI development list <dri-devel@lists.sourceforge.net>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>Linux
Subject: Re: My goal
Date: Thu, 11 Mar 2010 14:57:10 +0000 [thread overview]
Message-ID: <480988181003110657m5d33fd1dwc674e0b370551498@mail.gmail.com> (raw)
In-Reply-To: <1268289985.4b9891c1d28e3@online.sigmanet.lv>
2010/3/10 <aivils@latnet.lv>:
> Over the world are around 10 versions of multiseat:
There's also the USB multiseat case, which avoids shared resources
(VGA arbiter) and so can cleanly launch independent X instances for
each USB graphics device even now. Better yet, the USB topology can be
used (via udev scripts) to know exactly which keyboard, mouse,
keyboard, etc. go together so adding seats is completely plug and
play.
BUT it's a bit hackish on Linux today, because of the some assumptions
that need cleaned up (e.g. that all graphics are on PCIe). Some of
that cleanup is happening (e.g. hal->libudev), but it could use a lot
more attention and experienced help on the USB case. Also on
whether/how to move USB graphics driver from fbdev->dri with matching
xorg driver, on better newgdm/consolekit integration, and then on
getting this into distros.
http://plugable.com/2009/11/16/setting-up-usb-multiseat-with-displaylink-on-linux-gdm-up-to-2-20/
to see stuff to get it running in the hal/gdmdynamic world.
A lot of discussion and work is on the libdlo list, but needs more
contact with experts on those lists with deeper expertise (dri, fbdev,
console, etc.)
Best wishes,
Bernie
http://plugable.com/
next prev parent reply other threads:[~2010-03-11 14:57 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 [this message]
2010-03-18 0:05 ` Dave Airlie
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=480988181003110657m5d33fd1dwc674e0b370551498@mail.gmail.com \
--to=bernie@plugable.com \
--cc=aivils@latnet.lv \
--cc=dri-devel@lists.sourceforge.net \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev@vger.kernel.org \
/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).