Am Donnerstag, 10. Oktober 2002 01:42 schrieb Fabrice Bellet:
On Thu, Oct 10, 2002 at 12:33:59AM +0200, Michel Dänzer wrote:
What date is the DRM source you're using from?
I got that all the time with my dual Athlon MP 1900+, but nobody found a
solution so far.
Anyone who can fix the
On Thu, Oct 10, 2002 at 04:55:34PM +0200, Dieter Nützel wrote:
Am Donnerstag, 10. Oktober 2002 01:42 schrieb Fabrice Bellet:
I updated my dri HEAD cvs tree two hours ago, and I rebuilt
the drm module too.
Which kernel version?
2.4.20-pre9.
Hmm, all the interrupts are routed to the
Am Donnerstag, 10. Oktober 2002 18:25 schrieb Fabrice Bellet:
On Thu, Oct 10, 2002 at 04:55:34PM +0200, Dieter Nützel wrote:
Am Donnerstag, 10. Oktober 2002 01:42 schrieb Fabrice Bellet:
I updated my dri HEAD cvs tree two hours ago, and I rebuilt
the drm module too.
Which kernel
On Thu, Oct 10, 2002 at 06:55:40PM +0200, Dieter Nützel wrote:
Am Donnerstag, 10. Oktober 2002 18:25 schrieb Fabrice Bellet:
After doing some tests again, I noticed that R200_NO_IRQS doesn't
basically resolve the locking problem. But, when enabled,
I no longer have the drmRadeonIrqWait:
Hello,
I have regular crashes with the r200 driver, when running
more than one GL app.
I produced some logs, with drm debug enabled, and
R200_DEBUG=sanity.
The first program to be started is flightgear :
http://www.creatis.insa-lyon.fr/~bellet/r200/fgfs.log.gz
Everything is fine until I
On Don, 2002-10-10 at 00:06, Fabrice Bellet wrote:
I have regular crashes with the r200 driver, when running
more than one GL app.
I produced some logs, with drm debug enabled, and
R200_DEBUG=sanity.
The first program to be started is flightgear :
On Thu, Oct 10, 2002 at 12:33:59AM +0200, Michel Dänzer wrote:
What date is the DRM source you're using from?
I updated my dri HEAD cvs tree two hours ago, and I rebuilt
the drm module too.
Oct 10 00:53:32 dhcp7 kernel: [drm] Debug messages ON
Oct 10 00:53:32 dhcp7 kernel: [drm] AGP 0.99 on
On Don, 2002-10-10 at 01:42, Fabrice Bellet wrote:
On Thu, Oct 10, 2002 at 12:33:59AM +0200, Michel Dänzer wrote:
What date is the DRM source you're using from?
I updated my dri HEAD cvs tree two hours ago, and I rebuilt
the drm module too.
[...]
Does the interrupt count for the
On Don, 2002-09-26 at 02:22, Dieter Nützel wrote:
Any glue about the stuttering with UT?
usleeps? Again, IRQs are currently disabled in the r200 driver...
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free
On Mon, 2002-09-23 at 19:48, n001 wrote:
Small bug report of the latest r200-02-2 branch
(cvs checkout just before the merge in trunk)
With a lot of loki demos, i have this error:
r200WaitForFrameCompletion: drmRadeonIrqWait: -16
If that happened after a VT switch, it should be fixed in
On 25 Sep 2002 19:33:48 +0200
Michel Dänzer [EMAIL PROTECTED] wrote:
On Mon, 2002-09-23 at 19:48, n001 wrote:
Small bug report of the latest r200-02-2 branch
(cvs checkout just before the merge in trunk)
With a lot of loki demos, i have this error:
r200WaitForFrameCompletion:
On Mit, 2002-09-25 at 23:33, n001 wrote:
On 25 Sep 2002 19:33:48 +0200
Michel Dänzer [EMAIL PROTECTED] wrote:
On Mon, 2002-09-23 at 19:48, n001 wrote:
Small bug report of the latest r200-02-2 branch
(cvs checkout just before the merge in trunk)
With a lot of loki demos, i have
Am Donnerstag, 26. September 2002 00:17 schrieb Michel Dänzer:
On Mit, 2002-09-25 at 23:33, n001 wrote:
On 25 Sep 2002 19:33:48 +0200
Michel Dänzer [EMAIL PROTECTED] wrote:
On Mon, 2002-09-23 at 19:48, n001 wrote:
Small bug report of the latest r200-02-2 branch
(cvs checkout
On Thu, 26 Sep 2002, Dieter Nützel wrote:
Can we please change the IRQ code to not share the same IRQ with another
device?
Not up to us. It depends on the physical routing of the interrupt line on
the motherboard (often together with some amount programmability, but
Linux already tries to
Am Donnerstag, 26. September 2002 01:46 schrieb Linus Torvalds:
On Thu, 26 Sep 2002, Dieter Nützel wrote:
Can we please change the IRQ code to not share the same IRQ with another
device?
Not up to us. It depends on the physical routing of the interrupt line on
the motherboard (often
Small bug report of the latest r200-02-2 branch
(cvs checkout just before the merge in trunk)
With a lot of loki demos, i have this error:
r200WaitForFrameCompletion: drmRadeonIrqWait: -16
I have a radeon 8500 powered by ati
Thanks for you're work.
If I can help, let me know...
-
nicolas
n001 wrote:
Small bug report of the latest r200-02-2 branch
(cvs checkout just before the merge in trunk)
With a lot of loki demos, i have this error:
r200WaitForFrameCompletion: drmRadeonIrqWait: -16
I have a radeon 8500 powered by ati
Hmm. After this happens, and you run, eg
17 matches
Mail list logo
