I meant DON't suspect
On Thu, Oct 20, 2016 at 11:53 PM, Maarten Maathuis <madman2...@gmail.com>
wrote:
> Also tested v3 on top of 4.8.3 (mainline git is a mess right now for
> booting).
>
> I did encounter a seemingly unrelated message during boot (inc
ents a bit
> v3: Don't clobber other ports if the current port has no alternate aux
> ch/ddc pin
>
> Cc: sta...@vger.kernel.org
> Cc: Maarten Maathuis <madman2...@gmail.com>
> Tested-by: Maarten Maathuis <madman2...@gmail.com>
> References: https://bugs.freed
Retested the _2 branch, works fine as well.
On Wed, Oct 12, 2016 at 12:57 PM, Ville Syrjälä <
ville.syrj...@linux.intel.com> wrote:
> On Tue, Oct 11, 2016 at 10:04:00PM +0200, Maarten Maathuis wrote:
> > My name does not include the word "show" (Tested-by tag).
>
&
gt;
> I've structured the code such that other platforms could easily start
> using this as well, by simply filling in the ddi_port_info. IIRC there
> may be CHV system that might actually need this.
>
> v2: Include a commit message, include a debug message during init
>
> Cc:
00 00 fc 00 55
[768590.904924] 32 34 45 38 35 30 0a 20 20 20 20 20 00 00 00 ff
[768590.904940] 00 48 54 48 47 38 30 30 30 30 35 0b ff ff ff ff
[768590.906012] nouveau :01:00.0: DRM: DDC responded, but no EDID for
HDMI-A-1
On Mon, Sep 19, 2016 at 9:50 PM, Maarten Maathuis <madm
not
enabled, skipping
[2.853617] [drm:intel_fb_initial_config] connector HDMI-A-2 not
enabled, skipping
[2.853622] [drm:intel_fb_initial_config] looking for cmdline mode on
connector DP-2
[2.853626] [drm:intel_fb_initial_config] looking for preferred mode on
connector DP-2 0
[2.853729] [
ine 88:"640x480" 73
31500 640 664 704 832 480 489 492 520 0x40 0xa
[2.870461] [drm:drm_mode_debug_printmodeline] Modeline 89:"640x480" 67
30240 640 704 768 864 480 483 486 525 0x40 0xa
[2.870466] [drm:drm_mode_debug_printmodeline] Modeline 113:"640x480" 60
25200 640
Hi,
I have a monitor, that when connected a skylake system, doesn't ever come
up when hotplugging or after resume. The "bios" seems to not have problems
bringing it up, even at the native 3840x2160 resolution, and when it works,
all modes are correctly read (checked via xrandr).
I tried both the
Hi everyone.
I've been some hardlock problems when switching from the HDMI connection of
my monitor (connected to another PC) and the displayport (connected to the
problematic PC), several times a week at least.
In an effort to narrow down the problem I've been tried looking at drm
modeset debug