[PATCH] Fix gcc 4 compilation in DRM
Fix gcc 4 compilation in DRM. Signed-off-by: Andi Kleen <[EMAIL PROTECTED]> Index: linux/drivers/char/drm/drmP.h === --- linux.orig/drivers/char/drm/drmP.h 2005-01-04 18:48:41.%N +0100 +++ linux/drivers/char/drm/drmP.h 2005-01-09 18:11:45.%N +0100 @@ -962,7 +962,6 @@ extern drm_minor_t*drm_minors; extern struct class_simple *drm_class; extern struct proc_dir_entry *drm_proc_root; -extern struct file_operations drm_stub_fops; /* Proc support (drm_proc.h) */ extern intdrm_proc_init(drm_device_t *dev, --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] Compilation problems.
r200_context.h:98:1: warning: this is the location of the previous definition r300_ioctl.c: In function `r300ClearBuffer': r300_ioctl.c:67: error: `drm_r300_cmd_header_t' undeclared (first use in this function) ^^ Know what I'm doing wrong? There are instructions in the readme about replacing regular Mesa drm with a link to the one from r300_driver - perhaps you did not follow them exactly ? The defintion of drm_r300_cmd_header_t is picked up from there and is not present in regular Mesa drm. best Vladimir Dergachev Adam --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[R300] Compilation problems.
I've seen so much activity on the r300_driver recently, I thought it'd be good time to test it out on my 9800 and give as much feedback as possible. Unfortunately, I'm not even able to get it to compile. I think I've followed the instructions correctly. I actually copied the r300_driver/r300 directory into the Mesa source tree (rather than linking it) and added the r300 driver to the linux-dri config file. I've set DRM_SOURCE_PATH to the correct directory. This is the error I get: make[6]: Entering directory `/home/adamk/saved/source/Mesa/src/mesa/drivers/dri/r300' gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver -I../../../../../../drm/shared -I../../../../../../drm/ linux -I../../../../../include -I../../../../../include/GL/internal -I../../../../../src/mesa -I../../../../../src/mesa/ main -I../../../../../src/mesa/glapi -I../../../../../src/mesa/math -I../../../../../src/mesa/transform -I../../../../.. /src/mesa/shader -I../../../../../src/mesa/swrast -I../../../../../src/mesa/swrast_setup -I../dri_client -I../dri_client /imports -Wall -O -g -std=c99 -fPIC -ffast-math -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DDRI_NEW_INTERFACE_ONLY -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DCOMPILE_R300 -DGLX_DIRECT_RENDERING -D_P OSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DDRI_NEW_INTERFACE_ONLY -DPTHREADS -DU SE_EXTERNAL_DXTN_LIB=1 -DCOMPILE_R300 -DGLX_DIRECT_RENDERING r300_ioctl.c -o r300_ioctl.o In file included from r300_ioctl.c:47: r300_context.h:58: warning: redefinition of `uint32_t' /usr/include/stdint.h:52: warning: `uint32_t' previously declared here r300_context.h:59: warning: redefinition of `uint8_t' /usr/include/stdint.h:49: warning: `uint8_t' previously declared here In file included from r300_ioctl.c:47: r300_context.h:124:1: warning: "TEX_ALL" redefined In file included from r200_ioctl.h:44, from radeon_lock.h:38, from r300_context.h:54, from r300_ioctl.c:47: r200_context.h:98:1: warning: this is the location of the previous definition r300_ioctl.c: In function `r300ClearBuffer': r300_ioctl.c:67: error: `drm_r300_cmd_header_t' undeclared (first use in this function) r300_ioctl.c:67: error: (Each undeclared identifier is reported only once r300_ioctl.c:67: error: for each function it appears in.) r300_ioctl.c:67: error: `cmd' undeclared (first use in this function) r300_ioctl.c:85: error: parse error before ')' token r300_ioctl.c:89: error: parse error before ')' token r300_ioctl.c:141: error: parse error before ')' token r300_ioctl.c:168: error: parse error before ')' token r300_ioctl.c:169: error: parse error before ')' token r300_ioctl.c:170: error: parse error before ')' token r300_ioctl.c:171: error: parse error before ')' token r300_ioctl.c:189: error: parse error before ')' token r300_ioctl.c:226: error: parse error before ')' token r300_ioctl.c:227: error: `R300_CMD_PACKET3' undeclared (first use in this function) r300_ioctl.c:228: error: `R300_CMD_PACKET3_CLEAR' undeclared (first use in this function) r300_ioctl.c: In function `r300RefillCurrentDmaRegion': r300_ioctl.c:358: warning: passing arg 1 of `r200FlushCmdBufLocked' from incompatible pointer type r300_ioctl.c:373: warning: assignment from incompatible pointer type r300_ioctl.c:377: warning: assignment from incompatible pointer type make[6]: *** [r300_ioctl.o] Error 1 Know what I'm doing wrong? Adam --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drmAddMap failed
drm driver, to keep it simple and prevent interference with X. No my Xserver fail to initialize DRI, it fails with drmAddMap. it says: [drm] drmAddMap failed And then tells there is no dri. I wanted to test r300 driver. I have no more logs of that has i crashed my system. Anyway, i first thought that there was somethings wrong with r300, but i may have find the origin of the issue and it is not related to drm. Some PPC (G5) stuff with agp. I need to do more test. By the way, is there any flags that tell drm to verbose a bit on what it does ? Yes, but I don't remember them offhand. Try to grep for EXPORT_SYMBOL - the one with debug in the name is likely what you need. best Vladimir Dergachev best, Jerome Glisse --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drmAddMap failed
Vladimir Dergachev wrote: On Sun, 9 Jan 2005, Jerome Glisse wrote: Hello, I wanted to test a bit the r300 drv on g5 but i get a drmAddMap failed. I see a issue related to this in the archive (september 2004). I assume it's have been fixed. My drm version is the one from r300 (linux-core) but i guess there little difference between this trunk and the official one. Thus anyone got an idea from where this may came from ? May it came from the agp driver ? (forcing to pcimode disable dri here) Just to get the obvious out of the way - you are running an Xserver that successfully initialized DRI, right ? r300_demo does not initialize drm driver, to keep it simple and prevent interference with X. No my Xserver fail to initialize DRI, it fails with drmAddMap. it says: [drm] drmAddMap failed And then tells there is no dri. I wanted to test r300 driver. I have no more logs of that has i crashed my system. Anyway, i first thought that there was somethings wrong with r300, but i may have find the origin of the issue and it is not related to drm. Some PPC (G5) stuff with agp. I need to do more test. By the way, is there any flags that tell drm to verbose a bit on what it does ? best, Jerome Glisse --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
drm memory allocator
Hi, In the drm, I found that the memory allocator can handle both gart (RADEON_MEM_REGION_GART) and fb (RADEON_MEM_REGION_FB) memory. However, the second type is never used. Is there a reason for that ? Stephane --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM Build failure: 4 level page tables != 2.6.10
On Saturday, January 08, 2005 4:13 pm, Dave Airlie wrote: > > The 4 level code is already in Linus bk which also has the 2.6.10 > > kernel version. I don't see a good fix for this. I'll complain on > > lkml. > > I usually fix this by not supporting Linus trees in CVS until they are > released :-), also why I don't put -mm patches in either it's too much > hassle, really Linus should up the version number after releasing it Yeah, he really should for lots of reasons. But OTOH, how many people use DRM CVS vs. what's upstream in the kernel? Do distros generally ship the CVS version or whatever is in their kernel when they freeze on a particular release? If the latter, then maybe it makes sense to tie Linux DRM development more closely to the Linux kernel release process? E.g. have a BK or CVS tree that akpm could add to -mm for regular testing and maybe get rid of compatibility with older kernels in the latest DRM CVS? Jesse --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drmAddMap failed
On Sun, 9 Jan 2005, Jerome Glisse wrote: Hello, I wanted to test a bit the r300 drv on g5 but i get a drmAddMap failed. I see a issue related to this in the archive (september 2004). I assume it's have been fixed. My drm version is the one from r300 (linux-core) but i guess there little difference between this trunk and the official one. Thus anyone got an idea from where this may came from ? May it came from the agp driver ? (forcing to pcimode disable dri here) Just to get the obvious out of the way - you are running an Xserver that successfully initialized DRI, right ? r300_demo does not initialize drm driver, to keep it simple and prevent interference with X. best Vladimir Dergachev best, Jerome Glisse --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
drmAddMap failed
Hello, I wanted to test a bit the r300 drv on g5 but i get a drmAddMap failed. I see a issue related to this in the archive (september 2004). I assume it's have been fixed. My drm version is the one from r300 (linux-core) but i guess there little difference between this trunk and the official one. Thus anyone got an idea from where this may came from ? May it came from the agp driver ? (forcing to pcimode disable dri here) best, Jerome Glisse --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: r200 and ATI_fragment_shader
Philipp Klaus Krause wrote: Dave Airlie schrieb: Just to update, I've looked at the fragment shader stuff and the documentation I have isn't enough to implement the spec, we only have access to the second stage registers (PP_CNTL - states second or only pass registers) Is it enough to implement GL_ARB_texture_crossbar? Definitively. No additional information at all should be needed to implement it. The reason it's not implemented is the that the r200 does not have any "spare" register in the fragment pipeline. It has only 6, which can be used both as inputs and outputs. But you need to make sure you don't overwrite a register value which you got from texture sampling if you might need it again later on, which would easily happen with a trivial implementation of crossbar. It would be easy to add with the default enabled 4 or 2 tmus, but not quite so trivial for all 6. I think Ian was working on this some time ago. Roland --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: New Debian packages built from Xorg
> In <[EMAIL PROTECTED]> > John Lightsey <[EMAIL PROTECTED]> wrote: >> I'm still wondering where /usr/X11R6/lib/modules/codeconv/ went though. >> Is there a define to build these libraries that isn't in the sample >> host.def for Xorg? Are they necessary for languages other than English? Codeconv modules are gone. They are only used by X-TT TruetType font rendering backend. Most X-TT functions are merged into FreeType font rendering backend now, and X-TT related codes are dropped from tree. FreeType backend uses encoding files (under /usr/X11R6/lib/X11/fonts/encoding) for font encoding conversion. So, we are not needed codeconv modules any more. -- ISHIKAWA Mutsumi <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: New Savage DRM preview
Am Samstag, den 08.01.2005, 20:54 -0500 schrieb Alex Deucher: > On Sat, 8 Jan 2005 21:18:24 + (UTC), Martin Lucina <[EMAIL PROTECTED]> > wrote: > > Hi Felix, > > > > > [... new Savage DRM ...] > > > > I just tried this code via John's experimental Xorg packages at > > www.nixnuts.net. > > 400fps in glxgears, which is cute -- I never thought this laptops (Toshiba > > Portege 7220cte) video card would see OpenGL. :-) > > > > Neverball also works fine and is quite playable at 1024x768/16bpp, with > > reflection turned off. Also, the Cube 3D FPS engine > > (http://wouter.fov120.com/cube/) appears to work quite well. [1] > > > > Haven't tried much else... but it's very impressive. Thanks a lot for the > > hard > > work. Call me up for a beer if you are around Slovakia sometime. > > > > I had to set ShadowStatus to true as you describe, otherwise I would get > > lockups > > when (e.g.) trying to move a running glxgears window. > > perhaps we should make shadowstatus default to on. With DRI disabled the shadow status page is in frame buffer memory. On my ProSavageDDR that leads to a chip lockup. Therefore I'd prefer to enable ShadowStatus by default only if DRI is enabled or print a Warning/Error message to the log if DRI is enabled without shadow status. > > Alex > -- | Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: r200 and ATI_fragment_shader
Dave Airlie schrieb: Just to update, I've looked at the fragment shader stuff and the documentation I have isn't enough to implement the spec, we only have access to the second stage registers (PP_CNTL - states second or only pass registers) Is it enough to implement GL_ARB_texture_crossbar? Philipp --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
r200 and ATI_fragment_shader
Just to update, I've looked at the fragment shader stuff and the documentation I have isn't enough to implement the spec, we only have access to the second stage registers (PP_CNTL - states second or only pass registers) I'm going to use the r300 stuff to start reverse engineering the fglrx stuff, Vladimir can you add airlied to the r300 project on sf.net? I've got some updates for the pretty printer... for fragment shader packets... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
