I'm revoking this patch. A replacement will be posted.
Thomas Hellstrom wrote:
This code wraps the struct device so that the drm class callbacks can
differentiate between different types of drm sysfs devices. It fixes a
case where a struct drm_connecor is cast to a struct drm_minor in the
The drm sysfs class suspend / resume methods could not distinguish
between different device types wich could lead to illegal type casts.
Use struct device_type and make sure the class suspend / resume callbacks
are aware of those. There is no per device-type suspend / resume. Only
new-style PM.
http://bugs.freedesktop.org/show_bug.cgi?id=23232
--- Comment #2 from Terry Barnaby te...@beam.ltd.uk 2009-08-14 02:12:59 PST
---
I have tried this on an Intel 82915G/GV/910GL machine and it has the same
problem. So it doesn't look like it is just an R200/R300 issue ...
--
Configure
The following patch fixes missing r300 compiler in generated tarballs:
diff --git a/src/mesa/drivers/dri/r300/Makefile b/src/mesa/drivers/dri/r300/Makefile
index 95c6765..3bce7d2 100644
--- a/src/mesa/drivers/dri/r300/Makefile
+++ b/src/mesa/drivers/dri/r300/Makefile
@@ -40,6 +40,7 @@
Thierry Vignaud tvign...@mandriva.com writes:
The following patch fixes missing r300 compiler in generated tarballs:
diff --git a/src/mesa/drivers/dri/r300/Makefile
b/src/mesa/drivers/dri/r300/Makefile
index 95c6765..3bce7d2 100644
--- a/src/mesa/drivers/dri/r300/Makefile
+++
Thierry Vignaud tvign...@mandriva.com writes:
Thierry Vignaud tvign...@mandriva.com writes:
The following patch fixes missing r300 compiler in generated tarballs:
diff --git a/src/mesa/drivers/dri/r300/Makefile
b/src/mesa/drivers/dri/r300/Makefile
index 95c6765..3bce7d2 100644
---
http://bugs.freedesktop.org/show_bug.cgi?id=23303
Summary: Bad: Dri enabled freezes my computer
Product: Mesa
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Keywords: regression
http://bugs.freedesktop.org/show_bug.cgi?id=23303
Alfredo Cabrera albertosapi...@gmail.com changed:
What|Removed |Added
Summary|Bad: Dri enabled freezes my |Dri enabled
http://bugs.freedesktop.org/show_bug.cgi?id=23303
Alfredo Cabrera albertosapi...@gmail.com changed:
What|Removed |Added
Severity|major |critical
http://bugs.freedesktop.org/show_bug.cgi?id=23303
--- Comment #1 from Jerome Glisse gli...@freedesktop.org 2009-08-14 07:08:13
PST ---
According to your log DRI is disabled. Please provide a Xorg log with DRI
enabled.
--
Configure bugmail:
Thierry Vignaud wrote:
Thierry Vignaud tvign...@mandriva.com writes:
Thierry Vignaud tvign...@mandriva.com writes:
The following patch fixes missing r300 compiler in generated tarballs:
diff --git a/src/mesa/drivers/dri/r300/Makefile
b/src/mesa/drivers/dri/r300/Makefile
index
http://bugs.freedesktop.org/show_bug.cgi?id=23303
--- Comment #2 from Alfredo Cabrera albertosapi...@gmail.com 2009-08-14
07:18:22 PST ---
Created an attachment (id=28626)
-- (http://bugs.freedesktop.org/attachment.cgi?id=28626)
Xorg log when Dri is enabled
--
Configure bugmail:
http://bugs.freedesktop.org/show_bug.cgi?id=23303
--- Comment #3 from Alfredo Cabrera albertosapi...@gmail.com 2009-08-14
07:20:50 PST ---
Created an attachment (id=28628)
-- (http://bugs.freedesktop.org/attachment.cgi?id=28628)
Xorg conf disabling Dri an Exa acceleration
--
Configure
http://bugs.freedesktop.org/show_bug.cgi?id=23303
--- Comment #4 from Alfredo Cabrera albertosapi...@gmail.com 2009-08-14
07:24:18 PST ---
Created an attachment (id=28631)
-- (http://bugs.freedesktop.org/attachment.cgi?id=28631)
Xorg conf with Dri and EXA acceleration method
--
http://bugs.freedesktop.org/show_bug.cgi?id=23303
--- Comment #5 from Jerome Glisse gli...@freedesktop.org 2009-08-14 07:29:12
PST ---
So it lockups even when Forced to PCI ? Or only when in AGP ? Please also
provide a Xorg log when in AGP mode.
--
Configure bugmail:
http://bugs.freedesktop.org/show_bug.cgi?id=23303
--- Comment #6 from Alfredo Cabrera albertosapi...@gmail.com 2009-08-14
08:34:11 PST ---
Created an attachment (id=28634)
-- (http://bugs.freedesktop.org/attachment.cgi?id=28634)
Xorg log running AGP mode
--
Configure bugmail:
http://bugs.freedesktop.org/show_bug.cgi?id=23303
Alfredo Cabrera albertosapi...@gmail.com changed:
What|Removed |Added
Attachment #28634|application/x-trash |text/plain
http://bugs.freedesktop.org/show_bug.cgi?id=23303
--- Comment #7 from Alfredo Cabrera albertosapi...@gmail.com 2009-08-14
08:36:55 PST ---
(In reply to comment #5)
So it lockups even when Forced to PCI ? Or only when in AGP ? Please also
provide a Xorg log when in AGP mode.
Xorg
http://bugs.freedesktop.org/show_bug.cgi?id=23303
Alfredo Cabrera albertosapi...@gmail.com changed:
What|Removed |Added
Attachment #28626|text/x-log |text/plain
http://bugs.freedesktop.org/show_bug.cgi?id=23303
Alfredo Cabrera albertosapi...@gmail.com changed:
What|Removed |Added
Attachment #28628|application/octet-stream|text/plain
On Fri, 14 Aug 2009 10:42:57 +0200
Thomas Hellstrom thellst...@vmware.com wrote:
The drm sysfs class suspend / resume methods could not distinguish
between different device types wich could lead to illegal type casts.
Use struct device_type and make sure the class suspend / resume
callbacks
http://bugzilla.kernel.org/show_bug.cgi?id=13985
Summary: incorrect via chrome9 detection
Product: Drivers
Version: 2.5
Kernel Version: 2.6.30.4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Currently detailed timings are ignored on EDID 1.3 with the comment
EDID up to and including 1.2 may put monitor info here. However, the
EDID Implementation Guide only says that on EDID 1.1 (which introduced
monitor descriptors) and EDID 1.2, the first descriptor block of the
detailed timing
On Fri, 14 Aug 2009 10:38:31 -0700
Anssi Hannula anssi.hann...@iki.fi wrote:
Currently detailed timings are ignored on EDID 1.3 with the comment
EDID up to and including 1.2 may put monitor info here. However, the
EDID Implementation Guide only says that on EDID 1.1 (which introduced
monitor
Signed-off-by: Yang Zhao y...@yangman.ca
---
drivers/gpu/drm/radeon/radeon.h |2 ++
drivers/gpu/drm/radeon/radeon_atombios.c | 28
drivers/gpu/drm/radeon/radeon_device.c |5 +
drivers/gpu/drm/radeon/radeon_mode.h |2 ++
4 files
On Fri, Aug 14, 2009 at 5:09 PM, Yang Zhaoy...@yangman.ca wrote:
Signed-off-by: Yang Zhao y...@yangman.ca
---
drivers/gpu/drm/radeon/radeon.h | 2 ++
drivers/gpu/drm/radeon/radeon_atombios.c | 28
drivers/gpu/drm/radeon/radeon_device.c | 5
Alex pointed out that this should be done on all radeons.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
Signed-off-by: Yang Zhao y...@yangman.ca
---
drivers/gpu/drm/radeon/radeon.h |2 ++
drivers/gpu/drm/radeon/radeon_atombios.c | 28
drivers/gpu/drm/radeon/radeon_device.c |3 +++
drivers/gpu/drm/radeon/radeon_mode.h |2 ++
4 files changed,
http://bugzilla.kernel.org/show_bug.cgi?id=13713
--- Comment #7 from karaba...@gmail.com 2009-08-14 21:32:55 ---
nevermind, mesa from git fixed it.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching
On Fri, Aug 14, 2009 at 5:09 PM, Yang Zhaoy...@yangman.ca wrote:
Signed-off-by: Yang Zhao y...@yangman.ca
---
drivers/gpu/drm/radeon/radeon.h | 2 ++
drivers/gpu/drm/radeon/radeon_atombios.c | 28
drivers/gpu/drm/radeon/radeon_device.c | 5
http://bugzilla.kernel.org/show_bug.cgi?id=13713
--- Comment #8 from Rafael J. Wysocki r...@sisk.pl 2009-08-14 21:43:22 ---
Should the bug be closed, then?
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are
http://bugzilla.kernel.org/show_bug.cgi?id=13713
--- Comment #9 from karaba...@gmail.com 2009-08-14 22:04:22 ---
As stated above:
Because this is a rather minimal fix, there is at least one downside: If the
whole scene completes in one batchbuffer, we'll end up stalling the GPU.
So, this
http://bugs.freedesktop.org/show_bug.cgi?id=9751
Ian Romanick i...@freedesktop.org changed:
What|Removed |Added
CC||i...@freedesktop.org
On Sat, Aug 15, 2009 at 3:45 AM, Jesse Barnesjesse.bar...@intel.com wrote:
On Fri, 14 Aug 2009 10:38:31 -0700
Anssi Hannula anssi.hann...@iki.fi wrote:
Currently detailed timings are ignored on EDID 1.3 with the comment
EDID up to and including 1.2 may put monitor info here. However, the
Currently detailed timings are ignored on EDID 1.3 with the comment
EDID up to and including 1.2 may put monitor info here. However, the
EDID Implementation Guide only says that on EDID 1.1 (which introduced
monitor descriptors) and EDID 1.2, the first descriptor block of the
35 matches
Mail list logo