From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] displayport thinkpad x230 external monitor black screen
Date: Sun, 09 Apr 2023 23:26:46 +0200 [thread overview]
Message-ID: <A300A013F5E6F05C19D90F0AF8F1E03E@wopr.sciops.net> (raw)
> From: Romano <unobe@cpan.org>
> Date: Sun, 09 Apr 2023 06:31:09 +0000
> Subject: [PATCH] [PATCH] DP 1.2 on igfx; EDID wrapping; VGA display connections
>
>
> This patch more fully implements the training patterns for DP 1.2 per the spec,
> which then allows more monitors to successfully train and therefore connect. In
> my case it was an LG 34UM68-P.
>
> Secondly, this fixes EDID shifting to work with a wider range of values, notably
> ones which wrap.
>
> Lastly, a small correction in vesa.c as to which bits are used to determine
> available connections.
Wow, great work! I only skimmed through your patch, and I do have
some comments, but this is awesome. I don't have access to any
displayport monitors here to try that stuff myself, but I'll look over
your patch as soon as I can, though perhaps others already have/will.
I'll try to scavenge some equipment at work.
Prost,
qwx
next reply other threads:[~2023-04-09 21:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-09 21:26 qwx [this message]
2023-04-09 22:42 ` sirjofri
2023-04-11 21:33 ` Steve Simon
2023-04-12 22:13 ` unobe
2023-04-11 21:32 ` Roberto E. Vargas Caballero
2023-04-17 7:53 ` qwx
2023-04-19 20:50 ` unobe
2023-04-20 23:40 ` qwx
2023-04-24 18:52 ` qwx
2023-04-26 3:32 ` unobe
2023-04-30 3:12 ` qwx
-- strict thread matches above, loose matches on Subject: below --
2023-03-30 17:37 Romano
2023-03-30 17:47 ` Stanley Lieber
2023-04-03 22:27 ` qwx
2023-04-04 22:39 ` igor
2023-04-04 22:43 ` sl
2023-04-05 7:01 ` qwx
2023-04-09 6:59 ` unobe
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=A300A013F5E6F05C19D90F0AF8F1E03E@wopr.sciops.net \
--to=qwx@sciops.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).