dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15030] screen connected to displayport is not detected - kms radeon
Date: Wed, 13 Jan 2010 21:00:38 GMT	[thread overview]
Message-ID: <201001132100.o0DL0cin002140@demeter.kernel.org> (raw)
In-Reply-To: <bug-15030-2300@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=15030





--- Comment #2 from Nicolas Reinecke <pl4nkton@googlemail.com>  2010-01-13 21:00:37 ---
I now use kernel 2.6.33-rc4, before it was 2.6.33-rc3.
[    0.000000] Linux version 2.6.33-rc4-desktop32 (root@desktop) (gcc version
4.4.3 20100108 (prerelease) (Ubuntu 4.4.2-9ubuntu3) ) #1 SMP Wed Jan 13
15:28:02 CET 2010
The screen gets a video signal until drm take over control form the bios and
switch to standby.
I was wrong to report non kms as operational. No sign of DP link in xrandr,
Xorg log or dmesg.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
--

  parent reply	other threads:[~2010-01-13 21:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 18:19 [Bug 15030] New: screen connected to displayport is not detected - kms radeon bugzilla-daemon
2010-01-11 14:24 ` [Bug 15030] " bugzilla-daemon
2010-01-13 21:00 ` bugzilla-daemon [this message]
2010-01-14  1:51 ` bugzilla-daemon
2010-01-14  2:02 ` bugzilla-daemon
2010-01-18 16:54 ` bugzilla-daemon
2010-01-18 17:27 ` bugzilla-daemon
2010-01-22  0:39 ` bugzilla-daemon
2010-01-24 17:41 ` bugzilla-daemon
2010-02-02 17:25 ` bugzilla-daemon
2010-02-02 17:30 ` bugzilla-daemon
2010-02-02 17:31 ` bugzilla-daemon
2010-02-02 17:31 ` bugzilla-daemon
2010-02-13  7:09 ` bugzilla-daemon
2010-02-13  7:37 ` bugzilla-daemon
     [not found] <bug-15030-2300@https.bugzilla.kernel.org/>
2010-04-09 10:59 ` bugzilla-daemon
2010-04-09 12:11 ` bugzilla-daemon
2010-10-17 16:41 ` bugzilla-daemon
2010-10-17 16:44 ` bugzilla-daemon
2010-10-17 16:45 ` bugzilla-daemon
2010-10-17 19:19 ` bugzilla-daemon
2010-10-17 22:17 ` bugzilla-daemon
2012-06-27 12:55 ` 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=201001132100.o0DL0cin002140@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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