From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] aux/vga -p intermittent edid reporting
Date: Sat, 24 Apr 2021 18:07:11 +0200 [thread overview]
Message-ID: <050993C291A0D8B0008D9A4DAE2DA4DA@felloff.net> (raw)
In-Reply-To: <30C99A62E19B58AC69D833F029414A13@smtp.pobox.com>
> But back to the main issue: is edid supposed to be consistently
> reported, or is this expected?
no, this is not expected. this hints at some issue with the i2c
controller code that is supposed to read the edid over the aux
channel.
the fix would be to fix that code so it read edid consistently.
on some intel cards, the i2c stuff doesnt work at all. in this
case, you can copy the monitor information into vgadb and tell
it to use that info directly, skipping the i2c part.
--
cinap
next prev parent reply other threads:[~2021-04-25 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 22:16 unobe
2021-04-24 16:07 ` cinap_lenrek [this message]
2021-04-27 5:39 ` unobe
2021-04-27 9:19 ` cinap_lenrek
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=050993C291A0D8B0008D9A4DAE2DA4DA@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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).