diff for duplicates of <53DF9B58.8000403@canonical.com> diff --git a/a/1.txt b/N1/1.txt index c845a77..eb1b7fe 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -12,7 +12,3 @@ op 04-08-14 16:37, Christian König schreef: What cases did I miss then? I'm curious how you want to move the fence waiting out of reset, when there are so many places that could potentially wait, like radeon_ib_get can call radeon_sa_bo_new which can do a wait, or radeon_ring_alloc that can wait on radeon_fence_wait_next, etc. -_______________________________________________ -dri-devel mailing list -dri-devel@lists.freedesktop.org -http://lists.freedesktop.org/mailman/listinfo/dri-devel diff --git a/a/content_digest b/N1/content_digest index a63035f..680677c 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -33,10 +33,6 @@ "> How about moving the fence waiting out of the reset code?\n" "What cases did I miss then?\n" "\n" - "I'm curious how you want to move the fence waiting out of reset, when there are so many places that could potentially wait, like radeon_ib_get can call radeon_sa_bo_new which can do a wait, or radeon_ring_alloc that can wait on radeon_fence_wait_next, etc.\n" - "_______________________________________________\n" - "dri-devel mailing list\n" - "dri-devel@lists.freedesktop.org\n" - http://lists.freedesktop.org/mailman/listinfo/dri-devel + I'm curious how you want to move the fence waiting out of reset, when there are so many places that could potentially wait, like radeon_ib_get can call radeon_sa_bo_new which can do a wait, or radeon_ring_alloc that can wait on radeon_fence_wait_next, etc. -583a9ecc9a7a618cb55eab2b90bdb0b9c206e859556b91935782f1b010a4e087 +1cb2ad3fb9be7aa664500eb9e4229ab00e21fe5c6aaa9bccfe16555813f07e0d
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.