From: Denis O. K. <do...@di...> - 2003-06-03 18:43:19
|
Quoting Brian Paul (br...@tu...): > 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 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 -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" Convergence GmbH |