[Dri-devel] [Bug 314] 3D support for Radeon IGP chips
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=314 --- Additional Comments From [EMAIL PROTECTED] 2003-12-18 02:26 --- >I had the same problem, then I found we need to use the radeon dri module >provided with xfree and not the one provided with the kernel. >I tried it, but the new module can't open the device... in fact the device do >not exist and i don't know th minor and the major associated... I did patch dri in the xfree86 4.3.99.16. used make -f Makefile.linux LINUXDIR=/usr/src/linux-2.6.0-test11 builds fine, I copy the module to /lib/modues/2.6.0-test11/blah blah replacing the old radeon.ko, load the module with insmod, start up xfree86, and no dri. I have an IGP320M. -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] S3 SavageDDR
Hello, the new SavageDDR DRI driver compiles and seems to run. glxinfo doesn't show 'Indirect Rendering' any more, but starting q3demo or a 3D screensaver the X-Server crashes and restarts, is that what is meant by: ' ... - almost certain lockups on vt switches and when moving 3D windows ...' ? Another thing: I first tried to start the X-Server in my building directory, X started and worked (in 1280x1024), but complained about not finding the Xlib DRI extension - so after a 'make install' DRI worked, but now I only get a resolution of 1024x768 instead of 1280x1024, although I didn't touch the Modes in the Screen-Section of XF86Config ... any hints ?? [Somewhere in XFree86.0.log it says: '(II) SAVAGE(0): Not using default mode "1280x1024" (hsync out of range)' is that possible, although it worked without DRI?] Thanks, Mario --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] S3 SavageDDR
On Thu, 18 Dec 2003 09:02:44 +0100 "Mario Premke" <[EMAIL PROTECTED]> wrote: > Hello, > > the new SavageDDR DRI driver compiles and seems to run. glxinfo doesn't show > 'Indirect Rendering' any more, but starting q3demo or a > 3D screensaver the X-Server crashes and restarts, is that what is meant by: ' ... - > almost certain lockups on vt switches and when > moving 3D windows ...' ? No. Lockup means that the Xserver starts using nearly 100% CPU and is frozen or veeery slooow. Usually I can still reboot via remote login or by pushing the power button (which is caught by acpid that does a clean shutdown). I havn't seen my Xserver crash and restart yet. If you could find out why it crashes (segmentation fault?) and where that would be very helpful. For a start look at the end of your /var/log/XFree86.0.log. > Another thing: I first tried to start the X-Server in my building directory, X > started and worked (in 1280x1024), but complained > about not finding the Xlib DRI extension That's because you need more than just the new Xserver installed but also the new 2D driver, DRI extension module, GLX extension module and glcore for indirect rendering. > - so after a 'make install' DRI worked, but now I only get a resolution of 1024x768 > instead > of 1280x1024, although I didn't touch the Modes in the Screen-Section of XF86Config > ... any hints ?? [Somewhere in XFree86.0.log it > says: '(II) SAVAGE(0): Not using default mode "1280x1024" (hsync out of range)' is > that possible, although it worked without DRI?] The savage-2-0-0-branch has a completely different 2D driver. Try adding appropriate HorizSync and VertRefresh lines to your monitor section in XF86Config-4. If that doesn't help take another look at your XFree86.0.log. It should point out what hsync value the driver assumes and where it comes from. > > Thanks, > Mario > Felix __\|/_____ ___ - Felix ___\_e -_/___/ __\___/ __\_ You can do anything, Kühling (_\Ä// /_/ /) just not everything [EMAIL PROTECTED] \___/ \___/ Uat the same time. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] s3tc for r200, radeon, mesa
Jacek Popławski wrote: On Thu, Dec 18, 2003 at 02:43:09AM +0100, Roland Scheidegger wrote: and I don't know if any open-source compressors exist which could easily be included in mesa I don't know what is it, but I saw it on freshmeat: http://www.hut.fi/~vhelin/boxen.html this doesn't have its own compressor, it uses OGL to compress the textures. (from the readme: 4. HOW DOES IT DO IT? s3tc-boxen simply loads the texture into your video card's ram and tells the video card to s3tc-compress it.) (though I doubt there are video cards which actually can do it, afaik all consumer video cards do this in the driver but I could be wrong) Roland btw forgot to mention another limitation of the r200 s3tc patch, it can't do gart texturing (which is currently disabled anyway) for now. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] [Announce] Savage 3D driver in CVS
Felix, I tested your driver on my savage4 and i couldn't make the 3D driver work (i changed the code to enable direct render on savage4), the Xfree86 just can't find /dev/dri/cardX and i loaded agpgart and savage modules without warnings but it just doesn't create the device, i checked /dev/dri and it was empty. I'm still using kernel 2.4.21 and i will upgrade to 2.4.23 today but i don't know if this is the problem, I also tried running on xfree86 4.3.0 and with the binary on Alan's page (http://www.xfree86.org/~alanh/) but no change no matter if i'm run with root or normal user. Any help? beside the 3D problem, my screen is corrupted when my XFree86 starts, the same problem i posted before. bye. At 10:54 AM 17/12/2003, Felix Kühling wrote: Content-Transfer-Encoding: 8bit On Wed, 17 Dec 2003 10:50:26 -0300 Rafael Maximo <[EMAIL PROTECTED]> wrote: > Felix, > > Very nice. I'll try it latter. What version of Xfree86 did you > test it? The one on the savage-2-0-0-branch. The XFree86 version that is installed by my distribution is 4.2.1. But that shouldn't matter as all important stuff is replaced by the DRI stuff. Rafael Máximo --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] 2.6.0 problems.
So I decided to give 2.6.0 a shot this morning :-) My Radeon 8500 (which previous worked with 2.4.22) refuses to enable direct rendering: (WW) RADEON(0): [agp] AGP not available (II) RADEON(0): [drm] removed 1 reserved context for kernel (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0882000 at 0x48267000 (WW) RADEON(0): DRI forced on with virtual screen of greater than 2048. (II) RADEON(0): Direct rendering disabled $ lsmod: radeon122488 0 emu10k191300 0 sound 87464 1 emu10k1 soundcore 9664 2 emu10k1,sound ac97_codec 19264 1 emu10k1 eepro100 30508 0 mii 5344 1 eepro100 ipt_state 1952 6 ip_conntrack 45888 1 ipt_state iptable_filter 2880 1 ip_tables 22192 2 ipt_state,iptable_filter ide_scsi 15812 0 agpgart33292 0 nls_iso8859_1 4128 1 nls_cp437 5792 1 vfat 16416 1 fat47136 1 vfat agpgart *is* loaded (though unused). $ dmesg | grep agpgart Linux agpgart interface v0.100 (c) Dave Jones Is this definately an AGP issue that I should e-mail Dave Jones about? Adam --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] 2.6.0 problems.
On Thu, 2003-12-18 at 15:12, Adam K Kirchhoff wrote: > So I decided to give 2.6.0 a shot this morning :-) > > My Radeon 8500 (which previous worked with 2.4.22) refuses to enable > direct rendering: > > (WW) RADEON(0): [agp] AGP not available > (II) RADEON(0): [drm] removed 1 reserved context for kernel > (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0882000 at 0x48267000 > (WW) RADEON(0): DRI forced on with virtual screen of greater than 2048. > > (II) RADEON(0): Direct rendering disabled > > agpgart *is* loaded (though unused). > > $ dmesg | grep agpgart > Linux agpgart interface v0.100 (c) Dave Jones > > Is this definately an AGP issue that I should e-mail Dave Jones about? > Under 2.6 you need to load both agpgart and the chipset specific agp module (like via-agp, intel-agp, amd64-agp and others) -- Ronny V. Vindenes <[EMAIL PROTECTED]> --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] 2.6.0 problems.
in 2.6 there are two agp related kernel modules that need to be loaded. agpgart and your agp chipset specific module (via, sis, ati, etc.). Alex --- Adam K Kirchhoff <[EMAIL PROTECTED]> wrote: > > So I decided to give 2.6.0 a shot this morning :-) > > My Radeon 8500 (which previous worked with 2.4.22) refuses to enable > direct rendering: > > (WW) RADEON(0): [agp] AGP not available > (II) RADEON(0): [drm] removed 1 reserved context for kernel > (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0882000 at > 0x48267000 > (WW) RADEON(0): DRI forced on with virtual screen of greater than > 2048. > > (II) RADEON(0): Direct rendering disabled > > $ lsmod: > > radeon122488 0 > emu10k191300 0 > sound 87464 1 emu10k1 > soundcore 9664 2 emu10k1,sound > ac97_codec 19264 1 emu10k1 > eepro100 30508 0 > mii 5344 1 eepro100 > ipt_state 1952 6 > ip_conntrack 45888 1 ipt_state > iptable_filter 2880 1 > ip_tables 22192 2 ipt_state,iptable_filter > ide_scsi 15812 0 > agpgart33292 0 > nls_iso8859_1 4128 1 > nls_cp437 5792 1 > vfat 16416 1 > fat47136 1 vfat > > agpgart *is* loaded (though unused). > > $ dmesg | grep agpgart > Linux agpgart interface v0.100 (c) Dave Jones > > Is this definately an AGP issue that I should e-mail Dave Jones > about? > > Adam > > > > > --- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys > admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > -- > ___ > Dri-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dri-develceforge.net > https://lists.sourceforge.net/lists/listinfo/dri-devel __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] 2.6.0 problems.
Adam K Kirchhoff wrote: So I decided to give 2.6.0 a shot this morning :-) My Radeon 8500 (which previous worked with 2.4.22) refuses to enable direct rendering: (WW) RADEON(0): [agp] AGP not available (II) RADEON(0): [drm] removed 1 reserved context for kernel (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0882000 at 0x48267000 (WW) RADEON(0): DRI forced on with virtual screen of greater than 2048. (II) RADEON(0): Direct rendering disabled $ lsmod: radeon122488 0 emu10k191300 0 sound 87464 1 emu10k1 soundcore 9664 2 emu10k1,sound ac97_codec 19264 1 emu10k1 eepro100 30508 0 mii 5344 1 eepro100 ipt_state 1952 6 ip_conntrack 45888 1 ipt_state iptable_filter 2880 1 ip_tables 22192 2 ipt_state,iptable_filter ide_scsi 15812 0 agpgart33292 0 nls_iso8859_1 4128 1 nls_cp437 5792 1 vfat 16416 1 fat47136 1 vfat agpgart *is* loaded (though unused). $ dmesg | grep agpgart Linux agpgart interface v0.100 (c) Dave Jones Is this definately an AGP issue that I should e-mail Dave Jones about? You don't seem to have loaded the specific agpgart module for your chipset, i.e. intel-agp or via-agp which is needed now. Roland --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] 2.6.0 problems.
On Thu, 2003-12-18 at 15:12, Adam K Kirchhoff wrote: > > (WW) RADEON(0): [agp] AGP not available > (II) RADEON(0): [drm] removed 1 reserved context for kernel > (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0882000 at 0x48267000 > (WW) RADEON(0): DRI forced on with virtual screen of greater than 2048. > > (II) RADEON(0): Direct rendering disabled [...] > agpgart *is* loaded (though unused). Not the chipset specific AGP module though, which is needed now. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Software libre enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] 2.6.0 problems.
Wow. Thanks for all those quick and helpful reponses :-) Adam --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] [Announce] Savage 3D driver in CVS
On Thu, 18 Dec 2003 10:40:55 -0300 Rafael Maximo <[EMAIL PROTECTED]> wrote: > Felix, > > I tested your driver on my savage4 and i couldn't make the 3D > driver work (i changed the code to enable direct render on savage4), the > Xfree86 just can't find /dev/dri/cardX and i loaded agpgart and savage > modules without warnings but it just doesn't create the device, i checked > /dev/dri and it was empty. The device node is created by XFree86 when it looks for the DRM. Make sure that the directory /dev/dri exists and that the Xserver has permission to create new device nodes in it. The Xserver runs as root, so that should not be a problem, but I vaguely remember a report about /dev/dri directory permission problems. One more thing, there is another list of PCI IDs in xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/savage.h. You may have to add the savage4 PCI ID there. > > I'm still using kernel 2.4.21 and i will upgrade to 2.4.23 today It worked for me with 2.4.21-rc1. I don't think the kernel version matters. > but i don't know if this is the problem, I also tried running on xfree86 > 4.3.0 and with the binary on Alan's page (http://www.xfree86.org/~alanh/) > but no change no matter if i'm run with root or normal user. > > Any help? beside the 3D problem, my screen is corrupted when my > XFree86 starts, the same problem i posted before. Does the workaround 'Option "UseBios" "no"' help? > > bye. Hmm, from the feedback I got so far it seems like there will be more work required to get the Xserver side going before people can start testing the 3D driver. :-/ Felix __\|/_____ ___ - Felix ___\_e -_/___/ __\___/ __\_ You can do anything, Kühling (_\Ä// /_/ /) just not everything [EMAIL PROTECTED] \___/ \___/ Uat the same time. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Side band Address control
Hi There, Is it possible to disable the side address mechanism of Radeon 7000 by using command register(offset CAP_PTR +8) bit SBA_ENABLE? and how? SBA_ENABLE is read/writable. I'm not even able to turn it off without X is running. Thanks in advance, --Craig __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] [Announce] Savage 3D driver in CVS
At 12:38 PM 18/12/2003, Felix Kühling wrote:
The device node is created by XFree86 when it looks for the DRM. Make
sure that the directory /dev/dri exists and that the Xserver has
permission to create new device nodes in it. The Xserver runs as root,
so that should not be a problem, but I vaguely remember a report about
/dev/dri directory permission problems.
One more thing, there is another list of PCI IDs in
xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/savage.h. You
may have to add the savage4 PCI ID there.
Yes, I just changed savage.h and it worked just fine, added this line:
{0x533, 0x8a22, 0, "Savage4"}
Where 0x8a22 is my chipID. After that glxinfo reported that direct render
was working but i ran glxgears and i couldn't see anything, but it also
reported about 500 FPS, i could only see some white and black colors on
glxgears window.
>
> Any help? beside the 3D problem, my screen is corrupted when my
> XFree86 starts, the same problem i posted before.
Does the workaround 'Option "UseBios" "no"' help?
"UserBios" option didn't help, but i tried 'Option "DisableTile" "On"' and
worked just fine.
Hmm, from the feedback I got so far it seems like there will be more
work required to get the Xserver side going before people can start
testing the 3D driver. :-/
Felix
__\|/_____ ___ -
Felix ___\_e -_/___/ __\___/ __\_ You can do anything,
Kühling (_\Ä// /_/ /) just not everything
[EMAIL PROTECTED] \___/ \___/ Uat the same time.
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Rafael Máximo
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] [Announce] Savage 3D driver in CVS
On Thu, 18 Dec 2003 14:30:21 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:
> At 12:38 PM 18/12/2003, Felix Kühling wrote:
>
> >The device node is created by XFree86 when it looks for the DRM. Make
> >sure that the directory /dev/dri exists and that the Xserver has
> >permission to create new device nodes in it. The Xserver runs as root,
> >so that should not be a problem, but I vaguely remember a report about
> >/dev/dri directory permission problems.
> >
> >One more thing, there is another list of PCI IDs in
> >xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/savage.h. You
> >may have to add the savage4 PCI ID there.
>
> Yes, I just changed savage.h and it worked just fine, added this line:
>
> {0x533, 0x8a22, 0, "Savage4"}
Cool. I'm going to commit this soon.
>
> Where 0x8a22 is my chipID. After that glxinfo reported that direct render
> was working but i ran glxgears and i couldn't see anything, but it also
> reported about 500 FPS, i could only see some white and black colors on
> glxgears window.
Take a look at
xc/programs/Xserver/hw/xfree86/drivers/savage/savage_bci.h. There are
conditionals
#if SAVAGE4
...
#endif
Try defining
#define SAVAGE4 1
just before and recompile/reinstall the 2D driver. It looks like this
affects enabling of the BCI which is used to transfer some 3D commands
and the tiling which was broken for you. If this works, we'll have to
find a way to choose the correct values at run-time rather than
compile-time.
Felix
>
>
>
> > >
> > > Any help? beside the 3D problem, my screen is corrupted when my
> > > XFree86 starts, the same problem i posted before.
> >
> >Does the workaround 'Option "UseBios" "no"' help?
> >
>
> "UserBios" option didn't help, but i tried 'Option "DisableTile" "On"' and
> worked just fine.
>
>
> >Hmm, from the feedback I got so far it seems like there will be more
> >work required to get the Xserver side going before people can start
> >testing the 3D driver. :-/
> >
> >Felix
[snip]
> Rafael Máximo
__\|/_____ ___ -
Felix ___\_e -_/___/ __\___/ __\_ You can do anything,
Kühling (_\Ä// /_/ /) just not everything
[EMAIL PROTECTED] \___/ \___/ Uat the same time.
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] s3tc for r200, radeon, mesa
Since I'm not a lawyer, I'm not going to comment on any of the IP
legality of this patch. I am in no way offering any form of legal
advice. I do have a comment about the correctness of it that may also
apply to similar future (i.e., FXT1) patches.
Roland Scheidegger wrote:
Index: texcompress.c
===
RCS file: /cvsroot/mesa3d/Mesa-newtree/src/mesa/main/texcompress.c,v
retrieving revision 1.9
diff -u -r1.9 texcompress.c
--- texcompress.c 21 Nov 2003 09:56:50 - 1.9
+++ texcompress.c 18 Dec 2003 00:54:43 -
@@ -59,6 +59,9 @@
}
}
if (ctx->Extensions.EXT_texture_compression_s3tc) {
+/* quick hack. don't announce s3tc formats, hopefully noone then will try to
+compress textures despite having the s3tc extension */
+#if !MESA_S3TC
if (formats) {
formats[n++] = GL_COMPRESSED_RGB_S3TC_DXT1_EXT;
/* Skip this one because it has a restriction (all transparent
@@ -72,6 +75,7 @@
else {
n += 3;
}
+#endif
}
if (ctx->Extensions.S3_s3tc) {
if (formats) {
This is wrong, and may break valid applications. The supported
compressed formats should be listed no matter what. However, if the
requested internal format is compressed and the type does not match, the
driver is free to ignore the requested internal format. Technically
speaking, if ARB_texture_compression is supported, applications don't
need to check for other extensions. They only need to query
GL_COMPRESSED_TEXTURE_FORMATS_ARB and choose an available format that
they like.
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] s3tc for r200, radeon, mesa
Ian Romanick wrote:
Since I'm not a lawyer, I'm not going to comment on any of the IP
legality of this patch. I am in no way offering any form of legal
advice. I do have a comment about the correctness of it that may also
apply to similar future (i.e., FXT1) patches.
Roland Scheidegger wrote:
Index: texcompress.c
===
RCS file: /cvsroot/mesa3d/Mesa-newtree/src/mesa/main/texcompress.c,v
retrieving revision 1.9
diff -u -r1.9 texcompress.c
--- texcompress.c21 Nov 2003 09:56:50 -1.9
+++ texcompress.c18 Dec 2003 00:54:43 -
@@ -59,6 +59,9 @@
}
}
if (ctx->Extensions.EXT_texture_compression_s3tc) {
+ /* quick hack. don't announce s3tc formats, hopefully
noone then will try to
+ compress textures despite having the s3tc extension */
+#if !MESA_S3TC
if (formats) {
formats[n++] = GL_COMPRESSED_RGB_S3TC_DXT1_EXT;
/* Skip this one because it has a restriction (all
transparent
@@ -72,6 +75,7 @@
else {
n += 3;
}
+#endif
}
if (ctx->Extensions.S3_s3tc) {
if (formats) {
This is wrong, and may break valid applications. The supported
compressed formats should be listed no matter what.
Ok, I'll drop that. It was really just a crazy idea, though I've figured
out it won't do any good anyways (apps like QuakeIII will always request
a specific format if it's listed or not, the only reason QuakeIII still
works when compressed textures are enabled is it only checks for the
obsolete and somewhat undocumented s3_s3tc extension).
However, if the
requested internal format is compressed and the type does not match, the
driver is free to ignore the requested internal format. Technically
speaking, if ARB_texture_compression is supported, applications don't
need to check for other extensions. They only need to query
GL_COMPRESSED_TEXTURE_FORMATS_ARB and choose an available format that
they like.
So if I understand correctly, it is sufficient to just check if the
format and internalFormat in the xxxChooseTextureFormat function match
and use an uncompressed type if they don't? That's nice, it would even
make QuakeIII (of course only if the S3_S3tc extension is enabled) work
with "compressed" textures ;-). Thinking about it, this probably could
also be used to have compressed textures support for chips which don't
support it in hardware, so you could use the higher quality textures for
instance in nwn (though there might be a lot of texture swapping of
course, so probably not that useful).
Roland
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] s3tc for r200, radeon, mesa
Roland Scheidegger wrote: Ian Romanick wrote: This is wrong, and may break valid applications. The supported compressed formats should be listed no matter what. Ok, I'll drop that. It was really just a crazy idea, though I've figured out it won't do any good anyways (apps like QuakeIII will always request a specific format if it's listed or not, the only reason QuakeIII still works when compressed textures are enabled is it only checks for the obsolete and somewhat undocumented s3_s3tc extension). That's true. I think RtCW and Enemy Territory check for the newer extension string. In practice, apps with do one or the other, but usually not both. That is, they will either check the extension string or check GL_COMPRESSED_TEXTURE_FORMATS_ARB. In anycase, GL_S3_s3tc is deader than SGIS_multitexture, so I wouldn't worry about it. However, if the requested internal format is compressed and the type does not match, the driver is free to ignore the requested internal format. Technically speaking, if ARB_texture_compression is supported, applications don't need to check for other extensions. They only need to query GL_COMPRESSED_TEXTURE_FORMATS_ARB and choose an available format that they like. So if I understand correctly, it is sufficient to just check if the format and internalFormat in the xxxChooseTextureFormat function match and use an uncompressed type if they don't? That's nice, it would even make QuakeIII (of course only if the S3_S3tc extension is enabled) work with "compressed" textures ;-). Thinking about it, this probably could also be used to have compressed textures support for chips which don't support it in hardware, so you could use the higher quality textures for instance in nwn (though there might be a lot of texture swapping of course, so probably not that useful). That has *always* been the case with glTexImage. The internalFormat is merely a "suggestion." The driver is technically free to do whatever it wants as long as the base format (i.e., GL_RGB, GL_RGBA, etc.) of the requested internalFormat and the actual internalFormat match. Check the "issues" section of the GL_ARB_texture_compression spec. Under the question #10, it says that apps can call "GetTexLevelParameteriv with a of TEXTURE_COMPRESSED_ARB to determine if the GL was able to store the image in compressed form." The app can the call glGetTexLevelParameteriv with a of TEXTURE_INTERNAL_FORMAT to determine the exact format. This means that an app could do something like: glTexImage2D( GL_TEXTURE_2D, 0, GL_COMPRESSED_RGBA_S3TC_DXT1_EXT, 1024, 1024, 0, GL_RGBA, GL_UNSIGNED_BYTE, data ); But, calling glGetTexLevelParameteriv with a of TEXTURE_INTERNAL_FORMAT could return GL_COMPRESSED_RGBA_FXT1_3DFX or GL_RGBA8 or GL_RGBA or anything that has a base format of GL_RGBA. The spec gives driver writers a LOT of flexability to do something smart. ;) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] [Bug 967] fix missing symbol xf86ReadMmio32 for alpha platforms
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=967 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-12-18 16:36 --- I've just posted an alternate (untested) patch to the xfree86 list. I'll commit it so that it can be tested in 4.4RC2. There'll still be time to fix it after that if problems remain. -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] [Bug 716] GLX applications/commands very slow on ATI rage128
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=716 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-12-18 16:55 --- close for now -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
