diff options
| author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2011-10-26 00:53:57 +0200 |
|---|---|---|
| committer | Dave Airlie <airlied@redhat.com> | 2012-07-19 22:50:47 -0400 |
| commit | 4c373790a4d4d667d1ab38b1fe2bbf6a8322e93b (patch) | |
| tree | 19d122639cb74a5c2cc49f8e32fbea2d8b242053 /drivers/gpu/drm/drm_dma.c | |
| parent | b0071efe827f68cf173e1a8868b70618e9aca7d7 (diff) | |
| download | blackbird-op-linux-4c373790a4d4d667d1ab38b1fe2bbf6a8322e93b.tar.gz blackbird-op-linux-4c373790a4d4d667d1ab38b1fe2bbf6a8322e93b.zip | |
drm: ditch strange DRIVER_DMA_QUEUE only error bail-out
Only one driver (i810) even sets that flag. Now the actual locking
code uncoditionally promotes lock->context to an unsigned int.
Closer inspection of the userspace reveals that the drm lock context
is defined as an unsigned int (at least on linux). I suspect we just
have a strange case of signedness confusion going on.
Tested on my i815, doesn't seem to break anything.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/drm_dma.c')
0 files changed, 0 insertions, 0 deletions
