David Dawes wrote:
On Tue, Jan 27, 2004 at 06:45:10PM +, Alan Hourihane wrote:
On Tue, Jan 27, 2004 at 12:37:51PM -0500, David Dawes wrote:
There are quite a few Radeon-related bugs still outstanding in
bugs.xfree86.org, including several related to DRI lockups.
Has anyone followed them up?
I was pretty sure that the snapshots did staticly link with libexpat.a.
I remember there being some discussion about this. Once XFree86 4.4.0
hits the streets this particular problem will be moot. AFAIK, XFree86
4.4.0 will include libexpat. However, I still think that the default
should be
John Dennis wrote:
The locking problem is solved, my original analysis was incorrect. The
problem was that DRM_CAS was not correctly implemented on IA64. Thus
this was an IA64 issue only, this is consistent with others who showed
up in a google search describing the problem, all were on IA64.
I
John Dennis wrote:
[Note: this is cross posted between dri-devel and [EMAIL PROTECTED] ]
I'm trying to debug a hung X server problem with DRI using the radeon
driver. Sources are XFree86 4.3.0. This happens to be on ia64, but at
the moment I don't see anything architecture specific about the
Keith Whitwell wrote:
John Dennis wrote:
[Note: this is cross posted between dri-devel and [EMAIL PROTECTED] ]
I'm trying to debug a hung X server problem with DRI using the radeon
driver. Sources are XFree86 4.3.0. This happens to be on ia64, but at
the moment I don't see anything architecture
Thomas Winischhofer wrote:
Keith Whitwell wrote:
Thomas Winischhofer wrote:
Keith Whitwell wrote:
Unless someone can tell me I'm wrong, the SiS driver hasn't been
maintained in a long time. It sounds like it's quite broken
should be turned off.
You are *not* wrong: The SiS DRI driver
Andrew Barr wrote:
I am having a problem using DRI on my SiS 630 based board. Everything
seems OK...the X log says that DRI is enabled, the libGL.so.1.2 library
supports DRI (checked by strings libGL.so.1.2 | grep DRI as per the
DRI debug page: http://gatos.sourceforge.net/dri-debug.php), and
[EMAIL PROTECTED] wrote:
Further details about my current configuration:
Linux: Debian GNU/Linux unstable
CPU: Athlon 1.3GHz
RAM: 1024M
XFree86: 4.3.0, built from source
Video Card: ATI All-In-Wonder Radeon, with updated drivers from GATOS
(experimental 8)
OpenGL appears to work almost entirely
Michel Dänzer wrote:
On Sam, 2003-03-22 at 17:18, Keith Whitwell wrote:
[EMAIL PROTECTED] wrote:
Further details about my current configuration:
Linux: Debian GNU/Linux unstable
CPU: Athlon 1.3GHz
RAM: 1024M
XFree86: 4.3.0, built from source
Video Card: ATI All-In-Wonder Radeon, with updated
José Fonseca wrote:
No DRI developer expressed his interest or opposition, probably because
there isn't opposition, or simply no interest. In either case I see no
reasons why not proceed, so I'll open a bug to address this. I'll ask
that [EMAIL PROTECTED] (the same addressed used on SF BT
system)
In fact the lockup comes down to this one line:
--- radeon_driver.c28 Oct 2002 02:21:14 -1.44
+++ radeon_driver.c29 Oct 2002 13:49:25 -1.45
@@ -4639,6 +4639,7 @@
save-cap0_trig_cntl = 0;
save-cap1_trig_cntl = 0;
save-bus_cntl =
Michel Dänzer wrote:
On Mit, 2003-03-12 at 11:51, Keith Whitwell wrote:
In fact the lockup comes down to this one line:
--- radeon_driver.c28 Oct 2002 02:21:14 -1.44
+++ radeon_driver.c29 Oct 2002 13:49:25 -1.45
@@ -4639,6 +4639,7 @@
save-cap0_trig_cntl = 0
3. A good old segfault:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1026 (LWP 712)]
0x404dd042 in _swrast_InvalidateState ()
from /usr/X11R6/lib/modules/dri/radeon_dri.so
(gdb) bt
#0 0x404dd042 in _swrast_InvalidateState ()
from
Michel Dänzer wrote:
[ please move this thread to the appropriate development list(s) ]
On Fre, 2003-01-17 at 16:03, Alexis Vartanian wrote:
problem : GL application hangs at starting (quake3 and a threaded)
when running a multithread application, any call to _XRead should
be done after a
Count me in as much as I can help. I can make the hardware sing but I
know zilch about the Mesa end of things. I'm also interested in Voodoo2
since its for many people the best video card you can shove in old hppa
boxes and in sis 6326 (because its a good simplicity test)
At one point there was
Alan Cox wrote:
On Thu, 2002-10-31 at 15:58, José Fonseca wrote:
I don't know much about SIS 6326. I know that there is some deprecated
(it hasn't been updated for the architectural changes) support for SIS
630 chips on the CVS.
6326 is much older than 630 and 315 etc. Its in the PIO with
Ti Leggett wrote:
There seems to be a 512x512 OpenGL texture size limit for ATI 7500
Mobility. There's a game I'm helping test and it uses textures over
1024x1024 and they work on a regular ATI 7500 but don't on a 7500
Mobility. 512x512 textures do work though. Any ideas why this is? It's
Brian Paul wrote:
Keith Whitwell wrote:
Ti Leggett wrote:
There seems to be a 512x512 OpenGL texture size limit for ATI 7500
Mobility. There's a game I'm helping test and it uses textures over
1024x1024 and they work on a regular ATI 7500 but don't on a 7500
Mobility. 512x512 textures do
Keith Packard wrote:
Around 17 o'clock on Jul 1, James Ralston wrote:
So, it would appear that 3D support for the Radeon 64 DDR and the
Radeon Mobility M6 LY (and I suspect all Radeons) was accidentally
broken in CVS sometime on or before 2002-06-23.
It's been broken for me on my M6 LY
David D. Hagood wrote:
I've come across a weird problem in the Radeon drivers in 4.2 -
depending upon the horizontal scan rates I specify for my monitor, I can
cause a divide by zero within the Radeon init code.
You might be better off posting this problem on the Xpert (XFree86) mailing
James H. Cloos Jr. wrote:
Fabrice == Fabrice Bellet [EMAIL PROTECTED] writes:
the FireGL driver does not enable bus mastering on the graphics card, but
this is essential. So you have to do before starting the Xserver with setpci
by setting bit 2 of the command register-
Fabrice Wow it
Paul Matthias Diderichsen wrote:
Hi,
[EMAIL PROTECTED] wrote:
3. i810 + KDE display corruption (Dirk =?ISO-8859-1?Q?St=F6ffler?=)
A year ago, I had the severe version of the problem you describe. I was
able to (almost - once in a while there are a few stribes) cure it by
José Fonseca wrote:
Jens,
On 2002.05.13 14:58 Jens Owen wrote:
Jose,
I recommend a full two way merge (DRI-kernel and kernel-DRI). The
kernel-DRI changes can be submitted directly to our repository for
testing. The DRI-kernel changes require a patch be submitted to the
kernel
Mark Vojkovich wrote:
Currently, for libXvMC, Intel and NVIDIA have static libraries
that work essentially like libGLcore and is used in conjuction
with libXvMC.a. I want to move to a libXvMC.so plus libXvMCcore.so
type operation where libXvMC dlopens the appropriate core for
the
Vladimir Dergachev wrote:
On Wed, 30 Jan 2002, Gareth Hughes wrote:
Gareth, the current driver is broken. If someone wants to use video
capture they _need_ both GATOS 2d driver and GATOS drm driver, period.
What's so wrong about upgrading ?
Guaranteed, someone will get a
Vladimir Dergachev wrote:
On Wed, 30 Jan 2002, deek wrote:
Vladimir Dergachev scribbled:
__snipped_
I've implemented this (easier than software CCE) scheme. If you want to
please try the latest ati.2 CVS code at http://gatos.sf.net - or just take
a look at it.
Vladimir Dergachev wrote:
On Wed, 30 Jan 2002, Daryll Strauss wrote:
On Wed, Jan 30, 2002 at 02:05:42PM -0500, Vladimir Dergachev wrote:
Regardless of the way it is merged the driver major version will need to
be bumped. GATOS drivers does this but only minor - as I did not want to
Vladimir Dergachev wrote:
On Wed, 30 Jan 2002, Daryll Strauss wrote:
On Wed, Jan 30, 2002 at 03:15:53PM -0500, Vladimir Dergachev wrote:
I completely agree with you.. but I did not give you details :))
What happens is that if you try to use older drm driver with GATOS 2d
driver
28 matches
Mail list logo
