mach64 driver and X includes

2004-06-06 Thread Jon Smirl
The mach64 driver includes Xarch.h. In the mesa-solo model it can't do this since there is no X around. Is there some other way to achive the correct byte ordering without relying on X include files? #include "X11/Xarch.h" #if X_BYTE_ORDER == X_LITTLE_ENDIAN = Jon Smirl [EMAIL PROTECTED]

Re: mach64 driver and X includes

2004-06-06 Thread Dave Airlie
I've changed it to include /usr/include/endian.h rather than Xarch, it should work... but I can't test it until I get back to my laptop... Dave. On Sun, 6 Jun 2004, Jon Smirl wrote: > The mach64 driver includes Xarch.h. In the mesa-solo model it can't do this > since there is no X around. Is th

Re: mach64 driver and X includes

2004-06-06 Thread Michel Dänzer
On Mon, 2004-06-07 at 00:32 +0100, Dave Airlie wrote: > I've changed it to include /usr/include/endian.h rather than Xarch, it > should work... I'm afraid that's glibc specific. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://s

Re: mach64 driver and X includes

2004-06-06 Thread Dave Airlie
> > I'm afraid that's glibc specific. If I use on FreeBSD can I do the same thing? it'll look messy but to avoid the X includes we should do it .. #ifdef __linux__ #include #else #include #define __BYTE_ORDER BYTE_ORDER #define __LITTLE_ENDIAN LITTLE_ENDIAN #define __BIG_ENDIAN BIG_ENDIAN #en

Re: mach64 driver and X includes

2004-06-06 Thread Mike Mestnik
How about a copy/rename of teh X include and then s/X/dri/ it till it's good to go. This would make (re)porting a no task task. --- Dave Airlie <[EMAIL PROTECTED]> wrote: > > > > I'm afraid that's glibc specific. > > If I use on FreeBSD can I do the same thing? > > it'll look messy but to avoi

Re: mach64 driver and X includes

2004-06-06 Thread Jon Smirl
I see use of MESA_BIG_ENDIAN in the other drivers, could you use that instead? mach64 is the only driver using the X headers. = Jon Smirl [EMAIL PROTECTED] __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://me

Re: mach64 driver and X includes

2004-06-06 Thread Michel Dänzer
On Mon, 2004-06-07 at 00:52 +0100, Dave Airlie wrote: > > > > I'm afraid that's glibc specific. > > If I use on FreeBSD can I do the same thing? > > it'll look messy but to avoid the X includes we should do it .. > > #ifdef __linux__ > #include > #else > #include > #define __BYTE_ORDER BYTE_O

Re: mach64 driver and X includes

2004-06-06 Thread Jon Smirl
CPU_TO_LE32() etc seems to already be defined in mesa/main/glheader.h. Should mach64 be using that version? = Jon Smirl [EMAIL PROTECTED] __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/

Re: mach64 driver and X includes

2004-06-06 Thread Dave Airlie
okay I'll have a go and making the m64 use the Mesa stuff tonight if I can drag myself away from nwn :-) Dave. On Sun, 6 Jun 2004, Jon Smirl wrote: > CPU_TO_LE32() etc seems to already be defined in mesa/main/glheader.h. Should > mach64 be using that version? > > = > Jon Smirl > [EMAIL PROT

Re: mach64 driver and X includes

2004-06-06 Thread Jon Smirl
Can you fix the 500 compiler warnings while you're in there? --- Dave Airlie <[EMAIL PROTECTED]> wrote: > > okay I'll have a go and making the m64 use the Mesa stuff tonight if I can > drag myself away from nwn :-) > > Dave. > > On Sun, 6 Jun 2004, Jon Smirl wrote: > > > CPU_TO_LE32() etc seem

Re: mach64 driver and X includes

2004-06-06 Thread Dave Airlie
> Can you fix the 500 compiler warnings while you're in there? I actually have the fixes for all those warnings in a tree already, however they defo require testing as they are to do with building the vertex info for sending to the card.. Dave. > > --- Dave Airlie <[EMAIL PROTECTED]> wrote: >

Re: mach64 driver and X includes

2004-06-07 Thread Dave Airlie
> Can you fix the 500 compiler warnings while you're in there? okay it's finally done there shouldn't be all those warnings, and I've tested it on my laptop and it seems to still work, I also fixed the version check code that was recently put in .. wouldn't mind someone on a big endian testing i