Re: [Dri-devel] 2D textures for video rendering
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 18 October 2001 14:50, Michael Zayats wrote: Do you know whether 2D textures might be used as a surface to draw video on? Is DMA path of memory - texture implemented in i810 driver? (4.1.0) what do you think of this path at all? well, look at mplayer i do patch vo_gl2 (video out gl version2), and there is a first draw vo_gl also. well - for either DRI + r128 i had no problems with that, nor with nvidia's glx. but some said there are .. BGR related problems .. well, just give it a try:http://mplayer.dev.hu/homepage/dload.html ... the same technique is used in xmame.xgl too ;-) sven - -- my concern about the current attack: http://www.jausoft.com/20010911-wtc/ mailto:[EMAIL PROTECTED] www : http://www.jausoft.com ; pgp: http://www.jausoft.com/gpg/ voice : +49-521-2399440 ; fax : +49-521-2399442 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7z9ZyHdOA30NoFAARArSuAKCCZOJKFjcScmKYOAvRZMCwh7Wi5gCghxqU HF0pPCjPxbLi5xno+Mstx7o= =rK4D -END PGP SIGNATURE- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] /usr/bin/ld: cannot find -lXau
Liam Wilks writes: Could anybody help me with this problem? DRI doesn't seem to want to compile from CVS. I am running Redhat 7.1, with kernel 2.4.5 patched for Win4Lin, and XFree86 4.10. I have an ATI Rage Mobility P/M Graphics Card, which is a Mach 64 based card. I downloaded the alpha patch for ATI Mach 64 today and patched the source tree. I relise that this patch is very early in development and DRI currently does not support Mach 64, however I believe this is not the problem. Below is the tail of the output from compiling DRI: make[5]: Leaving directory `/downloads/dri/DRI-CVS/build/xc/programs/Xserver/hw/xfree86' gcc -o XFree86 -O2 -ansi -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -pipe -g -L../../exports/lib -L/usr/X11R6-DRI/lib ../../programs/Xserver/hw/xfree86/common/xf86Init.o ../../programs/Xserver/hw/xfree86/common/xf86IniExt.o ../../programs/Xserver/hw/xfree86/common/libxf86.a ../../programs/Xserver/hw/xfree86/parser/libxf86config.a ../../programs/Xserver/hw/xfree86/os-support/libxf86_os.a ../../programs/Xserver/hw/xfree86/loader/libloader.a ../../programs/Xserver/hw/xfree86/common/libxf86.a miext/shadow/libshadow.a dix/libdix.a os/libos.a -lXau -lXdmcp ../../lib/font/fontbase.o ../../lib/font/libfontbase.a Xext/libexts.a xkb/libxkb.a Xi/libxinput.a lbx/liblbx.a ../../lib/lbxutil/liblbxutil.a ../../programs/Xserver/hw/xfree86/common/libxf86.a Xext/libexts.a xkb/libxkb.a Xi/libxinput.a lbx/liblbx.a ../../lib/lbx! util/liblbxutil.a render/librender.a dix/libxpstubs.a mi/libmi.a Xext/libexts.a xkb/libxkb.a Xi/libxinput.a lbx/liblbx.a ../../lib/lbxutil/liblbxutil.a render/librender.a ../../programs/Xserver/hw/xfree86/os-support/libxf86_os.a ../../programs/Xserver/hw/xfree86/ddc/libddc.a -lz -lm -rdynamic -ldl -Wl,-rpath-link,../../exports/lib /usr/bin/ld: cannot find -lXau collect2: ld returned 1 exit status make[4]: *** [XFree86] Error 1 make[4]: Target `all' not remade because of errors. rm -f Xserver._man /lib/cpp -undef -traditional -D__filemansuffix__=5x -D__miscmansuffix__=7 -D__drivermansuffix__=4 -D__projectroot__=/usr/X11R6-DRI -D__xorgversion__='Release 6.5 X Version 11' -D__vendorversion__='Version 4.1.99.1 XFree86' Xserver.man | sed -e '/^# *[0-9][0-9]* *.*$/d' -e '/^XCOMM$/s//#/' -e '/^XCOMM[^a-zA-Z0-9_]/s/^XCOMM/#/' Xserver._man rm -f Xserver.1x.html Xserver.1x-html ../../config/util/rman -f HTML Xserver._man \ Xserver.1x-html mv -f Xserver.1x-html Xserver.1x.html macro in not recognized -- ignoring make[4]: Leaving directory `/downloads/dri/DRI-CVS/build/xc/programs/Xserver' make[3]: *** [all] Error 2 make[3]: Leaving directory `/downloads/dri/DRI-CVS/build/xc/programs' make[2]: *** [all] Error 2 make[2]: Leaving directory `/downloads/dri/DRI-CVS/build/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/downloads/dri/DRI-CVS/build/xc' make: *** [World] Error 2 It looks to me that the problem is it can't find libXau.a, however it seems to be there as far as I know. Any help would be appreciated thankyou. I think that you need a previous XFree installation in the /usr/X11R6-DRI, I suffered similar problems with some headers. Perhaps the fastest solution is copying the /usr/X11R6 to the /usr/X11R6-DRI directory to avoid this compilation problems. Then, the installation will overwrite the important stuff. BTW. I'm interested in any problems while applying the patch. Did it work correctly for you? I hope that this helps. Liam Wilks, SportingPulse.Com ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] /usr/bin/ld: cannot find -lXau
[EMAIL PROTECTED] wrote: /usr/bin/ld: cannot find -lXau [...] Perhaps the fastest solution is copying the /usr/X11R6 to the /usr/X11R6-DRI directory to avoid this compilation problems. Then, the installation will overwrite the important stuff. I'm currently trying to compile this, too - I'll try this ASAP. BTW. I'm interested in any problems while applying the patch. Did it work correctly for you? Yep, I do have another question though. Is it necessary to specify mach64 manually in xc/config/cf/host.def? If so, the patch should probably modify this file in that regard, too. Yours Malte #8-) ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] /usr/bin/ld: cannot find -lXau
On Fri, 19 Oct 2001, Malte Cornils wrote: Yep, I do have another question though. Is it necessary to specify mach64 manually in xc/config/cf/host.def? If so, the patch should probably modify this file in that regard, too. That's not necessary, the mach64 driver is part of the ati (2D) driver. -- Leif Delgass ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64: BusMastering test seems to work
On Fri, 19 Oct 2001 17:24, Leif Delgass wrote: Great work! I'll check this out soon. Once we get DMA working for the 3D operations, I guess the next task is to get the 2D acceleration routines synchronizing with the 3D ones so we can reenable XAA, right? Also, it looks as if the AGP setup has not been finished yet. At this point, atidri.c allocates 8M (hardcoded value, but the agpgart module tells me I have a 64M AGP aperture) and maps 2M of it for vertex buffers, but it never sets AGP_BASE or AGP_CNTL. There's currently no allocation of an AGP region for textures. I'm seeing problems with missing textures in the Quake 3 demo and some other GL apps. It's great to get past this hurdle, maybe we can get a new CVS branch going soon! Who would need cvs access? It's time this work got some support... Keith _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64: BusMastering test seems to work
Leif Delgass wrote: Great work! I'll check this out soon. Once we get DMA working for the 3D operations, I guess the next task is to get the 2D acceleration routines synchronizing with the 3D ones so we can reenable XAA, right? Also, it looks as if the AGP setup has not been finished yet. At this point, atidri.c allocates 8M (hardcoded value, but the agpgart module tells me I have a 64M AGP aperture) and maps 2M of it for vertex buffers, but it never sets AGP_BASE or AGP_CNTL. There's currently no allocation of an AGP region for textures. I'm seeing problems with missing textures in the Quake 3 demo and some other GL apps. Remember, the chip may only be able access 8 or 16MB of AGP memory. The docs should specify this somewhere -- the r128 could only access 32MB if I remember correctly... -- Gareth ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Mach64: Hard lock on vt switch
Just a warning, with the direct register writes enabled in mach64_dma_dispatch_clear (in mach64_state.c), switching to a virtual terminal and back to X causes my box to hang hard -- I can't ssh in and Alt-SysRq doesn't work. -- Leif Delgass ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64: BusMastering test seems to work
Hey, From what I can tell, it accesses 16mb. Aperature Base can be allocated anywhere in the shaded region and is aligned to a multiple of 16MB This comes from page 17. Congratulations on your work on the driver, and thanks. Carl Busjahn Gareth Hughes wrote: Leif Delgass wrote: Great work! I'll check this out soon. Once we get DMA working for the 3D operations, I guess the next task is to get the 2D acceleration routines synchronizing with the 3D ones so we can reenable XAA, right? Also, it looks as if the AGP setup has not been finished yet. At this point, atidri.c allocates 8M (hardcoded value, but the agpgart module tells me I have a 64M AGP aperture) and maps 2M of it for vertex buffers, but it never sets AGP_BASE or AGP_CNTL. There's currently no allocation of an AGP region for textures. I'm seeing problems with missing textures in the Quake 3 demo and some other GL apps. Remember, the chip may only be able access 8 or 16MB of AGP memory. The docs should specify this somewhere -- the r128 could only access 32MB if I remember correctly... -- Gareth ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
