On Wed, Oct 08, 2014 at 10:45:48AM +0100, Chris Wilson wrote:
> On Wed, Oct 08, 2014 at 11:16:38AM +0200, Daniel Vetter wrote:
> > On Tue, Oct 7, 2014 at 3:13 PM, Chris Wilson
> > wrote:
> > > The implmentation is simple in the extreme: we only want to wait for
> > > events if the device was open
On Tue, Oct 7, 2014 at 3:13 PM, Chris Wilson
wrote:
> The implmentation is simple in the extreme: we only want to wait for
> events if the device was opened in blocking mode, otherwise we grab what
> is available and report an error if there was none.
>
> Signed-off-by: Chris Wilson
> Cc: dri-de
On Wed, Oct 08, 2014 at 11:16:38AM +0200, Daniel Vetter wrote:
> On Tue, Oct 7, 2014 at 3:13 PM, Chris Wilson
> wrote:
> > The implmentation is simple in the extreme: we only want to wait for
> > events if the device was opened in blocking mode, otherwise we grab what
> > is available and report
The implmentation is simple in the extreme: we only want to wait for
events if the device was opened in blocking mode, otherwise we grab what
is available and report an error if there was none.
Signed-off-by: Chris Wilson
Cc: dri-devel at lists.freedesktop.org
---
drivers/gpu/drm/drm_fops.c | 12
On Tue, 7 Oct 2014 14:13:51 +0100
Chris Wilson wrote:
> The implmentation is simple in the extreme: we only want to wait for
> events if the device was opened in blocking mode, otherwise we grab
> what is available and report an error if there was none.
>
> Signed-off-by: Chris Wilson
> Cc: dr
