From: Jani Nikula <jani.nikula@linux.intel.com>
To: Paul Gardiner <lists@glidos.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] Does the intel driver support faking a connected monitor?
Date: Mon, 21 Dec 2020 16:04:45 +0200 [thread overview]
Message-ID: <87eejjp85e.fsf@intel.com> (raw)
In-Reply-To: <516f2e64-9f6b-f729-cbcd-6458997da377@glidos.net>
On Sun, 20 Dec 2020, Paul Gardiner <lists@glidos.net> wrote:
> The debug output was sufficient to track down the problem. It turned out
> that the connection was called HDMI-A-1. When I used that name your
> previous suggestion worked. To get exactly the behaviour I wanted I
> needed to also load EDID. This is the extra boot command string I'm using:
>
> drm.edid_firmware=HDMI-A-1:edid/marantz_edid.bin video=HDMI-A-1:D
>
>
> For that to work I also had to ensure the referenced edid file was in my
> initramfs.
>
> Thanks again for the help.
I'm glad you figured it out, and thanks for letting us know!
> By the way, an EDID emulator is a small USB-stick-sized device that sits
> in between computer and monitor and acts like a monitor when the actual
> monitor is off.
Ah, thanks for the info.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-12-21 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 12:32 [Intel-gfx] Does the intel driver support faking a connected monitor? Paul Gardiner
2020-11-17 14:52 ` Jani Nikula
2020-11-21 10:52 ` Paul Gardiner
2020-11-23 16:19 ` Jani Nikula
2020-11-24 15:03 ` Paul Gardiner
2020-12-04 11:22 ` Paul Gardiner
2020-12-09 10:19 ` Jani Nikula
2020-12-20 10:31 ` Paul Gardiner
2020-12-21 14:04 ` 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=87eejjp85e.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lists@glidos.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