[android] Secondary outputs on phones are hard coded as "DisplayPort" but might be HDMI
Bug #1491223 reported by
Daniel van Vugt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Won't Fix
|
Low
|
Unassigned | ||
| mir-android-platform |
New
|
Undecided
|
Unassigned | ||
Bug Description
Secondary outputs on phones are reported as "DisplayPort":
[1440740318.830277] mirserver: Selected driver: android (version 0.16.0)
[1440740319.152206] mirserver: Initial display configuration:
[1440740319.152450] mirserver: 0.0: LVDS 4.7" 61x102mm
[1440740319.152633] mirserver: Current mode 768x1280 60.00Hz
[1440740319.152816] mirserver: Preferred mode 768x1280 60.00Hz
[1440740319.152908] mirserver: Logical position +0+0
[1440740319.153060] mirserver: 0.1: unused DisplayPort
However in reality they're more likely HDMI. This seems to be a simple matter of the value being hardcoded:
if (name == mga::DisplayNam
type = mg::DisplayConf
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #1 |
| Changed in mir: | |
| status: | New → Opinion |
| summary: |
- [android] Secondary outputs on phones are reported as "DisplayPort" but - more likely are HDMI + [android] Secondary outputs on phones are hard coded as "DisplayPort" + but migh be HDMI |
| summary: |
[android] Secondary outputs on phones are hard coded as "DisplayPort" - but migh be HDMI + but might be HDMI |
| Changed in mir: | |
| importance: | Undecided → Low |
| status: | Opinion → Triaged |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #2 |
| Changed in mir: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
Hmm, apparently not. The device in question actually uses Slimport so is more closely related to DisplayPort than HDMI.