The attached set of patches adds an i2c algo for radeon hardware. It
transparently supports bit-banging i2c on all asics and uses the hw
i2c engine on supported asics (r1xx-r5xx right now, support for newer
chips can be added later). For the bit banging, it encapsulates the
gpio masking that
http://bugs.freedesktop.org/show_bug.cgi?id=25776
Summary: [regression] crash on loading radeon module on 2.6.33-
rc1 vanilla
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status:
From: Michel Dänzer daen...@vmware.com
Signed-off-by: Michel Dänzer daen...@vmware.com
---
drivers/gpu/drm/radeon/radeon_combios.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_combios.c
b/drivers/gpu/drm/radeon/radeon_combios.c
index
From: Michel Dänzer daen...@vmware.com
The HDP read cache should only affect CPU reads from VRAM.
Signed-off-by: Michel Dänzer daen...@vmware.com
---
drivers/gpu/drm/radeon/radeon_gem.c | 12
1 files changed, 8 insertions(+), 4 deletions(-)
diff --git
The C99 specification states in section 6.11.5:
The placement of a storage-class specifier other than at the beginning
of the declaration specifiers in a declaration is an obsolescent
feature.
Signed-off-by: Tobias Klauser tklau...@distanz.ch
---
drivers/gpu/drm/i915/intel_display.c |8
http://bugs.freedesktop.org/show_bug.cgi?id=25779
Summary: Crash in radeon using the drm-radeon-testing branch of
drm-next
Product: DRI
Version: DRI CVS
Platform: Other
OS/Version: All
Status: NEW
http://bugs.freedesktop.org/show_bug.cgi?id=25779
--- Comment #1 from Kevin DeKorte kdeko...@yahoo.com 2009-12-23 08:14:36 PST
---
Card is an rv635 card
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3600
Series (prog-if 00 [VGA controller])
Subsystem:
A drm_handle_t can be safely converted to a pointer and back even on a
64bit platform (where the size is not the same).
Signed-off-by: Luca Tettamanti kronos...@gmail.com
---
I looked at the kernel part of the ioctl and it seems that the handle is
always a 32bit quantity, but please double check
http://bugs.freedesktop.org/show_bug.cgi?id=25776
--- Comment #1 from Luca Tettamanti kronos...@gmail.com 2009-12-23 12:41:44
PST ---
It happens when firmware for the interrupt controller is missing; a proper
fallback should already be present in airlied's tree:
On Wed, 2009-12-23 at 21:36 +0100, Luca Tettamanti wrote:
A drm_handle_t can be safely converted to a pointer and back even on a
64bit platform (where the size is not the same).
Signed-off-by: Luca Tettamanti kronos...@gmail.com
---
I looked at the kernel part of the ioctl and it seems that
On Wed, Dec 23, 2009 at 10:05 PM, Robert Noland rnol...@2hip.net wrote:
On Wed, 2009-12-23 at 21:36 +0100, Luca Tettamanti wrote:
A drm_handle_t can be safely converted to a pointer and back even on a
64bit platform (where the size is not the same).
Signed-off-by: Luca Tettamanti
On Wed, 2009-12-23 at 22:55 +0100, Luca Tettamanti wrote:
On Wed, Dec 23, 2009 at 10:05 PM, Robert Noland rnol...@2hip.net wrote:
On Wed, 2009-12-23 at 21:36 +0100, Luca Tettamanti wrote:
A drm_handle_t can be safely converted to a pointer and back even on a
64bit platform (where the size
I applied patches from http://www.botchco.com/alex/xorg/pm/ and now
engine reclocks between 110MHz and 680MHz.
The problem is I see ~10 black horizontal lines for a one frame time
on almost every reclock. I tried to fix this or at least understand it
somehow but without success.
1) Putting 500ms
2009/12/23 Rafał Miłecki zaj...@gmail.com:
I applied patches from http://www.botchco.com/alex/xorg/pm/ and now
engine reclocks between 110MHz and 680MHz.
The problem is I see ~10 black horizontal lines for a one frame time
on almost every reclock. I tried to fix this or at least understand it
W dniu 24 grudnia 2009 02:59 użytkownik Alex Deucher
alexdeuc...@gmail.com napisał:
2009/12/23 Rafał Miłecki zaj...@gmail.com:
Do you have any other ideas?
I suspect the reclock is missing the blanking period. Try removing
the debugging output in my patch as that adds additional latency.
2009/12/23 Rafał Miłecki zaj...@gmail.com:
W dniu 24 grudnia 2009 02:59 użytkownik Alex Deucher
alexdeuc...@gmail.com napisał:
2009/12/23 Rafał Miłecki zaj...@gmail.com:
Do you have any other ideas?
I suspect the reclock is missing the blanking period. Try removing
the debugging output in
On Thu, 2009-12-24 at 03:24 +0100, Rafał Miłecki wrote:
W dniu 24 grudnia 2009 02:59 użytkownik Alex Deucher
alexdeuc...@gmail.com napisał:
2009/12/23 Rafał Miłecki zaj...@gmail.com:
Do you have any other ideas?
I suspect the reclock is missing the blanking period. Try removing
the
17 matches
Mail list logo
