You are right. We need to support at least 2 buffer mappings: one for the user and the other one for internal purposes.
Marek On Thu, Jan 30, 2014 at 11:33 PM, Fredrik Höglund <fred...@kde.org> wrote: > On Thursday 30 January 2014, Chris Forbes wrote: >> Marek, >> >> I think there's an interaction with software primitive restart here. >> >> The primitive restart path maps the index buffer (and the indirect >> buffer, for indirect draws), and relies on these checks to guarantee >> that's possible. >> >> That may not be an issue for your driver, though -- I don't know. > > This is also an issue with display list compilation and PBO fallbacks, > which is relevant for the gallium state tracker. > > I'm not sure how to best deal with it. Maybe we need another driver > hook that can create a private mapping of an already mapped buffer > object. > > Fredrik > _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev