On 2014년 07월 09일 20:06, Rahul Sharma wrote:
On 8 July 2014 21:25, Inki Dae inki@samsung.com wrote:
2014-06-20 0:13 GMT+09:00 Rahul Sharma rahul.sha...@samsung.com:
This situation arises when userspace remove the frambuffer object
and call setmode ioctl.
drm_mode_rmfb --
Hi Inki,
What do you think about the following fix? I need your inputs for this.
Regards,
Rahul Sharma
On 19 June 2014 20:43, Rahul Sharma rahul.sha...@samsung.com wrote:
This situation arises when userspace remove the frambuffer object
and call setmode ioctl.
drm_mode_rmfb --
2014-06-20 0:13 GMT+09:00 Rahul Sharma rahul.sha...@samsung.com:
This situation arises when userspace remove the frambuffer object
and call setmode ioctl.
drm_mode_rmfb -- drm_plane_force_disable -- plane-crtc = NULL;
and
drm_mode_setcrtc -- exynos_plane_commit -- passes plane-crtc to
This situation arises when userspace remove the frambuffer object
and call setmode ioctl.
drm_mode_rmfb -- drm_plane_force_disable -- plane-crtc = NULL;
and
drm_mode_setcrtc -- exynos_plane_commit -- passes plane-crtc to
exynos_drm_crtc_plane_commit which is NULL.
This crashes the system.