That's debateable. In current kernels, if it's not defined you've more than likely built your kernel with i386 rather than i486 or later, because building for i486 or later automatically turns on CONFIG_X86_CMPXCHG. I understand that i386's don't have that instruction.
Maybe we need to put in our CVS something like... #ifndef cmpxchg #error "your kernel needs to be recompiled with CPU support for i486 and later" #endif Alan. On Thu, Oct 31, 2002 at 09:52:12PM +0000, José Fonseca wrote: > This user had troubles compiling the DRM from a snapshot due to missing > definition of cmpxchg. Here are the relevant bits of the log: > > cc -O2 -Wall -Wwrite-strings -Wpointer-arith -Wcast-align > -Wstrict-prototypes -Wnested-externs -Wpointer-arith -D__KERNEL__ > -DMODULE -fomit-frame-pointer -DCONFIG_AGP -DCONFIG_AGP_MODULE > -DCONFIG_DRM_SIS -DEXPORT_SYMTAB -I/lib/modules/2.4.18/build/include -c > radeon_drv.c -o radeon_drv.o > In file included from radeon_drv.c:48: > drm_lock.h: In function `radeon_lock_take': > drm_lock.h:57: warning: implicit declaration of function `cmpxchg' > ... > ld -r radeon_drv.o radeon_cp.o radeon_state.o radeon_mem.o radeon_irq.o > -o radeon.o > /usr/X11R6/lib > /lib/modules/2.4.18/kernel/drivers/char/drm/radeon.o: unresolved symbol > cmpxchg > /lib/modules/2.4.18/kernel/drivers/char/drm/radeon.o: insmod > /lib/modules/2.4.18/kernel/drivers/char/drm/radeon.o failed > > The snapshots don't define cmpxchg, but drivers/char/drm/drmP.h on the > RedHat kernel 2.4.18-17.8.0 defines it in case __HAVE_ARCH_CMPXCHG isn't > defined. Should we had this to CVS as well? > > Jos Fonseca > > ----- Forwarded message from Jos Fonseca <[EMAIL PROTECTED]> ----- > > Date: Thu, 31 Oct 2002 17:53:57 +0000 > From: Jos Fonseca <[EMAIL PROTECTED]> > Subject: Re: [Dri-users] Slack 8.1 Radeon 8500 64MB > To: Wojciech Banas <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > > Wojciech, > > On Thu, Oct 31, 2002 at 10:09:04AM -0600, Wojciech Banas wrote: > >I have a Radeon 8500 AGP 64MB video card and Slackware Linux 8.1 clean > >install. I'm trying to get DRI working with it. I have downloaded > >radeon-20021022-linux.i386.tar.bz2 and run the ./install.sh as root. Note: > >X-Window works ok before installing DRI. Also if I don't install DRI from > >dri.sourceforge.net /var/log/XFree86.0.log has a line saying: > >(WW) RADEON(0): Direct rendering not yet supported on Radeon 8500 > >Does this mean that the X/DRI that comes with Slackware 8.1 does not > >support DRI with Radeon 8500? i > > That's right. DRI support for Radeon 8500 is fairly recent and was not > included in XFree86 4.2.x. It will be included in the next release. > > >Has the radeon-20021022-linux.i386.tar.bz2 install.sh script been tested > >with Slackware 8.1??? > > Not necessarily. I've read your log and it seems that there may be some > compatability problems with the kernel shipped in Slackware 8.1. I'm > going to look it deeper. > > Another thing, the snapshot for Radeon 8500 is actually > r200-*-linux.i386.tar.bz2. > > >I'm not a programmer, I have tried to install DRI with X 4.x.x probably 20 > >times and failed. So I just gave up and started to use MS-Windows 2000. > >Now I'm trying DRI and Slackware again. For me to use Linux and DRI, the > >installation of DRI has to be as EASY as installing DirectX 8.1 on > >MS-Windows 2000. The install.sh script fails and gives an error message > >which I do not understand. As an end user I understand/respond to error > >messages that say something like "Sorry, you don't have the latest version > >of DirectX installed, you must install DirectX 8.1 to run your silly game." > > The binary snapshots and the 'install.sh' script is meant primarily for > advanced user (beta testers) to help testing the development. It is not > meant to end users as things can and do get broken sometimes. (And it's > not easy to predict what can fail and write nice error messages. On the > other hand, what MS representative would give you free support for > installing DirectX if you ran into problems?) > > Once the Radeon 8500 is released (XFree86 4.3.0), and Slackware includes > DRI will be as EASY as the rest of your distribution instalation... > > >Slackware is my favorite Linux distirbution, but if I can't get DRI > >installed, I will switch to RedHat. I think RedHat sets up DRI during > >installation..., if not I will just keep on using Windows 2000 and try > >this again in a few years. > > As said above, using RedHat will do no good as no Linux distribution > includes DRI support Radeon 8500. (NOTE: most have DRI support already, > just not for Radeon 8500). > > If you think you're better served with Windows 2000, then by all means > keep using it and don't waste our time. If on the other hand you want help > to > face this difficulty you've encountered you can count with our full > support. > > In any case, thanks for the error report. > > Jos Fonseca > > ----- End forwarded message ----- > __________________________________________________ > Do You Yahoo!? > Everything you'll ever need on one web page > from News and Sport to Email and Music Charts > http://uk.my.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by: Influence the future > of Java(TM) technology. Join the Java Community > Process(SM) (JCP(SM)) program now. > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en > _______________________________________________ > Dri-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dri-devel ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
