Skip to content
Snippets Groups Projects
  1. Jul 20, 2005
  2. Jul 19, 2005
  3. Jul 18, 2005
    • Brian Paul's avatar
      s/clippping/clipping/ · 7e152b83
      Brian Paul authored
      7e152b83
    • Philippe Houdoin's avatar
      ed886336
    • Alan Hourihane's avatar
      re-enable the ffb driver · 5343ae83
      Alan Hourihane authored
      5343ae83
    • Alan Hourihane's avatar
      Fix the FFB driver for the renderbuffer changes · df88dfe1
      Alan Hourihane authored
      Support NEW INTERFACE as well
      df88dfe1
    • Alan Hourihane's avatar
      pass in the renderbuffer · c235a96a
      Alan Hourihane authored
      c235a96a
    • Ian Romanick's avatar
      Missed this on the previous commit. · aa8ff1e7
      Ian Romanick authored
      aa8ff1e7
    • Ian Romanick's avatar
      Wrap every place that accesses a dispatch table with a macro. A new script- · 9bdfee3a
      Ian Romanick authored
      generated file, called src/mesa/glapi/dispatch.h, is added.  This file
      contains three macros for each API function.  It contains a GET, a SET, and
      a CALL.  Each of the macros take a pointer to the context and a pointer to
      the dispatch table.
      
      In several threads on mesa3d-dev we discussed replacing _glapi_add_entrypoint
      with a new function called _glapi_add_dispatch.  For this discussion, the
      important difference between the two is that the caller of _glapi_add_dispatch
      does *not* know what the dispatch offset will be at compile time.  Because of
      this callers need to track the dispatch offset returned by
      _glapi_add_dispatch.
      
      http://marc.theaimsgroup.com/?t=111947074700001&r=1&w=2
      
      The downside is that driver code then has to access the dispatch table two
      different ways.  It accesses it using structure tags (e.g., exec->Begin) for
      functions with fixed offsets and via a remap table (e.g., exec[
      remap->NewExtensionFunction ]) for functions without fixed offsets. Yuck!
      
      Using the macros allows both types of functions to be accessed
      identically.  If a driver needs to set a pointer for Begin, it does
      'SET_Begin(ctx, exec, my_begin_function)'.  If it needs to set a pointer
      for NewExtensionFunction, it does 'SET_NewExtensionFunction(ctx, exec,
      my_NewExtensionFunction_function)'.  Furthermore, if at some point in
      the future a static offset is assigned for NewExtensionFunction, only
      the macros need to change (instead of every single place that accesses a
      table for that function).
      
      This code differs slightly from the originally posted patches in that the
      CALL, GET, and SET marcos no longer take a context pointer as a parameter.
      Brian Paul had suggested that the remap table could be stored as a global
      since it would be set at CreateScreen time and would be constant for all
      contexts.  This change reflects that feedback.
      
      http://marc.theaimsgroup.com/?t=112087194700001&r=1&w=2
      9bdfee3a
  4. Jul 16, 2005
  5. Jul 15, 2005
  6. Jul 14, 2005
  7. Jul 13, 2005
  8. Jul 11, 2005
  9. Jul 10, 2005
  10. Jul 08, 2005
  11. Jul 07, 2005
  12. Jul 06, 2005
  13. Jul 05, 2005
  14. Jul 02, 2005
Loading