On Thursday 17 December 2009 19:13:59 Jesse Barnes wrote:
Ok, I'll try that. The problem is keeping me from doing any useful
upstream kernel work on my main machine, so I'm rather motivated ;-)
Another patch to try...
Thanks!
It's running fine so far, uptime 90 minutes together with
On Sun, Dec 20, 2009 at 09:03:27AM +0200, Marin Mitov wrote:
Hello all,
Silancing a false positive:
warning: 'width' may be used uninitialized in this function
drivers/gpu/drm/drm_edid.c
Is it guaranteed that the switch will always see a value covered by the
four cases it has? If not width
http://bugs.freedesktop.org/show_bug.cgi?id=25718
--- Comment #7 from Rafał Miłecki zaj...@gmail.com 2009-12-20 02:48:29 PST
---
I don't know... The only place where I mess with fences it:
read_lock_irqsave(rdev-fence_drv.lock, irq_flags);
if (!list_empty(rdev-fence_drv.emited)) {
W dniu 18 grudnia 2009 19:42 użytkownik Rafał Miłecki
zaj...@gmail.com napisał:
V2: reorganize functions, fix modesetting calls
V3: rebase patch, use radeon's workqueue
V4: enable on tested chipsets only, request VBLANK IRQs
V5: enable PM on older hardware (IRQs, mode_fixup, dpms)
V6: use
http://bugs.freedesktop.org/show_bug.cgi?id=24844
--- Comment #11 from Bruno bonbon...@internet.lu 2009-12-20 07:21:59 PST ---
(In reply to comment #10)
Some of the DRM patches between 2.6.32 and 2.6.33-rc1 do fix the issue, I've
tried to determine the exact patch.
I've *not yet* tried to
http://bugs.freedesktop.org/show_bug.cgi?id=24844
--- Comment #10 from Bruno bonbon...@internet.lu 2009-12-20 07:20:55 PST ---
Some of the DRM patches between 2.6.32 and 2.6.33-rc1 do fix the issue, I've
tried to determine the exact patch.
It's probably one of those that touch EDID
http://bugs.freedesktop.org/show_bug.cgi?id=25290
--- Comment #3 from Rafael Monica monr...@gmail.com 2009-12-20 08:49:05 PST
---
I think I found the problem. The hardware already makes the right decision
based on the FACE_bit. This code in r700UpdatePolygonMode actually reverses it
when
http://bugs.freedesktop.org/show_bug.cgi?id=25718
--- Comment #8 from Trevour bio_t...@yahoo.com 2009-12-20 08:50:47 PST ---
With 2.6.31.1 and drm-radeon-testing of four days ago with V7 and ATOM lock
applied, I have no problems here. Has anyone tested V7 with the newer changes?
--
2009/12/19 Christian König deathsim...@vodafone.de:
Hi,
Am Samstag, den 19.12.2009, 15:37 +0100 schrieb Luca Tettamanti:
- first of all, I have a M56 (RV630) which lacks the PCI audio
function, I guess in this case the audio shouldn't be enabled at all
That's definitely a bug, AFAIK
http://bugs.freedesktop.org/show_bug.cgi?id=25731
Summary: [Radeon FireGL][RV635] Too many stalls with KMS and IRQs
enabled
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status:
http://bugs.freedesktop.org/show_bug.cgi?id=25731
--- Comment #1 from Shawn Starr shawn.st...@rogers.com 2009-12-20 11:01:11
PST ---
See URL for XML call without KMS enabled here:
http://www.sh0n.net/spstarr/radeon/secondlife-r600-nokms.log.bz2
--
Configure bugmail:
http://bugs.freedesktop.org/show_bug.cgi?id=25718
--- Comment #9 from Rafał Miłecki zaj...@gmail.com 2009-12-20 12:00:24 PST
---
I got info from Aidan that he experienced similar (same?) problem with dynpm=0
and while playing Nexuiz for longer time (about 15mins?).
Not sure what is real
Am Sonntag, den 20.12.2009, 19:10 +0100 schrieb Luca Tettamanti:
Typo, sorry: it's a M76 (the core is a RV630).
Interesting, I always thought that every R6xx based chipset has an audio
codec. Could you make sure that there is no audio codec on this chipset?
Take a look in the bios, its possible
http://bugs.freedesktop.org/show_bug.cgi?id=25718
--- Comment #10 from Trevour bio_t...@yahoo.com 2009-12-20 12:02:26 PST ---
(In reply to comment #8)
With 2.6.31.1 and drm-radeon-testing of four days ago with V7 and ATOM lock
applied, I have no problems here. Has anyone tested V7 with the
2009/12/20 Christian König deathsim...@vodafone.de:
Am Sonntag, den 20.12.2009, 19:10 +0100 schrieb Luca Tettamanti:
Typo, sorry: it's a M76 (the core is a RV630).
Interesting, I always thought that every R6xx based chipset has an audio
codec. Could you make sure that there is no audio codec
http://bugs.freedesktop.org/show_bug.cgi?id=25109
--- Comment #5 from Tom Stellard tstel...@gmail.com 2009-12-20 18:50:04 PST
---
I am now using:
xorg-server: 1.7.4 RC 1
kernel: 2.6.32 with KMS disabled.
wine: 1.1.35
and the most recent git versions of libdrm and ddx.
I can reproduce this
http://bugs.freedesktop.org/show_bug.cgi?id=25662
--- Comment #4 from Tom Stellard tstel...@gmail.com 2009-12-20 18:56:25 PST
---
I have done some debugging of the problem, and it appears my system locks up
while calling glXSwapBuffers() on line 340 of glxgears.c. This is while I am
using
http://bugs.freedesktop.org/show_bug.cgi?id=25733
Summary: Latest drm-radeon-testing fails to suspend
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
I've reworked Arnd's two patches to we have all the core changes in one
patch, this in theory should change no behaviour in any of the current
drivers.
Patch 2: updates the vmwgfx unlocked ioctl code, to use the new interface
as this work conflicts with its current interface.
From: Dave Airlie airl...@redhat.com
For some reason these ioctls have no DRM flags, which just seems wrong,
so I guess that needs reviewing also before staging exit.
Signed-off-by: Dave Airlie airl...@redhat.com
---
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 69 ---
From: Arnd Bergmann a...@arndb.de
drm_ioctl is called with the Big Kernel Lock held,
which shows up very high in statistics on vfs_ioctl.
Moving the lock into the drm_ioctl function itself
makes sure we blame the right subsystem and it gets
us one step closer to eliminating the locked version
of
From: Bob Gleitsmann rjgle...@bellsouth.net
This is from bug 25728.
[airlied: I'm just forwarding the patch for review, Thomas, ickle?]
---
drivers/gpu/drm/drm_mm.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c
From: Dave Airlie airl...@redhat.com
In 2.6.32.2 r600 had no IRQ support, however the patch in
500b758725314ab1b5316eb0caa5b0fa26740e6b to fix vblanks on avivo
cards, needs irqs.
So check for an R600 card and avoid this path if so.
This is a stable only patch for 2.6.32.2 as 2.6.33 has IRQs for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Subject: [ANNOUNCE] libdrm 2.4.17
To: xorg-annou...@lists.freedesktop.org
CC: dri-de...@lists.freedesktop.org
The experimental radeon API changed a lot, still experimental,
but I don't think it'll break incompatability again after this.
This also
I just tried to compile last stable kernel with radeon DRM gpu driver
and I got this:
...
LD vmlinux.o
MODPOST vmlinux.o
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
On Sunday 20 December 2009 11:56:44 am Simon Horman wrote:
On Sun, Dec 20, 2009 at 09:03:27AM +0200, Marin Mitov wrote:
Hello all,
Silancing a false positive:
warning: 'width' may be used uninitialized in this function
drivers/gpu/drm/drm_edid.c
Is it guaranteed that the switch will
With 2.6.32.2 the system hangs completely with black screen when modprobing
radeon with modeset=1. I was able to connect via ssh, but after entering the
password nothing happend. I didn't got a prompt. Only SysRq worked. I've
tracked it down to the following patch:
From
2009/12/20 Ruud Linders kerne...@xs4all.nl:
Hello,
After upgrading from 2.6.32.1 to 2.6.32.2 my radeon KMS broke. Broke
meaning after kernel boot at the moment radeon module is loaded, I get a
blank screen, monitor goes in powersave mode and machine stops booting
(ping-able but can't login
Johannes Hirte wrote:
With 2.6.32.2 the system hangs completely with black screen when modprobing
radeon with modeset=1. I was able to connect via ssh, but after entering the
password nothing happend. I didn't got a prompt. Only SysRq worked. I've
tracked it down to the following patch:
On Sun, Dec 20, 2009 at 12:43:19PM +0200, Marin Mitov wrote:
On Sunday 20 December 2009 11:56:44 am Simon Horman wrote:
On Sun, Dec 20, 2009 at 09:03:27AM +0200, Marin Mitov wrote:
Hello all,
Silancing a false positive:
warning: 'width' may be used uninitialized in this function
30 matches
Mail list logo
