| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Alan Coopersmith <alan.coopersmith@sun.com>
Signed-off-by: Brian Paul <brianp@vmware.com>
|
|
|
|
Any allocation that may fail should be checked, and propogate the
error upwards. At the highest level we will flush batch and retry.
This is an alternate strategy to what the original DRI driver did of
attempting to flush batch from the lowest levels (eg inside
BEGIN_BATCH). The trouble with that strategy was that flushes could
occur at unexpected times, and additionally there was a need for a
wierd notification mechanism to propogate the 'lost context' state
back up to higher levels.
Propogating the errors directly gives us a lot of flexibility how to
deal with these states, at the expense of a lot more checking in the
code.
Will add some sanity checks later to make sure that out-of-memory
conditions are properly escalated and not lost halfway up the stack.
|
|
trivial/tri runs without crashing (on debug winsys) but still produces
obviously incorrect command buffers.
|
|
|
|
With the stubbed out, non-hardware xlib winsys, trivial/clear runs and
prints a plausible command stream
|
|
|
|
|
|
|
|
Easier to understand what's going on in the driver sources, convert
stereotype usage values back to GEM read/write domain flags in the
winsys.
|
|
That was a lot more work than I expected. Still the winsys to go,
then the small matter of making it work and re-enabling the
missing functionality.
|
|
|
|
|
|
|
