Current DRM on FreeBSD

2006-01-25 Thread Adam K Kirchhoff


Just thought I'd point out that DRM has stopped compiling on FreeBSD again:

=== radeon (all)
Warning: Object directory not changed from original 
/home/adamk/saved/source/drm/bsd-core/radeon
cc -O2 -fno-strict-aliasing -pipe  -Werror -D_KERNEL -DKLD_MODULE 
-nostdinc -I-  -I. -I.. -I. -I@ -I@/contrib/altq -finline-limit=8000 
-fno-common  -mno-align-long-strings -mpreferred-stack-boundary=2  
-mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -c 
/home/adamk/saved/source/drm/bsd-core/radeon/../radeon_state.c
/home/adamk/saved/source/drm/bsd-core/radeon/../radeon_state.c: In 
function `radeon_cp_cmdbuf':
/home/adamk/saved/source/drm/bsd-core/radeon/../radeon_state.c:2750: 
error: incompatible types in assignment

*** Error code 1

Stop in /home/adamk/saved/source/drm/bsd-core/radeon.
*** Error code 1

DRI, from Mesa CVS, still builds, but falls back to indirect rendering 
since it needs DRM 1.22.x to run.


Isn't it possible to only make newer functionality in the DRI drivers 
depend on newer DRM?  This way, users stuck with a particular version of 
the DRM still have functional DRI drivers, even if they are missing out 
on newer features of the driver?


Adam



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: Current DRM on FreeBSD

2006-01-25 Thread Dave Airlie
 DRI, from Mesa CVS, still builds, but falls back to indirect rendering since
 it needs DRM 1.22.x to run.

 Isn't it possible to only make newer functionality in the DRI drivers depend
 on newer DRM?  This way, users stuck with a particular version of the DRM
 still have functional DRI drivers, even if they are missing out on newer
 features of the driver?

For any other driver than r300 this is done, I don't want to do this for
r300 as it is an experimental driver, and having a lot of backwarrds
compat in the Mesa driver during development is only going to make it look
uglier for no real gain..

I guess it was my kcmdbuf changes that broke radeon on FreeBSD, they
shouldn't be that hard to fixup..

Dave.

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel