dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105880] [dc] No support for LVDS or VGA connectors (Cannot find any crtc or sizes)
Date: Fri, 08 Jun 2018 16:08:08 +0000	[thread overview]
Message-ID: <bug-105880-502-GD2qYTYBoR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105880-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 439 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105880

--- Comment #22 from Przemek <soprwa@gmail.com> ---
Just to supplement the list above.

Netbook Lenovo g50-45, a6-6310 R4 Beema/Mullins.

Has HDMI and VGA output.

HDMI is working without a hitch, while VGA output is dead.(eDP plus only one
extra monitor connected at a time)

Thanks,
Przemek.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1265 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-06-08 16:08 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04  9:19 [Bug 105880] [dc][kabini] Cannot find any crtc or sizes bugzilla-daemon
2018-04-04  9:20 ` bugzilla-daemon
2018-04-04  9:20 ` bugzilla-daemon
2018-04-04 14:26 ` bugzilla-daemon
2018-04-05 11:59 ` bugzilla-daemon
2018-04-05 12:50 ` bugzilla-daemon
2018-04-05 20:12 ` bugzilla-daemon
2018-04-05 20:13 ` bugzilla-daemon
2018-04-11  9:04 ` bugzilla-daemon
2018-04-12  1:19 ` bugzilla-daemon
2018-04-12  1:21 ` bugzilla-daemon
2018-04-12  8:02 ` bugzilla-daemon
2018-04-13 11:28 ` bugzilla-daemon
2018-04-13 11:42 ` bugzilla-daemon
2018-04-13 12:17 ` [Bug 105880] [dc] No support for LVDS or VGA connectors (Cannot find any crtc or sizes) bugzilla-daemon
2018-04-13 16:30 ` bugzilla-daemon
2018-04-13 18:56 ` bugzilla-daemon
2018-04-13 20:01 ` bugzilla-daemon
2018-04-16 10:14 ` bugzilla-daemon
2018-04-16 10:14 ` bugzilla-daemon
2018-04-16 10:23 ` bugzilla-daemon
2018-04-24 18:53 ` bugzilla-daemon
2018-05-09 14:09 ` bugzilla-daemon
2018-05-25  8:11 ` bugzilla-daemon
2018-05-25  8:52 ` bugzilla-daemon
2018-06-08 16:08 ` bugzilla-daemon [this message]
2018-06-14 18:38 ` bugzilla-daemon
2018-06-14 18:49 ` bugzilla-daemon
2018-06-26 22:36 ` bugzilla-daemon
2018-08-14 11:03 ` bugzilla-daemon
2018-08-14 15:47 ` bugzilla-daemon
2018-08-14 19:15 ` bugzilla-daemon
2018-08-14 20:53 ` bugzilla-daemon
2018-08-14 21:01 ` bugzilla-daemon
2018-08-14 21:57 ` bugzilla-daemon
2018-08-14 22:41 ` bugzilla-daemon
2018-08-15 22:28 ` bugzilla-daemon
2018-08-16  0:11 ` bugzilla-daemon
2018-08-16  0:12 ` bugzilla-daemon
2018-08-16  1:38 ` bugzilla-daemon
2018-08-16 13:33 ` bugzilla-daemon
2018-08-17  8:40 ` bugzilla-daemon
2018-09-04 20:18 ` bugzilla-daemon
2018-09-04 20:29 ` bugzilla-daemon
2018-09-05 16:56 ` bugzilla-daemon
2019-01-31  9:08 ` bugzilla-daemon
2019-01-31 10:35 ` bugzilla-daemon
2019-01-31 10:36 ` bugzilla-daemon
2019-01-31 10:37 ` bugzilla-daemon
2019-01-31 10:55 ` bugzilla-daemon
2019-11-19  8:34 ` bugzilla-daemon

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=bug-105880-502-GD2qYTYBoR@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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).