On Thu, Jan 24, 2013 at 10:53:25AM -0600, Rob Clark wrote:
On Thu, Jan 24, 2013 at 10:20 AM, Daniel Vetter daniel.vetter@ffwll.ch wrote:
Hi all,
This series is mostly just a bit of fallout from my modeset locking rework which just landed, and some other things I've noticed while rearchitecting the modeset infrastructure for i915.k in 3.7.
First two patches are for omapdrm, but included here since they depend upon the locking rework in drm-next. Dunno what to do with these patches, so I'll just drop them here. Rob, you really need to put the finishing touches on omapdrm and move it out of staging!
Yeah, I think that omapdrm is ready to move out of staging, and it would simplify a lot of things to not have to merge changes across drm/staging/omapdss..
I do prefer that over time, omapdrm and omapdss merge closer together (ie. move omapdss into omapdrm, so we can make better use of drm helpers in the omapdss bits.. and probably this starts to make even more sense as CDF comes into the picture). But from a functional standpoint, now that "drm/omap: use omapdss low level API" has landed, the kms stuff works sanely/properly finally.
Dave/Greg, how do I go about this?
There's two ways. One, I can just move the files to the correct location if David has no objections.
Or, if people want to review this better, create a patch that just adds the driver to the "correct" place. Then, when that is accepted in the drm tree, I'll just delete the staging version.
It's up to David which he wants me to do, either is fine with me.
greg k-h