Em Seg 15 Mar 2004 18:44, you wrote: > On Mon, 15 Mar 2004 17:30:48 -0300 > > "Paulo R. Dallan" <[EMAIL PROTECTED]> wrote: > > Em Ter 09 Mar 2004 20:09, you wrote: > > > "Paulo R. Dallan" <[EMAIL PROTECTED]> wrote: > > > > Em Seg 08 Mar 2004 13:31, you wrote: > > > > > Em Seg 08 Mar 2004 08:35, you wrote: > > > > <snip> > > > > Hi Felix, > > > > How are you doing? > > > > Sorry for not talking about the driconfig support, but I was out of town > > for some days and was completely off-line. But did not forget about the > > help promised! :) > > > > Well, we have some progress, so here we go. > > > > <snip> > > > > > See the end of the design doc for some XML-references. Though I don't > > > think you need to deal with XML directly either. There are macro > > > definitions for some common options in xmlpool.h. You only need to > > > write some XML if you want to add new options. But that's pretty > > > intuitive and the existing options in xmlpool.h should give good > > > examples. > > > > <snip> > > > > I've been studing the dri configuration documentations, checked the macro > > possibilities in xmlpool.h, and following your tip, analysed how it was > > implemented for the mga card (the code in mga_xmesa.c). So, basically, > > it's a macro at compiling time, correct (actually a good idea)? > > The macros expand to exactly the XML document that you see with > "xdriinfo options mga". > > > Ok, I checked the output of "xdriinfo options mga" and "xdriinfo options > > savage". This last one, obviously, returned nothing (because this is what > > is supposed to be being implemented now), the other one returned a page > > of xml info (and, in fact, very /few/ options, basically "vblank_mode", > > "texture_depth" and "color_reduction"). > > Yes, anyone is welcome to add new options. ;-) > > > (i) Now comes one question: this options implemented, what is their > > relation to the options described in the man page of the driver (e.g. > > "man mga" or "man savage"? Is there any relation between both? Does the > > man page contains all of them, /plus/ others related to X86 general > > options etc? > > The man pages refer only to the 2D drivers. The 3D driver options aren't > documented in any manpages. The hope was that they are self documenting, > but currently the descriptions are rather terse. There is some more > verbose documentation of some options in the Wiki. > > > (ii) So, in order to implement the options for the savage driver, I have > > to go through the code itself, or is there any document which I should > > follow (i.e., how to verify which are the options of xmlpool.h which are > > aplicable)? If it is throught the code, good, will learn a lot; but it > > won't be that easy at the present stage! ;) - any tip for where to start > > from? > > The first step will be to add the necessary boilerplate to the screen- > and context data structures, add a first simple (maybe empty) option > description in __driConfigOptions and to call the initialization > functions in CreateContext and CreateScreen. If you want to see output > from xdriinfo you can safely add options without actually implementing > any code that evaluates them. > > The hard part will be adding the actual implementation of options. > That's where you'll have to go into different parts of the driver and > make the behaviour depend on some options. Often it's a good idea to > read an option value in CreateContext and store it somewhere in the > Context structure. Then it can be accessed more quickly later on. > > > Best regards, > > > > Paulo > > > > PS1: In parallel, have been studing the "Redbook" (& having a view in the > > Bluebook) and also following some tutorials in gl, glx and, more > > especifically, in glu & glut (for Linux). Have been having some problems > > in image viewing, or funcions not being implemented. Is it relevant, or > > not really fully implemented yet so we may get some trouble in it? > > Someone else complained about this. The funny thing is that the relevant > mesa demo (don't remember the name, something with "pix" I think) works > on my system, but not on another user's system. Someone is going to have > to fix it at some point. I have other priorities ATM. > > > PS2: Funny that to compile glu & glut programs, I have to especifically > > use the -L option to indicate the location of the libraries, although my > > ld.so.config file seem to include the path (/usr/X11R6/lib)... Have you > > had the same problem? > > I don't think so. I usually use this in Makefiles: > > LDFLAGS=-lGL -lGLU -lglut > > Though the search paths of the compiler don't have anything to do with > the search paths of the dynamic linker IIRC. > > > PS3: Will have a look at the meeting today (actually, have done that > > twice already). Will be quiet (as usual), just watching. :) > > The funny thing is that the messages seem to take so long to get. I don't > > know if I'm getting them delayed somehow. > > Don't know. Sometimes it's a bit hard to follow because all the threads > of discussion are interleaved. And sometimes people take some time to > type a good answer or have to look something up first. > > Cu, > Felix > > P.S.: I think it would be good to make this thread public on the > dri-devel or mesa3d-dev mailing list (maybe both). It could be > instructive for people interested in adding configuration support to > other drivers. Feel free to forward this message to the mailing lists.
Forwarded as suggested. :) Paulo ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
