-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Keith Whitwell wrote:
> Roland Scheidegger wrote:
>
>> Try this patch here:
>> http://marc.theaimsgroup.com/?l=mesa3d-dev&m=112337787415898&w=2
>> That should fix the issue. I believe it not only fixes it, but it's
>> the right thing to do, mesa maps
Alan Coopersmith wrote:
> I was wondering why ffb was even being built on x86_64. If it's referring
> to the board from Sun (which marketing called a "Creator" or "Creator 3D"),
> it was only ever made for the UPA bus (UltraSPARC Port Architecture), not
> PCI or any other common bus, and I've ne
Thomas Hellström wrote:
Hi!
Attached is a patch that stops a drm client from registering a fb /
agp memory block under an arbitrary context handle, which will lead to
heap memory leaks if the client dies.
It also stops malicious clients from freeing other clients fb / agp
memory blocks.
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4031
[EMAIL PROTECTED] changed:
What|Removed |Added
--
Roland Scheidegger wrote:
Adam K Kirchhoff wrote:
Thanks for the tip. I updated to not only the latest Mesa cvs and
drm cvs, but the latest xorg cvs. This is a vast improvement, and
XFCE4
works with DRI enabled. But... glxgears segfaults:
(gdb) run
Starting program: /usr/X11R6/bin/glx
Roland Scheidegger wrote:
Adam K Kirchhoff wrote:
Thanks for the tip. I updated to not only the latest Mesa cvs and
drm cvs, but the latest xorg cvs. This is a vast improvement, and
XFCE4
works with DRI enabled. But... glxgears segfaults:
(gdb) run
Starting program: /usr/X11R6/bin/gl
Adam K Kirchhoff wrote:
Thanks for the tip. I updated to not only the latest Mesa cvs and
drm cvs, but the latest xorg cvs. This is a vast improvement, and XFCE4
works with DRI enabled. But... glxgears segfaults:
(gdb) run
Starting program: /usr/X11R6/bin/glxgears
[Thread debugging using
Hi,
On Wednesday 10 of August 2005 14:43, Vladimir Dergachev wrote:
> > Here is dmesg output:
> >
> > [drm] Initialized drm 1.0.0 20040925
> > PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device
> > :01:00.0 [drm] Initialized radeon 1.17.0 20050720 on minor 0: ATI
> > Technologie
Here is dmesg output:
[drm] Initialized drm 1.0.0 20040925
PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device :01:00.0
[drm] Initialized radeon 1.17.0 20050720 on minor 0: ATI Technologies Inc
RV350 AS [Radeon 9600 AS]
[drm] Used old pci detect: framebuffer loaded
mtrr: 0xb0
On Jul 28, 05 19:29:19 +0200, Roland Scheidegger wrote:
> >R200 did not really have pixel shaders. They had a configurable pixel
> > pipeline, that's different. Comparable to GeForce2, a little bit
> >better.
> Looks better to me than GeForce3/4, really, if only for the dependant
> texture read. Y
Hi,
Thanks for the hint.
On Wednesday 10 of August 2005 13:43, you wrote:
> Hi,
>
> What is the dmesg output after X is terminated by the SIGKILL? I also
> am seeing X get killed the same way, and in dmesg it shows that the
> kernel killed it (see the messages with the subject "r300 DRI killing
Hi,
On Wednesday 10 of August 2005 11:53, you wrote:
> > I suggest testing a 2.6.12 not a 2.6.13, i think something might be wrong
> > with 2.6.13 (IIRC i see people complaining on lkml or on dri user) a
> > change in API a regression somewhere... But it could also be a 64bits
> > issue not seen
>
> I suggest testing a 2.6.12 not a 2.6.13, i think something might be wrong with
> 2.6.13 (IIRC i see people complaining on lkml or on dri user) a change in API
> a regression somewhere... But it could also be a 64bits issue not
> seen before :)
>
I'd appreciate if someone could test with 2.6.
On 8/10/05, Michał Pytasz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Thanks for information,
> Unfortunately yesterday I built "vanilla" kernel 2.6.12.4 and 2.6.13-rc6 from
> kernel.org - I got same results as with gentoo patched kernel.
I suggest testing a 2.6.12 not a 2.6.13, i think something might
Hi,
On Wednesday 10 of August 2005 10:28, you wrote:
> On 8/9/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
> > Hi Michal,
> >
> > > (II) RADEON(0): [drm] DRM interface version 1.2
> > > (II) RADEON(0): [drm] created "radeon" driver at busid
> > > "pci::01:00.0" (II) RADEON(0): [drm] added
On 8/9/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
>
> Hi Michal,
>
> >
> > (II) RADEON(0): [drm] DRM interface version 1.2
> > (II) RADEON(0): [drm] created "radeon" driver at busid "pci::01:00.0"
> > (II) RADEON(0): [drm] added 8192 byte SAREA at 0xc2bfc000
> >
> > Program ter
Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernardo Innocenti wrote:
GAS choked on the DRM_CAS invocation in ffb_lock.h because
__ret was declared as "int" and so it gets passed in %edx
instead of %dl or %dh as required by the setnz instruction.
I just wrapped the decla
17 matches
Mail list logo
