Denis Oliver Kropp wrote:
Quoting Brian Paul ([EMAIL PROTECTED]):
src/
mesa/
glapi/
glapi*.[ch] - dispatcher files
APIspec file gl*.py - Python API scripts
main/ - core Mesa sources
attrib.c
context.c
enable.c
...
CPU detection code
transform/ - was tnl
t_*.[ch]
X86/3Dnow code
math/ - math/vector routines
m_*.[ch]
swrast/ - s/w rasterization
s_*.[ch]
mmx_blend.S
swsetup/ - was swrast_setup
ss_*.[ch]
arraycache/ - vertex array stuff
ac_*.[ch]
drivers/
common/ - reusable driver code
and transform_dd/ files
x11/ - X11 (XMesa) driver
osmesa/ - OSMesa driver
swfbdev/ - software fbdev driver
radeon/ - DRI/fbdev driver
radeon-es/ - subset radeon fbdev driver
r200/ ...
mga/ - DRI/fbdev driver
windows/
beos/
ggi/
glide/ - was FX driver
dos/
dri/ - es dri code
Oops, dri/ is indented one tab too far, and probably not named very well. It should be probably be src/dri-es/ since it implements DRI facilities for the embedded subset.
I think the DRI drivers should be moved into the dri/ directory which itself should be in the drivers/ directory, because drivers/ contains the public APIs of Mesa, e.g. OSMesa, fxMesa etc. The dri/ directory will contain windowing system independent code as a public interface to the DRI drivers. The DRI drivers won't be used by applications directly.
My suggestion:
drivers/ common/ - reusable driver code and transform_dd/ files x11/ - X11 (XMesa) driver osmesa/ - OSMesa driver swfbdev/ - software fbdev driver windows/ beos/ ggi/ glide/ - was FX driver dos/ dri/ - dri driver interface common/ - reusable driver code radeon/ - DRI/fbdev driver r200/ - DRI/fbdev driver mga/ - DRI/fbdev driver
Where do you propose that the files currently in Mesa/src/dri/ (such as dri_glx.c, glxclient.h, etc) belong? src/dri-es/ is the place I was planning on.
I'm trying to keep the tree fairly shallow (one of the things that intimidates people about the XFree86/DRI tree is its size and depth) so I'm not sure we need drivers/dri/ yet.
Also, I want to try to keep all source files as leaves in the tree. That is, a directory foo/ won't contain both files and subdirs; just one or the other.
Brian,
One thing that would help me understand how this new tree structure (and how having the Mesa DRI driver in the tree) will work would be to understand where the resulting binary files would end up *after* a build. Specifically, can a radeon DRI driver module be built from this standalone tree? Where will it reside? Where will an embedded Mesa radeon driver module reside? and finally, future window system bindings, for example a DirectFB Mesa driver module. Where would that live?
--
/\
Jens Owen / \/\ _
[EMAIL PROTECTED] / \ \ \ Steamboat Springs, Colorado------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
