On 7/8/06, Jerome Glisse wrote:
> On 7/8/06, Frédéric L. W. Meunier wrote:
> > I was able to compile r300 from Mesa 6.5 but CVS after that and
> > until now returns:
> >
> > gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver
> > -I../../../../../include -I../../../../../include/GL/in
On 7/8/06, Jerome Glisse <[EMAIL PROTECTED]> wrote:
> On 7/8/06, Frédéric L. W. Meunier <[EMAIL PROTECTED]> wrote:
> > I was able to compile r300 from Mesa 6.5 but CVS after that and
> > until now returns:
> >
> > gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver
> > -I../../../../.
On 7/8/06, Frédéric L. W. Meunier <[EMAIL PROTECTED]> wrote:
> I was able to compile r300 from Mesa 6.5 but CVS after that and
> until now returns:
>
> gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver
> -I../../../../../include -I../../../../../include/GL/internal
> -I../../../../
On 7/8/06, Frédéric L. W. Meunier <[EMAIL PROTECTED]> wrote:
I was able to compile r300 from Mesa 6.5 but CVS after that and
until now returns:
gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver
-I../../../../../include -I../../../../../include/GL/internal
-I../../../../../src/me
I was able to compile r300 from Mesa 6.5 but CVS after that and
until now returns:
gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver
-I../../../../../include -I../../../../../include/GL/internal
-I../../../../../src/mesa -I../../../../../src/mesa/main
-I../../../../../src/mesa/g
Jerome Glisse wrote:
Do you have lastest Mesa checkout ? Maybe Michel
has applied the wrong patch to mesa cvs. I will check
this.
I've cvs-ed it this afternoon, but looking to "Re: [Fwd: Snapshot build
failed]" seems that michel will fix it soon.
--
Laera Dario
Undergraduate student at Computer S
On Sun, 13 Feb 2005 19:02:40 +0100, Dario Laera <[EMAIL PROTECTED]> wrote:
> Fionn Behrens wrote:
> --- Mesa/src/mesa/drivers/dri/radeon/server/radeon_macros.h 2005-02-12
> 21:37:07.0 +0100
> +++ Mesa.up/src/mesa/drivers/dri/radeon/server/radeon_macros.h 2005-02-13
> 17:24:40.28884
Fionn Behrens wrote:
Xorg and drm modules compiled fine but Mesa bails out:
radeon_screen.c: In function `radeonCreateScreen':
radeon_screen.c:519: error: `addr' undeclared (first use in this
function)
radeon_screen.c:519: error: (Each undeclared identifier is reported only
once
radeon_screen.c:519
Am Sonntag, den 13.02.2005, 11:28 -0500 schrieb Vladimir Dergachev:
> Which module is it ? You only need r300 and you can ignore compiling all
> others.
Sorry, here are some more lines.
radeon_screen.c: In function `radeonCreateScreen':
radeon_screen.c:519: error: `addr' undeclared (first use in
Which module is it ? You only need r300 and you can ignore compiling all
others.
best
Vladimir Dergachev
On Sun, 13 Feb 2005, Fionn Behrens wrote:
Xorg and drm modules compiled fine but Mesa bails out:
radeon_screen.c: In function `radeonCreateScreen':
radeon
Xorg and drm modules compiled fine but Mesa bails out:
radeon_screen.c: In function `radeonCreateScreen':
radeon_screen.c:519: error: `addr' undeclared (first use in this
function)
radeon_screen.c:519: error: (Each undeclared identifier is reported only
once
radeon_screen.c:519: error: for each f
On Fri, 4 Feb 2005, Jacob Gorm Hansen wrote:
Vladimir Dergachev wrote:
I am just getting the message (WW) RADEON(0): Direct Rendering not yet
supported on Radeon 9500 and newer cards.
This means you have old Xorg code. You need to compile new one from CVS.
Hmm, apparently the 'make install' had
Vladimir Dergachev wrote:
I am just getting the message (WW) RADEON(0): Direct Rendering not yet
supported on Radeon 9500 and newer cards.
This means you have old Xorg code. You need to compile new one from CVS.
Hmm, apparently the 'make install' had not nuked all of my old X11
binaries. Now it
On Fri, 4 Feb 2005, Jacob Gorm Hansen wrote:
Vladimir Dergachev wrote:
1. Get Xorg CVS, Get Mesa CVS Get r300_driver from CVS at r300.sf.net
2. Compile drm from r300.sf.net, insmod ./drm.ko ; insmod ./radeon.ko
check for no lockups
3. Compile and install Xorg CVS. Check that there are no lo
Vladimir Dergachev wrote:
1. Get Xorg CVS, Get Mesa CVS Get r300_driver from CVS at r300.sf.net
2. Compile drm from r300.sf.net, insmod ./drm.ko ; insmod ./radeon.ko
check for no lockups
3. Compile and install Xorg CVS. Check that there are no lockups
4. insmod drm modules as above, run Xor
On Fri, 4 Feb 2005, Fionn Behrens wrote:
Dear Jacob, dear everyone,
once you managed to get everything in place, would you mind to write
down what you did in a form like:
- Get xorg cvs via
# cvs command co
- cd into directory xy and edit Makefile z in some way
- ./configure & make
- Get some oth
Dear Jacob, dear everyone,
once you managed to get everything in place, would you mind to write
down what you did in a form like:
- Get xorg cvs via
# cvs command co
- cd into directory xy and edit Makefile z in some way
- ./configure & make
- Get some other cvs tree via this command:
# cvs
> Well, when I went to load the kernel module I compiled from the
> /drm directory, I get this:
>
> radeon: Unknown symbol drm_open
> radeon: Unknown symbol drm_fasync
> So what am I doing wrong this time? :-)
>
insmod drm.ko first..
Dave.
>
>
FYI,
Apparently, even though the DRM_SOURCE_PATH variable is set, it's
not getting checked. If I copy the r300_driver/drm directory to the
same directory as the Mesa source tree, the r300_dri.so library gets
built fine.
Now to test it :-)
Adam
Well, when I went to load the kernel modu
Adam K Kirchhoff wrote:
Jerome Glisse wrote:
Adam K Kirchhoff wrote:
Vladimir Dergachev wrote:
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 f
Adam K Kirchhoff wrote:
Vladimir Dergachev wrote:
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)
^^
Jerome Glisse wrote:
Adam K Kirchhoff wrote:
Vladimir Dergachev wrote:
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)
Vladimir Dergachev wrote:
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 wha
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 ar
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
25 matches
Mail list logo
