9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] aux/vga display mirroring
Date: Wed, 15 Jun 2022 08:56:56 +0200	[thread overview]
Message-ID: <71133B4E09D680E313004B3FEDCD0651@wopr.sciops.net> (raw)
In-Reply-To: <EFDAE50DF2AF450435377A0445372607@chrisfroeschl.de>

>  From my understanding, it should be the other way around.  Just a
> understand problem on my side perhaps. Nothing that bothers me since
> I know that it works at least.  Although an explanation could
> be helpful.

So long as switching works and you get the right resolution, it
doesn't matter whether you use vesa or not.  The igfx driver really
only does mode setting.  There are some benefits, depending on your
machine though: you can adjust the brightness if you don't have
hardware buttons for it, you can have screen blanking that doesn't
deactivate the screen until you reboot, and you could use a hardware
cursor;  and of course use resolutions that you don't get with vesa.

> There also seems to be some caching like logic to be involved. I have
> to include the display number '#1' at least at the first call. Afterwards
> it doesn't need to be included.

If you mean that it's wrt.  the sequence of commands you show, igfx
doesn't recognize the ,#n syntax, it's for vesa only, so it will
either auto-detect the screen to use (as is the case here), or use a
vgadb entry that specifies which port (vga, displayport 1-5, etc.) to
use, vga by default.  Also, if you're not using -m vesa, you don't
need realemu(8).

> Anyways, I get to the switch leaving me with a blank screen.  Is there
> a way to do a screen mirroring?  (Laptop screen synced with beamer
> screen)

No, there's no support for using multiple screens in any way, unless
there's some trick specifically for mirroring that I'm not aware of.

Someone please correct me if I'm saying something stupid, it's been a
while since I messed with all this :)


  reply	other threads:[~2022-06-15  6:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 20:01 chris
2022-06-15  6:56 ` qwx [this message]
2022-06-15 20:36   ` chris

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=71133B4E09D680E313004B3FEDCD0651@wopr.sciops.net \
    --to=qwx@sciops.net \
    --cc=9front@9front.org \


* 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).