diff options
| author | Marek Olšák <marek.olsak@amd.com> | 2014-01-13 13:03:25 +0100 |
|---|---|---|
| committer | Marek Olšák <marek.olsak@amd.com> | 2014-01-23 01:47:14 +0100 |
| commit | ee0dc659c849ca9a552edd88d062035cae189068 (patch) | |
| tree | 5454254a89a3402fb0e7bc8c39a86d446984d240 /src/gallium/auxiliary/util/u_upload_mgr.h | |
| parent | 0c20bff4b626413804486444ad239af620722e2f (diff) | |
| download | external_mesa3d-ee0dc659c849ca9a552edd88d062035cae189068.zip external_mesa3d-ee0dc659c849ca9a552edd88d062035cae189068.tar.gz external_mesa3d-ee0dc659c849ca9a552edd88d062035cae189068.tar.bz2 | |
gallium/u_upload_mgr: don't expose u_upload_flush
It's unused and shouldn't be used at all in my opinion.
If some driver doesn't support the unsynchronized flag, u_upload_mgr should
avoid the synchronization by other means, e.g. by using the DONTBLOCK flag.
Diffstat (limited to 'src/gallium/auxiliary/util/u_upload_mgr.h')
| -rw-r--r-- | src/gallium/auxiliary/util/u_upload_mgr.h | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/src/gallium/auxiliary/util/u_upload_mgr.h b/src/gallium/auxiliary/util/u_upload_mgr.h index 82215a5..63bf30e 100644 --- a/src/gallium/auxiliary/util/u_upload_mgr.h +++ b/src/gallium/auxiliary/util/u_upload_mgr.h @@ -57,16 +57,6 @@ struct u_upload_mgr *u_upload_create( struct pipe_context *pipe, void u_upload_destroy( struct u_upload_mgr *upload ); /** - * Unmap and release old upload buffer. - * - * This is like u_upload_unmap() except the upload buffer is released for - * recycling. This should be called on real hardware flushes on systems - * that don't support the PIPE_TRANSFER_UNSYNCHRONIZED flag, as otherwise - * the next u_upload_buffer will cause a sync on the buffer. - */ -void u_upload_flush( struct u_upload_mgr *upload ); - -/** * Unmap upload buffer * * \param upload Upload manager |