Opened 12 years ago
Last modified 4 years ago
#8626 new enhancement
radeon_hd needs display port support
| Reported by: | kallisti5 | Owned by: | kallisti5 |
|---|---|---|---|
| Priority: | normal | Milestone: | R1.1 |
| Component: | Drivers/Graphics/radeon_hd | Version: | R1/Development |
| Keywords: | nutmeg, travis, displayport | Cc: | |
| Blocked By: | #8612 | Blocking: | #8485, #10335 |
| Platform: | All |
Description (last modified by )
While radeon_hd is aware of display port devices (and can even speak to them somewhat via the aux channel), the display port link training code needs finished. This is essential to supporting newer chipsets in laptop configurations with internal DisplayPort encoders such as travis and nutmeg.
TRAVIS is a DP -> lvds encoder NUTMEG is a DP -> VGA encoder
Attachments (4)
Change History (18)
comment:1 by , 12 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 12 years ago
| Blocking: | 8485 added |
|---|
comment:3 by , 12 years ago
| Description: | modified (diff) |
|---|
comment:4 by , 12 years ago
comment:6 by , 12 years ago
Have just tested with hrev44523 (GCC4 Hyb). Display Port not working for HD6770. Attempting to attach a syslog.
by , 12 years ago
| Attachment: | syslog.GCC4Hyb.44523 added |
|---|
comment:7 by , 12 years ago
Sorry - somehow - I submitted the wrong syslog. It shows the HD6770 using a DVI connector.
This second attachement is the correct one for the DisplayPort. eg: syslog.44523.with.DP
by , 12 years ago
| Attachment: | syslog.44523.with.DP added |
|---|
comment:8 by , 12 years ago
KERN: radeon_hd: detect_displays: ERROR: 0 attached monitors were found on display connectors. Injecting first connector as a last resort.
Definitely your first issue.. I tested the DisplayPort on my 7970 this evening and got the same error. Let me see what I can do about the EDID on DisplayPort devices.
comment:9 by , 12 years ago
| Blocked By: | 8612 added |
|---|
adding blocked by #8612.
It's unlikely that the VESA edid matches the DisplayPort endpoint edid.
As the accelerant mode_set hook doesn't pass the crtc id, the hook functions are blissfully unaware of the needed information to properly train each display port device.
follow-up: 11 comment:10 by , 12 years ago
The largest thing left to fix here is the lack of multi-head support in the AppServer.
The core problem is that currently we use the vesa edid mode for all monitors as the appserver doesn't pass which mode to set on which display. However the edid modes from vesa don't reflect *any* DisplayPort edid info as the DisplayPort monitors have to be probed.
We could set the "preferred/native mode" on each display, but this would mean the end user would get 0 choice on what displaymode to set where.
comment:11 by , 12 years ago
I tested hrev45432-gcc4-hybrid on Dell Precision M4600 with Radeon HD 6700M. Result of this test you can see on this short movie: http://dl.dropbox.com/u/92245884/20130331_173905.mp4 I attached syslog from Haiku and to comparing the log file of X11 from Linux Fedora 17.
by , 12 years ago
| Attachment: | Dell.Precision-M4600-Radeon.HD-6700M-2013-04-01-Haiku45432.log added |
|---|
by , 12 years ago
| Attachment: | Dell.Precision-M4600-Radeon.HD-6700M-2013-04-01-X11.log added |
|---|
comment:12 by , 11 years ago
| Blocking: | 10335 added |
|---|
comment:14 by , 4 years ago
| Milestone: | R1 → R1.1 |
|---|
#8826 duplicate issue was closed.