From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Felix Miata <mrmazda@earthlink.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: sad output names
Date: Wed, 25 Jul 2018 14:43:27 -0700 [thread overview]
Message-ID: <20180725214327.GP16907@intel.com> (raw)
In-Reply-To: <7cb37f10-9c23-4f09-3ad1-4cc2e2e89d80@earthlink.net>
On Wed, Jul 25, 2018 at 02:21:24PM -0400, Felix Miata wrote:
> Rodrigo Vivi composed on 2018-07-25 09:20 (UTC-0700):
>
> > On Wed, Jul 25, 2018 at 03:37:52AM -0400, Felix Miata wrote:
>
> >> Asus B250 LGA 1151 (Kaby Lake) Motherboard (4 total physical video outputs):
> >> https://www.asus.com/us/Motherboards/PRIME-B250M-C-CSM/
>
> >> G4600 HD Graphics 630 CPU
>
> >> Server 1.20.0 (openSUSE Tumbleweed)
>
> >> kernel 4.17.4
>
> >> Xorg driver: modesetting
>
> >> Xrandr Actual Cable
> >> Reports Connectors
> >> DP-1 DisplayPort
> >> HDMI-1 ----
> >> HDMI-2 HDMI
> >> HDMI-3 DVI
> >> DP-2 VGA
>
> > I understand your concern, but as you can see there are adaptors involved
> > here and they are decided by manufactures. From the driver perspective the
> > protocol is the most important part, but that gets sometimes really bad for
> > the users, I know.
>
> By "adaptors", do you mean logical adapters in motherboard firmware that maybe
> an update could improve?
adapter... converter... something from the sw side we see as the protocol we support,
but it do whatever conversion needed to another format at the other end.
I don't understand how the update could solve this. But well... maybe that Paulo
mention to EDID and if the information is there. But with so many different
adapters out there from many different vendors I don't think it is worth trying
to guess an universal way.
>
> > Honestly I don't know if there's a way to detect the presence of adapters
> > like this DP to VGA for instance. I don't think so.
>
> > Afaik on HDMI-DP with LSPCON we do some tweak on the names to avoid
> > showing a misleading information, but that's is the further we can go I'm afraid...
>
> Thanks for the reply.
>
> BTW, DP daisy chaining the same motherboard I get the following:
>
> Screen 0: minimum 320 x 200, current 4480 x 1200, maximum 8192 x 8192
> DP-1 disconnected primary (normal left inverted right x axis y axis)
> HDMI-1 disconnected (normal left inverted right x axis y axis)
> HDMI-2 disconnected (normal left inverted right x axis y axis)
> HDMI-3 disconnected (normal left inverted right x axis y axis)
> DP-2 disconnected (normal left inverted right x axis y axis)
> DP-1-8 connected 2560x1080+0+0 (normal left inverted right x axis y axis) 673mm
> x 284mm
> 2560x1080 60.00*+
> 1920x1080 60.00 60.00 50.00 59.94 24.00 23.98
> 1680x1050 59.95
> 1280x1024 75.02 60.02
> 1280x800 59.81
> 1152x864 75.00
> 1280x720 60.00 50.00 59.94 ...
> DP-1-1 connected 1920x1200+2560+0 (normal left inverted right x axis y axis)
> 519mm x 324mm
> 1920x1200 59.95*+
> 1920x1080 60.00 59.94
> 1680x1050 59.95
> 1400x1050 59.98
> 1280x1024 60.02
> 1440x900 59.89
> 1280x960 60.00
> 1280x800 59.81
> 1280x720 60.00 59.94 ...
>
> That logic looks backwards to me. DP-1-8 is the screen in the middle of the
> cable chain. :-p
Yeap... seems a bit backwards to me to... But does it really matter?
>
> >> Is there anything with kernel, xrandr, driver, server (or other?) that might be
> >> changed to better associate the connector names to the actual connector types?
> >> Is this a motherboard firmware shortcoming?--
> "Wisdom is supreme; therefore get wisdom. Whatever else you
> get, get wisdom." Proverbs 4:7 (New Living Translation)
>
> Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
>
> Felix Miata *** http://fm.no-ip.com/
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-25 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 7:37 sad output names Felix Miata
2018-07-25 7:43 ` Felix Miata
2018-07-25 16:20 ` Rodrigo Vivi
2018-07-25 18:21 ` Felix Miata
2018-07-25 21:43 ` Rodrigo Vivi [this message]
2018-07-25 22:02 ` Dhinakaran Pandiyan
2018-07-25 20:07 ` Paulo Zanoni
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=20180725214327.GP16907@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mrmazda@earthlink.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;
as well as URLs for NNTP newsgroup(s).