Just a side note, is the history of these files needed in the mesa tree?
I would think it would only be uasable in the DRI tree and it's archived
there so no need to duplicate that.
The DRM is another storry, ppl may wish to build older versions from the
new module.
--- Michel Dänzer <[EMAIL PRO
On Wed, 2004-03-17 at 19:10, Ian Romanick wrote:
>
> Another question. dri_util.[ch] will need to be moved from DRI CVS to
> Mesa CVS. Is it possible to copy the ,v files from one project to another?
Theoretically yes, but won't this cause the files to appear in checkouts
of earlier revisions
Ian Romanick wrote:
Keith Whitwell wrote:
Ian Romanick wrote:
There also seem to be some issues with drivers using CARD32. That
type comes from X, so it should probably be replaced with something
window-system agnostic. Would int32_t work for everyone?
I think this is the best we can do, th
--- Ian Romanick <[EMAIL PROTECTED]> wrote:
> Another question. dri_util.[ch] will need to be moved from DRI CVS to
> Mesa CVS. Is it possible to copy the ,v files from one project to another?
I just copied v files from mesa into dri/drm and it seems to work.
Check the videro-reset files in th
Keith Whitwell wrote:
Ian Romanick wrote:
There also seem to be some issues with drivers using CARD32. That
type comes from X, so it should probably be replaced with something
window-system agnostic. Would int32_t work for everyone?
I think this is the best we can do, though at least some vers
--- Felix Kühling <[EMAIL PROTECTED]> wrote:
> Hmm, the savage driver uses GLuint when it actually means a 32 bit word
> in the register definitions. Where does int32_t come from? Would it be
> the right type to use in that case? Is there also a uint32_t?
They come form the standard C header file
--- Felix Kühling <[EMAIL PROTECTED]> wrote:
> On Tue, 16 Mar 2004 16:31:37 -0800
> Ian Romanick <[EMAIL PROTECTED]> wrote:
>
> > I spent some time today pulling the DRI interface structures and
> > function prototypes out of glxclient.h. I came across one snag
> that I
> > missed before. It
On Tue, 16 Mar 2004 16:31:37 -0800
Ian Romanick <[EMAIL PROTECTED]> wrote:
> I spent some time today pulling the DRI interface structures and
> function prototypes out of glxclient.h. I came across one snag that I
> missed before. It turns out that the bindContext2 and unbindContext2
> method
Ian Romanick wrote:
I spent some time today pulling the DRI interface structures and
function prototypes out of glxclient.h. I came across one snag that I
missed before. It turns out that the bindContext2 and unbindContext2
methods in __DRIcontextRec are passed pointers to GLXContext structure
I spent some time today pulling the DRI interface structures and
function prototypes out of glxclient.h. I came across one snag that I
missed before. It turns out that the bindContext2 and unbindContext2
methods in __DRIcontextRec are passed pointers to GLXContext structures.
I don't think t
10 matches
Mail list logo
