Re: Getting started

2005-01-05 Thread Sjoerd Langkemper
Alex Deucher wrote:
- DRI enabled DDX (2d driver) (xorg tree)
I think this is already done. Would this be the files in
xc/programs/Xserver/hw/xfree86/drivers/trident ?
- 3D driver library (mesa tree)
I have to implement this. There are already some things done for the
CyberbladeXP in Mesa/src/mesa/drivers/dri/trident, right?
- kernel DRM to provide secure/multiple client access to the hardware (drm tree)
Where can I find this? What are the meanings of the directories linux,
linux-core, etc?
Greetings,
Sjoerd

---
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: Getting started

2005-01-04 Thread Alan Cox
On Maw, 2005-01-04 at 09:18, Alan Hourihane wrote:
> The DDX and DRM driver are still in the DRI CVS on the trident-0-0-2 branch.

0-0-2 seems to be empty, but 0-0-1 has code ?>



---
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: Getting started

2005-01-04 Thread Adam Jackson
On Tuesday 04 January 2005 04:19, Alan Hourihane wrote:
> On Mon, Jan 03, 2005 at 06:10:37PM -0500, Adam Jackson wrote:
> > On Monday 03 January 2005 18:02, Alex Deucher wrote:
> > > Actually it did work at one time, basic stuff like glxgears, at least
> > > according to AlanH.
> >
> > I only said "does not".  Present tense ;)
>
> It should still work on the trident-0-0-2 branch. Shouldn't it ?

trident-0-0-2-branch does not have any DRI driver source:

/dri/archive$ find trident-0-0-1 -name trident_context.c
trident-0-0-1/xc/lib/GL/mesa/src/drv/trident/trident_context.c
/dri/archive$ find trident-0-0-2 -name trident_context.c
/dri/archive$ 

I used the trident-0-0-1 tip when I imported the driver into Mesa.  
trident-0-0-2-branch does seem to have the DDX and DRM bits though.

- ajax


pgpTXhvagXqf3.pgp
Description: PGP signature


Re: Getting started

2005-01-04 Thread Peter Karlsson
On Tue, 4 Jan 2005, Thomas Hellström wrote:

> The VIA CN400 contains the Unichrome Pro "Group A" which, 3D-wise,
> should be compatible with the Unichrome, so once the DDX sets up the
> chip correctly, 3D should work right out of the box (at least as good as
> for the Unichrome).
>
> The DDX doesn't support the Unichrome Pro fully yet because of lack of
> HW samples. Specifically lacking is dotclock setup, 2D accel in some
> cases, Xv and XvMC. Since all developers at unichrome.sf.net are unpaid
> freetimers, that support is probably not going to happen until VIA or
> another commercial user donates a board or two.

Ok, thanks for the info. I'm currently underfunded (unemployed) myself
otherwise I would gladly donate a board...

Best regards

Peter K

-- 
We Can Put an End to Word Attachments:
http://www.fsf.org/philosophy/no-word-attachments.html


---
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: Getting started

2005-01-04 Thread Alan Hourihane
On Mon, Jan 03, 2005 at 06:10:37PM -0500, Adam Jackson wrote:
> On Monday 03 January 2005 18:02, Alex Deucher wrote:
> > On Mon, 3 Jan 2005 17:09:31 -0500, Adam Jackson <[EMAIL PROTECTED]> wrote:
> > > On Monday 03 January 2005 09:46, Sjoerd Langkemper wrote:
> > > > Hello,
> > > >
> > > > I would like 3D acceleration for my on-board Trident Cyberblade (VIA
> > > > PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What
> > > > do I have to program in order to get this done?
> > >
> > > Though there is a trident driver in CVS now, it does not work.  The DDX
> > > is not DRI-aware and there is no DRM driver.
> >
> > Actually it did work at one time, basic stuff like glxgears, at least
> > according to AlanH.
> 
> I only said "does not".  Present tense ;)
 
It should still work on the trident-0-0-2 branch. Shouldn't it ?

> > you'd probably need the trident branch from dri 
> > cvs to get it working, plus I'm not sure which chipsets were
> > supported.
> 
> Cyberblade XP only, I believe.
 
Indeed.

Alan.


---
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: Getting started

