Hi Inki, I've pushed out the latest bits to http://cgit.freedesktop.org/~danvet/drm/log/?h=drm-kms-locking with some hacks on top to be able to compile all the arm drivers. Testing feedback of the entire pile would be awesome, especially since you've had some issues with framebuffer lifecycle and those should now be correctly fixable with the proper refcounting. If you have too many conflicts pls yell so that I can include your base into mine and rebase the entire series. Thanks, Daniel On Thu, Dec 13, 2012 at 1:26 PM, Inki Dae <inki.dae@xxxxxxxxxxx> wrote: >> -----Original Message----- >> From: dri-devel-bounces+inki.dae=samsung.com@xxxxxxxxxxxxxxxxxxxxx >> [mailto:dri-devel-bounces+inki.dae=samsung.com@xxxxxxxxxxxxxxxxxxxxx] On >> Behalf Of Daniel Vetter >> Sent: Thursday, December 13, 2012 8:05 PM >> To: DRI Development >> Cc: Nouveau Dev; Intel Graphics Development; Daniel Vetter >> Subject: [PATCH 2/2] drm/exynos: reorder framebuffer init sequence >> >> For user framebuffers it's easier to just inline the >> exynos_drm_framebuffer_init helper instead of trying to adjust it - >> most of the things that helper sets up need to be overwritten anyway >> again due to the multiple backing storage objects support exynos has, >> but does not use for the fbdev. >> > > Hi Daniel, > > I'd rebase this patch to -next. This patch is conflicted with -next. > And if there is no any problem after test, will apply it. -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
