dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Arun Mani J <J.ArunMani@proton.me>, dri-devel@lists.freedesktop.org
Subject: Re: Development of custom virtual monitor
Date: Mon, 25 Sep 2023 13:17:03 +0300	[thread overview]
Message-ID: <87cyy6o8v4.fsf@intel.com> (raw)
In-Reply-To: <LneaADrt-thjT-QDSquor44L0ZPFATd58AVE4uUbkLCefwa4mFmjOvdPw6PVZAKMuG0meL_DMzXMPZuz7i6XXqDks27o-A4u-JSCir6IwGw=@proton.me>

On Mon, 25 Sep 2023, Arun Mani J <J.ArunMani@proton.me> wrote:
> Hey all
> I would like to develop a virtual monitor, regarding which I need help. The situation is, I need to design a virtual monitor and make it a top-level window. I should be able to move windows to this monitor, render them and do other things which can be done in a physical monitor.
>
> Of course, X11 and Mutter provide APIs to create virtual monitors. but I want it to be as DE independent as possible. So I'm looking for a low-level solution which might interface with the Kernel to act as a universal virtual monitor.
>
> The closest I can get to is DRI and KMS. But I'm stuck on how to take it forward as in how to fake this entire scenario.
>
> My assumption of the situation is like, I create a file in /dev that signals "plugging-in" of a monitor, which makes Kernel load my custom driver. Window managers, DRIs write to this file, as in write the data to be shown on the monitor and my driver would take care of rendering those data on a top-level window. But I think, this won't be that easy...
>
> This is similar to a virtual machine, but I just want to emulate a monitor than a processor or so.
>
> Any pointers and documentation regarding this is highly appreciated. Yes, I'm new to such kinda stuff but I'm ready to invest time and learn :)

Maybe look into drm/vkms [1][2].


BR,
Jani.


[1] https://docs.kernel.org/gpu/vkms.html
[2] https://docs.kernel.org/gpu/drm-uapi.html#using-vkms-to-test-drm-api


-- 
Jani Nikula, Intel

      reply	other threads:[~2023-09-25 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25  5:03 Development of custom virtual monitor Arun Mani J
2023-09-25 10:17 ` Jani Nikula [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=87cyy6o8v4.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=J.ArunMani@proton.me \
    --cc=dri-devel@lists.freedesktop.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