2005-01-04 Thread Alan Hourihane
On Mon, Jan 03, 2005 at 06:02:27PM -0500, Alex Deucher wrote:
> On Mon, 3 Jan 2005 17:09:31 -0500, Adam Jackson <[EMAIL PROTECTED]> wrote:
> > On Monday 03 January 2005 09:46, Sjoerd Langkemper wrote:
> > > Hello,
> > >
> > > I would like 3D acceleration for my on-board Trident Cyberblade (VIA
> > > PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What
> > > do I have to program in order to get this done?
> > 
> > Though there is a trident driver in CVS now, it does not work.  The DDX is 
> > not
> > DRI-aware and there is no DRM driver.
> 
> Actually it did work at one time, basic stuff like glxgears, at least
> according to AlanH.  you'd probably need the trident branch from dri
> cvs to get it working, plus I'm not sure which chipsets were
> supported.

Exactly. CyberBladeXP is the only one supported.

Alan.


---
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: Getting started

2005-01-04 Thread Alan Hourihane
On Mon, Jan 03, 2005 at 05:09:31PM -0500, Adam Jackson wrote:
> On Monday 03 January 2005 09:46, Sjoerd Langkemper wrote:
> > Hello,
> >
> > I would like 3D acceleration for my on-board Trident Cyberblade (VIA
> > PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What
> > do I have to program in order to get this done?
> 
> Though there is a trident driver in CVS now, it does not work.  The DDX is 
> not 
> DRI-aware and there is no DRM driver.
 
The DDX and DRM driver are still in the DRI CVS on the trident-0-0-2 branch.

Alan.


---
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: Getting started

2005-01-04 Thread Alan Hourihane
On Mon, Jan 03, 2005 at 09:49:30PM +, Alan Cox wrote:
>  On Llu, 2005-01-03 at 14:46, Sjoerd Langkemper wrote:
> > Hello,
> > 
> > I would like 3D acceleration for my on-board Trident Cyberblade (VIA 
> > PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What 
> > do I have to program in order to get this done?
> 
> You would need to write
> - Locking hooks for the X server driver for the trident
> - A kernel module to supervise the access to the video chip and remove
> unsafe commands
> - A 3D graphics driver library for MESA
> 
> A few tiny starting points exist in the form of some bad documentation
> for the cyberblade and some very early code for an old MESA that was
> written by Alan Hourihane and then abandoned before it even drew
> triangles.
 
Correction here. It does draw triangles. But that's about it. The documentation
is seriously lacking and so bringing up the engine on how to draw triangles
is the hardest part. Now that it draws triangles I was going to revisit the 
Command Queueing engine. I've just never had enough time to devote back to it.

NOTE: That the code in Mesa CVS, is for the CyberBladeXP. So it won't work
on other CyberBlades.

Alan.


---
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: Getting started

2005-01-04 Thread =?ISO-8859-1?Q?Thomas_Hellstr=F6m?=




Hi

Peter Karlsson wrote:

  On Mon, 3 Jan 2005, Alan Cox wrote:

  
  
It depends what your interests are. If you want to master 3D graphics
driver writing and have six months to spare you can have great fun. If
you just want a VIA EPIA with working 3D support then the newer chipset
(VIA CLE266) DRI is very close to working and you might want to just
upgrade hardware and join that effort ?

  
  
Just out of curiousity: Is there any support for the VIA CN400
(ongoing/planned)?

  

The VIA CN400 contains the Unichrome Pro "Group A" which, 3D-wise,
should be compatible with the Unichrome, so once the DDX sets up the
chip correctly, 3D should work right out of the box (at least as good
as for the Unichrome).

The DDX doesn't support the Unichrome Pro fully yet because of lack of
HW samples. Specifically lacking is dotclock setup, 2D accel in some
cases, Xv and XvMC. Since all developers at unichrome.sf.net are unpaid
freetimers, that support is probably not going to happen until VIA or
another commercial user donates a board or two.

/Thomas
 



  Best regards

Peter K

  






Re: Getting started

2005-01-03 Thread Alex Deucher
On Tue, 4 Jan 2005 05:15:21 +0100 (MET), Peter Karlsson
<[EMAIL PROTECTED]> wrote:
> On Mon, 3 Jan 2005, Alan Cox wrote:
> 
> > It depends what your interests are. If you want to master 3D graphics
> > driver writing and have six months to spare you can have great fun. If
> > you just want a VIA EPIA with working 3D support then the newer chipset
> > (VIA CLE266) DRI is very close to working and you might want to just
> > upgrade hardware and join that effort ?
> 
> Just out of curiousity: Is there any support for the VIA CN400
> (ongoing/planned)?

I think it's supported.  check out http://unichrome.sf.net

Alex

> 
> Best regards
> 
> Peter K
> 
> --
> We Can Put an End to Word Attachments:
> http://www.fsf.org/philosophy/no-word-attachments.html
> 
>


---
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: Getting started

2005-01-03 Thread Peter Karlsson
On Mon, 3 Jan 2005, Alan Cox wrote:

> It depends what your interests are. If you want to master 3D graphics
> driver writing and have six months to spare you can have great fun. If
> you just want a VIA EPIA with working 3D support then the newer chipset
> (VIA CLE266) DRI is very close to working and you might want to just
> upgrade hardware and join that effort ?

Just out of curiousity: Is there any support for the VIA CN400
(ongoing/planned)?

Best regards

Peter K

-- 
We Can Put an End to Word Attachments:
http://www.fsf.org/philosophy/no-word-attachments.html


---
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: Getting started

2005-01-03 Thread Alex Deucher
On Mon, 3 Jan 2005 18:10:37 -0500, Adam Jackson <[EMAIL PROTECTED]> wrote:
> On Monday 03 January 2005 18:02, Alex Deucher wrote:
> > On Mon, 3 Jan 2005 17:09:31 -0500, Adam Jackson <[EMAIL PROTECTED]> wrote:
> > > On Monday 03 January 2005 09:46, Sjoerd Langkemper wrote:
> > > > Hello,
> > > >
> > > > I would like 3D acceleration for my on-board Trident Cyberblade (VIA
> > > > PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What
> > > > do I have to program in order to get this done?
> > >
> > > Though there is a trident driver in CVS now, it does not work.  The DDX
> > > is not DRI-aware and there is no DRM driver.
> >
> > Actually it did work at one time, basic stuff like glxgears, at least
> > according to AlanH.
> 
> I only said "does not".  Present tense ;)
> 
> > you'd probably need the trident branch from dri
> > cvs to get it working, plus I'm not sure which chipsets were
> > supported.
> 
> Cyberblade XP only, I believe.
> 
> The DDX changes on the old branch can be found at:
> 
> http://freedesktop.org/~ajax/trident-dri-aware-ddx.patch
> 
> It assuredly needs some cleanup.  Also I haven't dug out the DRM yet.

that looks like it should be pretty easy to merge.  I may even give it
a shot.  All that really needs to be merged are the trident_dri* files
and a couple other dri bits in the card rec, etc..  The mode and other
stuff can probably be ignored since that shouldn't have any affect on
the dri.  Now if only I had a cyberblade chipset to test on...

Alex

> 
> - ajax
> 
> 
>


---
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: Getting started

2005-01-03 Thread Adam Jackson
On Monday 03 January 2005 18:02, Alex Deucher wrote:
> On Mon, 3 Jan 2005 17:09:31 -0500, Adam Jackson <[EMAIL PROTECTED]> wrote:
> > On Monday 03 January 2005 09:46, Sjoerd Langkemper wrote:
> > > Hello,
> > >
> > > I would like 3D acceleration for my on-board Trident Cyberblade (VIA
> > > PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What
> > > do I have to program in order to get this done?
> >
> > Though there is a trident driver in CVS now, it does not work.  The DDX
> > is not DRI-aware and there is no DRM driver.
>
> Actually it did work at one time, basic stuff like glxgears, at least
> according to AlanH.

I only said "does not".  Present tense ;)

> you'd probably need the trident branch from dri 
> cvs to get it working, plus I'm not sure which chipsets were
> supported.

Cyberblade XP only, I believe.

The DDX changes on the old branch can be found at:

http://freedesktop.org/~ajax/trident-dri-aware-ddx.patch

It assuredly needs some cleanup.  Also I haven't dug out the DRM yet.

- ajax


pgpHYjnfWxBjM.pgp
Description: PGP signature


Re: Getting started

2005-01-03 Thread Alex Deucher
On Mon, 3 Jan 2005 17:09:31 -0500, Adam Jackson <[EMAIL PROTECTED]> wrote:
> On Monday 03 January 2005 09:46, Sjoerd Langkemper wrote:
> > Hello,
> >
> > I would like 3D acceleration for my on-board Trident Cyberblade (VIA
> > PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What
> > do I have to program in order to get this done?
> 
> Though there is a trident driver in CVS now, it does not work.  The DDX is not
> DRI-aware and there is no DRM driver.

Actually it did work at one time, basic stuff like glxgears, at least
according to AlanH.  you'd probably need the trident branch from dri
cvs to get it working, plus I'm not sure which chipsets were
supported.

Alex

> 
> > I already read some stuff on dri.sf.net, but I am more confused than
> > when I started: drm, dri, opengl, kernel modules, mesa and more. Which
> > of these thing I have to get my hands on?
> 
> First, a different video card.
> 
> - ajax
> 
> 
>


---
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: Getting started

2005-01-03 Thread Alan Cox
 On Llu, 2005-01-03 at 14:46, Sjoerd Langkemper wrote:
> Hello,
> 
> I would like 3D acceleration for my on-board Trident Cyberblade (VIA 
> PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What 
> do I have to program in order to get this done?

You would need to write
- Locking hooks for the X server driver for the trident
- A kernel module to supervise the access to the video chip and remove
unsafe commands
- A 3D graphics driver library for MESA

A few tiny starting points exist in the form of some bad documentation
for the cyberblade and some very early code for an old MESA that was
written by Alan Hourihane and then abandoned before it even drew
triangles.

It depends what your interests are. If you want to master 3D graphics
driver writing and have six months to spare you can have great fun. If
you just want a VIA EPIA with working 3D support then the newer chipset
(VIA CLE266) DRI is very close to working and you might want to just
upgrade hardware and join that effort ?



---
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: Getting started

2005-01-03 Thread Adam Jackson
On Monday 03 January 2005 09:46, Sjoerd Langkemper wrote:
> Hello,
>
> I would like 3D acceleration for my on-board Trident Cyberblade (VIA
> PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What
> do I have to program in order to get this done?

Though there is a trident driver in CVS now, it does not work.  The DDX is not 
DRI-aware and there is no DRM driver.

> I already read some stuff on dri.sf.net, but I am more confused than
> when I started: drm, dri, opengl, kernel modules, mesa and more. Which
> of these thing I have to get my hands on?

First, a different video card.

- ajax


pgpiMA0yt6RPS.pgp
Description: PGP signature


Re: Getting started

2005-01-03 Thread Alex Deucher
On Mon, 03 Jan 2005 15:46:34 +0100, Sjoerd Langkemper
<[EMAIL PROTECTED]> wrote:
> Hello,
> 
> I would like 3D acceleration for my on-board Trident Cyberblade (VIA
> PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What
> do I have to program in order to get this done?
> 
> I already read some stuff on dri.sf.net, but I am more confused than
> when I started: drm, dri, opengl, kernel modules, mesa and more. Which
> of these thing I have to get my hands on?

3d acceleration requires 3 parts:

- DRI enabled DDX (2d driver) (xorg tree)
- 3D driver library (mesa tree)
- kernel DRM to provide secure/multiple client access to the hardware (drm tree)

There was partially implemented trident support in the DRI cvs tree on
one of the branches (although I'm not sure if your chip was supported
or not).  you'd need to port the DDX changes to the xorg trident
driver, get the mesa 3d driver into shape (ajax recently imported the
old code to the into mesa) and update the drm.

Alex

> 
> Thanks in advance,
> 
> Sjoerd
>


---
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


Getting started

2005-01-03 Thread Sjoerd Langkemper
Hello,
I would like 3D acceleration for my on-board Trident Cyberblade (VIA 
PLE133), in order to run 3D apps (e.g. games and glxgears) faster. What 
do I have to program in order to get this done?

I already read some stuff on dri.sf.net, but I am more confused than 
when I started: drm, dri, opengl, kernel modules, mesa and more. Which 
of these thing I have to get my hands on?

Thanks in advance,
Sjoerd
---
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: [Dri-devel] Getting started on DRI hacking...

2002-05-18 Thread José Fonseca

On 2002.05.18 13:31 Ian Molton wrote:
> On Sat, 18 May 2002 12:40:51 +0100
> José Fonseca <[EMAIL PROTECTED]> wrote:
> 
> > > > First thing you need is to download the cvs tree and build it. You
> > > > can
> > >
> > > I downloaded it and am trying to build it following the instructions
> > > you gave, but ran into this:
> 
> > Please tell which branch are you using, and if you changed the
> > ProjectRoot in the host.def file or not.
> 
> whatever the default is, I guess.
> 
> I did this:
> 
> cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri co xc
> 
> here is my host.def:
> 
> #define Options -Wall
> #define DefaultGcc2i386Opt -O2
> #define LibraryCDebugFlags -O2
> #define BuildServersOnly YES
> #define XF86CardDrivers vga radeon
> #define LinuxDistribution LinuxRedHat
> #define DefaultCCOptions -ansi GccWarningOptions -pipe
> #define BuildXF86DRI YES
> /* Optionally turn these on for debugging */
> /* #define GlxBuiltInTdfx YES */
> /* #define GlxBuiltInMga YES */
> /* #define GlxBuiltInR128 YES */
> /* #define GlxBuiltInRadeon YES */
> /* #define DoLoadableServer NO */
> #define SharedLibFont NO
> #define ProjectRoot /usr/src/X11test
> #define MesaUse3DNow YES
> 

You can't simply replace /xc/config/cf/host.def file that comes from the 
CVS. It's better if you just edit it and do not change below where it says 
"Don't change anything below or the build will fail."... ;-)

If you want to define ProjectRoot to /usr/src/X11test don't forget to 
lndir from /usr/X11R6 to /usr/src/X11test.

> > This is just trying to clean everything. Attempt to do "make World"
> > again and see if it gets over it.
> 
> Already tried that. it didnt.
> 
> > You just need the DRI CVS and a working XFRee >= 4.1.x installed on
> > the system as the DRI source is partial and reads some headers from
> > there. If you changed ProjectRoot to another thing (e.g.,
> > /usr/X11R6-DRI) then before you start to compile you need to do:
> >
> > mkdir -p /usr/X11R6-DRI
> > cd /usr/X11R6-DRI
> > lndir ../X11R6
> >
> > so that when building the needed files are found in the right place.
> 
> I'll give that a try. thanks.
> 

José Fonseca

___
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] Getting started on DRI hacking...

2002-05-18 Thread José Fonseca

On 2002.05.18 12:11 Ian Molton wrote:
> On Sat, 18 May 2002 11:08:22 +0100
> José Fonseca <[EMAIL PROTECTED]> wrote:
> 
> > On 2002.05.18 10:41 Ian Molton wrote:
> > > Hi.
> > >
> > > What do I need to do to get started on DRI hacking?
> > >
> > > I want to track down a bug in radeon_dri.so
> > >
> > > how do I build it? what sources do I need?
> >
> > Ian,
> >
> > First thing you need is to download the cvs tree and build it. You can
> 
> I downloaded it and am trying to build it following the instructions you
> gave, but ran into this:
> 

Please tell which branch are you using, and if you changed the ProjectRoot 
in the host.def file or not.

> make[3]: Entering directory `/usr/src/cvs/dri/build/xc/lib/xtrans'
> rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a .emacs_* tags TAGS
> make.log MakeOut  "#"*
> make[3]: Leaving directory `/usr/src/cvs/dri/build/xc/lib/xtrans'
> cleaning in lib/Xau...
> make[3]: Entering directory `/usr/src/cvs/dri/build/xc/lib/Xau'
> make[3]: *** No rule to make target `clean'.  Stop.
> make[3]: Leaving directory `/usr/src/cvs/dri/build/xc/lib/Xau'
> make[2]: *** [clean] Error 2
> make[2]: Leaving directory `/usr/src/cvs/dri/build/xc/lib'
> make[1]: *** [clean] Error 2
> make[1]: Leaving directory `/usr/src/cvs/dri/build/xc'
> make: *** [World] Error 2
> ian:/usr/src/cvs/dri/build/xc$
> 
> What is xtrans?
> 

Have no idea..!

This is just trying to clean everything. Attempt to do "make World" again 
and see if it gets over it. 
> > All this process can be quite tricky on the first time you make it, so
> >
> > make sure that you have you new Xfree running properly before you
> > start playing with it.
> 
> is the DRI CVS all I need? or was I supposed to add it to a full X4.2
> source?
> 

You just need the DRI CVS and a working XFRee >= 4.1.x installed on the 
system as the DRI source is partial and reads some headers from there. If 
you changed ProjectRoot to another thing (e.g., /usr/X11R6-DRI) then 
before you start to compile you need to do:

mkdir -p /usr/X11R6-DRI
cd /usr/X11R6-DRI
lndir ../X11R6

so that when building the needed files are found in the right place.

José Fonseca

___
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] Getting started on DRI hacking...

2002-05-18 Thread Ian Molton

On Sat, 18 May 2002 11:08:22 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:

> On 2002.05.18 10:41 Ian Molton wrote:
> > Hi.
> > 
> > What do I need to do to get started on DRI hacking?
> > 
> > I want to track down a bug in radeon_dri.so
> > 
> > how do I build it? what sources do I need?
> 
> Ian,
> 
> First thing you need is to download the cvs tree and build it. You can

I downloaded it and am trying to build it following the instructions you
gave, but ran into this:

make[3]: Entering directory `/usr/src/cvs/dri/build/xc/lib/xtrans'
rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a .emacs_* tags TAGS
make.log MakeOut  "#"*
make[3]: Leaving directory `/usr/src/cvs/dri/build/xc/lib/xtrans'
cleaning in lib/Xau...
make[3]: Entering directory `/usr/src/cvs/dri/build/xc/lib/Xau'
make[3]: *** No rule to make target `clean'.  Stop.
make[3]: Leaving directory `/usr/src/cvs/dri/build/xc/lib/Xau'
make[2]: *** [clean] Error 2
make[2]: Leaving directory `/usr/src/cvs/dri/build/xc/lib'
make[1]: *** [clean] Error 2
make[1]: Leaving directory `/usr/src/cvs/dri/build/xc'
make: *** [World] Error 2
ian:/usr/src/cvs/dri/build/xc$

What is xtrans?

> All this process can be quite tricky on the first time you make it, so
> 
> make sure that you have you new Xfree running properly before you
> start playing with it.

is the DRI CVS all I need? or was I supposed to add it to a full X4.2
source?

___
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] Getting started on DRI hacking...

2002-05-18 Thread José Fonseca

On 2002.05.18 10:41 Ian Molton wrote:
> Hi.
> 
> What do I need to do to get started on DRI hacking?
> 
> I want to track down a bug in radeon_dri.so
> 
> how do I build it? what sources do I need?

Ian,

First thing you need is to download the cvs tree and build it. You can 
follow the instructions on http://dri.sourceforge.net/doc/DRIcompile.html. 
If you don't want to override your distro's XFree, then follow instead 
Leif's instructions on http://www.retinalburn.net/linux/dri_HOWTO.html 
replacing mach64-?-?-?-branch for the branch you're interested (either 
HEAD or tcl-0-0-branch).

All this process can be quite tricky on the first time you make it, so 
make sure that you have you new Xfree running properly before you start 
playing with it.

After, go to the radeon Mesa driver sources (see 
http://dri.sourceforge.net/doc/faq/architecture.html#ED-DRIVER-WHERE) and 
start debugging them, either by putting debug output statements, or 
running gdb on it, like:

   gdb glxgears
   run
(there is always a breakpoint here due to the SSE 
detection - it's best the time to add breakpoints in radeon_dri.so)
   break nauthy-function-in-radeon-dri-so
   continue
(it should popup)
   list
   step
   step
   next
   print foo
   ...

if your app segfaults then when you run it with gdb it will breakpoint 
there.

You don't need to recompile the whole X when you change parts of it. Just 
do "make", (if you mess with header is better to do "make clean" first 
because the dependencies may be wrong) and then " su -c "make install" "


When you got so far come to us again giving more details about the bug 
you're keen, and we'll give hints of places to look and answer any doubt 
you may have.

José Fonseca

___
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] Getting started on DRI hacking...

2002-05-18 Thread Ian Molton

Hi.

What do I need to do to get started on DRI hacking?

I want to track down a bug in radeon_dri.so

how do I build it? what sources do I need?

___
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel