From: Thomas Hellstrom <thellstrom@vmware.com>
To: Rian Quinn <rianquinn@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Testing LibDRM with Multi-Monitors on VMWare Fusion / Workstation
Date: Wed, 15 Oct 2014 22:34:41 +0200 [thread overview]
Message-ID: <543EDA61.906@vmware.com> (raw)
In-Reply-To: <B4500931-13FC-42ED-AC12-A5C434B8965E@gmail.com>
Hi!
On 09/25/2014 06:52 PM, Rian Quinn wrote:
> I have been doing a lot of work with LibDRM, including Multi-Monitor work on Intel and VMWare. Do you guy’s know if there is an easy way to tell VMWare to add more virtual display’s for testing? LibDRM reports something like 8 different connectors, and several CRTCs, so I know it at least supports Multi-Monitor, I’m just not sure how to tell the hypervisor to enable more than one for testing.
>
> I’m sure this is a question for a better list, but I figured I cannot be the only one interested in working with LibDRM on VMWare.
>
> Thanks in advance,
> - Rian
Sorry for the late reply. There's an ioctl you may use to set the GUI
layout: DRM_IOCTL_VMW_UPDATE_LAYOUT
(which would in real hardware correspond to plugging in a set of
monitors and arranging them). That ioctl is currently reserved for the
master and the Xorg driver is using it if you need a code example. I
haven't tested for a while, but it should be possible to have up to
eight different virtual "displays" in a single VMware GUI window.
One caveat is that you might need to manually set the number of displays
and their max sizes from the VMware GUI to make sure you get enough VRAM
to back the displays.
/Thomas
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-10-15 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 16:52 Testing LibDRM with Multi-Monitors on VMWare Fusion / Workstation Rian Quinn
2014-10-15 20:34 ` Thomas Hellstrom [this message]
2014-10-17 23:52 ` Rian Quinn
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=543EDA61.906@vmware.com \
--to=thellstrom@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=rianquinn@gmail.com \
/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.