You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the (stolen from ChromeOS) rockchip-drm-ioctl called from create_custom_gem currently does (exactly?) the same as the dumb_create callback of the rockchip drm driver. So it could possibly be calling this one, instead of defining a new ioctl.
But in [0] Dave Airlie was quite vehemently stating:
"DON'T USE DUMB BUFFERS FOR ALLOCATING BUFFERS USED FOR ACCELERATION."
and although there was an answer from a developer of the armsoc X-Server the discussion did not seem to reach any conclusion.
So, figure out what the correct path is here. Either we can use the dumb interface, should define this similar new ioctl, or maybe the ioctl even needs more functionality of some sort?
Currently the (stolen from ChromeOS) rockchip-drm-ioctl called from create_custom_gem currently does (exactly?) the same as the dumb_create callback of the rockchip drm driver. So it could possibly be calling this one, instead of defining a new ioctl.
But in [0] Dave Airlie was quite vehemently stating:
"DON'T USE DUMB BUFFERS FOR ALLOCATING BUFFERS USED FOR ACCELERATION."
and although there was an answer from a developer of the armsoc X-Server the discussion did not seem to reach any conclusion.
So, figure out what the correct path is here. Either we can use the dumb interface, should define this similar new ioctl, or maybe the ioctl even needs more functionality of some sort?
[0] http://lists.freedesktop.org/archives/dri-devel/2013-April/037823.html
The text was updated successfully, but these errors were encountered: