Re: [r300] what about *BSD?

> On Tuesday 19 April 2005 10:49 am, jan kreuzer wrote: > > Hi > > > > the fix you provided let the module get compiled. > > However when starting an GL-Application i get the following: > > > > glxgears > > Using 8 maximum texture units.. &

Re: [r300] what about *BSD?

Ok after i commented the r300_check_range function (line 256 in r300_cmdbuf.c) glxgears and xscreensaver work. No i am compiling some GL-Progs under FreeBSD and see if they work also. Greetings Jan -- +++ GMX - Die erste Adresse für Mail, Message, More +++ 1 GB Mailbox bereits in GMX FreeMail h

Re: [r300] what about *BSD?

Hi the fix you provided let the module get compiled. However when starting an GL-Application i get the following: glxgears Using 8 maximum texture units.. sizeof(drm_r300_cmd_header_t)=4 sizeof(drm_radeon_cmd_buffer_t)=32 Allocating 284420 bytes command buffer (max state is 11140 bytes)

Re: [r300] what about *BSD?

On Tue, 15 Mar 2005 18:36:21 -0500, Jung-uk Kim <[EMAIL PROTECTED]> wrote: > I have sort of working drm but I always get this from drm when I run > glxinfo or glxgears: > > drm0: port 0x2000-0x20ff mem \ > 0xd010-0xd010,0xd800-0xdfff irq 16 at device > 0.0 on \ >

Re: R300 success stories

> nwn probably uses something which requires elts to be supported (ie. > glDrawElements). > The latest cvs snapshot has made a start on this, but more information > is needed. I've > had some success with ut2004 by putting the indices into the command > buffer, but > ultimately this is not how we

Re: R300 success stories

Hi i tested nwn with latest cvs-snapshot of r300. It runs, however the screen is totally weird. I uploaded an screenshot of what the screen looks like to http://www.freephotoserver.com/files/img14048784_50868694.jpg . Neverball runs fine, the only option which slows it down is reflection (which ne

Re: DRM change for R300 DMA

Ok the oops seems to be related to my sensor monitor (superkaramba), i disabled it and i get no more oops (although this should not happen). However i still am not able to get dri working when debugging is enabled in the drm module (with and without Bens patch). Here is the output from dmesg: [dr

Re: DRM change for R300 DMA

Hi again when i try to load the drm module with debug enabled i get the following message in my syslog (and dri works not in xorg): Unable to handle kernel NULL pointer dereference at 0018 RIP: {:radeon:gpio_setsda+20} PML4 efa6067 PGD e4ce067 PMD 0 Oops: [1] PREEMPT CPU 0 Modules

Re: DRM change for R300 DMA

Hi Ben your patch seems to solve some of the lockups I experienced (for example without your patch i got random lockups after trying some of the nehe lessons, now i can run most of them fine). However i noticed that xorg cpu-usage went up to 10% (from around 1%) and that the screen rendering (2D a

Re: amd64 + r300.sf.net drivers

Nope glxinfo should state directrendering yes. Try "LIBGL_DEBUG=verbose glxinfo" and post the output. Greetings Jan -- +++ GMX - die erste Adresse für Mail, Message, More +++ 1 GB Mailbox bereits in GMX FreeMail http://www.gmx.net/de/go/mail

Re: [R300] red_tinted_cube snapshot

Hi i get the following compile error on an FC3 x86_64 system when trying the new snapshot: gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver - I../../../../../../drm/shared-core -I../../../../../include - I../../../../../include/GL/internal -I../../../../../src/mesa - I../../../../.

Re: amd64 + r300.sf.net drivers

I saw that you have Option "AGPFastWrite" "on" in your xorg.conf, try to disable it. My system also locks up when it is on (same symptoms as yours), but works when i disable it. It seems this is the same behaviour as described in the following bur reports: https://bugs.freedesktop.org/show_bug.cg

Re: r300.sf.net r300_driver and amd64 (now working)

Hi i found out what was wrong, i used the wrong drm driver. Now the gears are rotating. Good work and a happy new year Jan --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt f

r300.sf.net r300_driver and amd64

Hi i just tried again the r300_driver, compiled and installed it on FedoraCore3 x86_64. I updated Xorg via cvs to the latest version and also downloaded latest mesa-cvs and drm-cvs. I compiled the kernel module and compiled the driver as stated in the instructions. glxinfo is working, but only aft

R300 driver on AMD64

0 pro (RV350 AP). Thanks for your work and greetings Jan Kreuzer --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the bes