Hi,
* Daniel Stone [180420 10:21]:
> Hi Tomi,
>
> On 20 April 2018 at 08:09, Tomi Valkeinen wrote:
> > It's actually not quite clear to me how manual update displays work with
> > DRM...
> >
> > As far as I see, we have essentially two cases: 1)
* Daniel Stone [180420 14:41]:
> Hi Tony!
>
> On 20 April 2018 at 15:25, Tony Lindgren wrote:
> > * Daniel Stone [180420 10:21]:
> >> On 20 April 2018 at 08:09, Tomi Valkeinen wrote:
> >> > It's actually not
Hi Tony!
On 20 April 2018 at 15:25, Tony Lindgren wrote:
> * Daniel Stone [180420 10:21]:
>> On 20 April 2018 at 08:09, Tomi Valkeinen wrote:
>> > It's actually not quite clear to me how manual update displays work with
>> > DRM...
Hi Tomi,
On 20 April 2018 at 08:09, Tomi Valkeinen wrote:
> It's actually not quite clear to me how manual update displays work with
> DRM...
>
> As far as I see, we have essentially two cases: 1) single buffering,
> where the userspace must set an area in the fb dirty,
On Fri, Apr 20, 2018 at 10:09:38AM +0300, Tomi Valkeinen wrote:
> Hi Sebastian,
>
> On 30/03/18 20:18, Sebastian Reichel wrote:
> > This adds the required infrastructure for manually
> > updated displays, such as DSI command mode panels.
> >
> > While those panels often support partial updates
>
Hi Sebastian,
On 30/03/18 20:18, Sebastian Reichel wrote:
> This adds the required infrastructure for manually
> updated displays, such as DSI command mode panels.
>
> While those panels often support partial updates
> we currently always do a full refresh. Display
> will be refreshed when
This adds the required infrastructure for manually
updated displays, such as DSI command mode panels.
While those panels often support partial updates
we currently always do a full refresh. Display
will be refreshed when something calls the dirty
callback, such as libdrm's drmModeDirtyFB().
This