On Thu, Aug 29, 2013 at 3:58 AM, Ville Syrjälä
wrote:
>> Imo we should just convert primary planes to real planes so that we
>> can do the same table-based checking for them as we do for secondary
>> planes right now.
>
> My plan for i915 is to convert them to drm_planes but first keep them
> hidd
On Thu, Aug 29, 2013 at 3:01 AM, Daniel Vetter wrote:
> On Thu, Aug 29, 2013 at 5:51 AM, Rob Clark wrote:
>>> 1. The API is geared toward updating one object at a time. Android's
>>> graphics stack needs the entire screen updated atomically to avoid tearing,
>>> and on some SoCs to avoid wedg
On Thu, Aug 29, 2013 at 10:58:51AM +0300, Ville Syrjälä wrote:
> After that we need to figure out how we can expose them to userspace w/o
> risking breaking stuff too much. Maybe a new ioctl to enumerate private
> planes only? And the maybe only accept direct use of private planes via
> the atomic
On Thu, Aug 29, 2013 at 09:01:01AM +0200, Daniel Vetter wrote:
> On Thu, Aug 29, 2013 at 5:51 AM, Rob Clark wrote:
> >> 1. The API is geared toward updating one object at a time. Android's
> >> graphics stack needs the entire screen updated atomically to avoid
> >> tearing, and on some SoCs to
On Thu, Aug 29, 2013 at 5:51 AM, Rob Clark wrote:
>> 1. The API is geared toward updating one object at a time. Android's
>> graphics stack needs the entire screen updated atomically to avoid tearing,
>> and on some SoCs to avoid wedging the display hardware. Rob Clark's atomic
>> modeset pa
