From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 25052] kernel modesetting still does not work
Date: Sat, 12 Feb 2011 16:41:51 GMT [thread overview]
Message-ID: <201102121641.p1CGfpNB032491@demeter2.kernel.org> (raw)
In-Reply-To: <bug-25052-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=25052
--- Comment #13 from Elmar Stellnberger <estellnb@gmail.com> 2011-02-12 16:41:48 ---
Well; I possibly know now why it has worked with 0.0.7:
The radeonhd driver wrote 'KMS is disabled.' under this particular kernel
version - and it started up correctly: evidence enough that something does not
work with KMS in this kernel version.- and UMS is known to work.
I will try to re-test if it inspite possibly also worked with HDMI under the
0.0.7 version (though I had always been believing it was not - however I am no
more absolutely sure now). However that will hardly be possible since the
radeon driver or the dri xorg code now overflows the event loop as soon as i
just try to boot into X (https://bugs.freedesktop.org/show_bug.cgi?id=32393).
p.s.: Will git auto-apply the patch that I can view under the given http
address on the right kernel version if I invoke git with it in the right way?
One more thx. for the patch! (I will now test it after having been away for
some time).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2011-02-12 16:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25052-2300@https.bugzilla.kernel.org/>
2011-01-04 21:41 ` [Bug 25052] kernel modesetting still does not work bugzilla-daemon
2011-01-04 21:42 ` bugzilla-daemon
2011-01-04 23:03 ` bugzilla-daemon
2011-01-05 21:58 ` bugzilla-daemon
2011-01-10 17:56 ` bugzilla-daemon
2011-01-10 17:58 ` bugzilla-daemon
2011-01-10 19:21 ` bugzilla-daemon
2011-01-31 21:38 ` bugzilla-daemon
2011-01-31 21:44 ` bugzilla-daemon
2011-02-08 19:25 ` bugzilla-daemon
2011-02-08 19:31 ` bugzilla-daemon
2011-02-12 16:41 ` bugzilla-daemon [this message]
2011-02-15 22:13 ` bugzilla-daemon
2011-02-23 20:27 ` bugzilla-daemon
2011-02-23 20:45 ` bugzilla-daemon
2011-02-23 21:29 ` bugzilla-daemon
2011-03-04 15:51 ` bugzilla-daemon
2011-03-04 15:57 ` bugzilla-daemon
2011-03-04 15:58 ` bugzilla-daemon
2011-05-03 20:17 ` bugzilla-daemon
2011-08-09 17:44 ` bugzilla-daemon
2011-08-09 18:20 ` bugzilla-daemon
2011-08-16 12:34 ` bugzilla-daemon
2011-09-01 18:24 ` bugzilla-daemon
2012-03-03 19:03 ` bugzilla-daemon
2012-08-25 9:53 ` bugzilla-daemon
2012-08-25 11:30 ` bugzilla-daemon
2012-08-25 11:30 ` bugzilla-daemon
2012-08-25 13:05 ` bugzilla-daemon
2012-08-26 8:59 ` 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=201102121641.p1CGfpNB032491@demeter2.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.