From: Paulo Zanoni <paulo.r.zanoni@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Felix Miata <mrmazda@earthlink.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: sad output names
Date: Wed, 25 Jul 2018 13:07:39 -0700 [thread overview]
Message-ID: <1532549259.2522.20.camel@intel.com> (raw)
In-Reply-To: <20180725162018.GG16907@intel.com>
Em Qua, 2018-07-25 às 09:20 -0700, Rodrigo Vivi escreveu:
> 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.
>
> 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...
>
> >
> > 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?
Keep in mind that due to adapters, the actual cable connected to a
certain port may change over time, and our Kernel connector names are
fixed.
The most user friendly thing apps can do is to read monitor information
(from EDID) and display that to the user. For example, I see my desktop
environment says I have "Acer Technologies 27"" and "Laptop" (and it
even displays which one is which). I don't even need to care if the
monitor is connected through HDMI or DP: all I have to know is what I
can see (the monitor itself).
> > --
> > "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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-07-25 20:07 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
2018-07-25 22:02 ` Dhinakaran Pandiyan
2018-07-25 20:07 ` Paulo Zanoni [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=1532549259.2522.20.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mrmazda@earthlink.net \
--cc=rodrigo.vivi@intel.com \
/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).