On Fri, Oct 26, 2018 at 4:13 PM Boris Brezillon
wrote:
>
> On Fri, 26 Oct 2018 15:36:15 +0200
> Daniel Vetter wrote:
>
> > On Fri, Oct 26, 2018 at 02:36:56PM +0200, Boris Brezillon wrote:
> > > Hi Daniel,
> > >
> > > On Fri, 26 Oct 2018 12:33:37 +0200
> > > Daniel Vetter wrote:
> > >
> > > > On
On Fri, 26 Oct 2018 15:36:15 +0200
Daniel Vetter wrote:
> On Fri, Oct 26, 2018 at 02:36:56PM +0200, Boris Brezillon wrote:
> > Hi Daniel,
> >
> > On Fri, 26 Oct 2018 12:33:37 +0200
> > Daniel Vetter wrote:
> >
> > > On Thu, Oct 25, 2018 at 02:45:44PM +0200, Boris Brezillon wrote:
> > > >
On Fri, Oct 26, 2018 at 02:36:56PM +0200, Boris Brezillon wrote:
> Hi Daniel,
>
> On Fri, 26 Oct 2018 12:33:37 +0200
> Daniel Vetter wrote:
>
> > On Thu, Oct 25, 2018 at 02:45:44PM +0200, Boris Brezillon wrote:
> > > Display controllers usually provide a lot features like overlay planes,
> > >
Hi Daniel,
On Fri, 26 Oct 2018 12:33:37 +0200
Daniel Vetter wrote:
> On Thu, Oct 25, 2018 at 02:45:44PM +0200, Boris Brezillon wrote:
> > Display controllers usually provide a lot features like overlay planes,
> > hardware scalers, hardware rotations, ...
> > Most of the time those features
On Thu, Oct 25, 2018 at 02:45:44PM +0200, Boris Brezillon wrote:
> Display controllers usually provide a lot features like overlay planes,
> hardware scalers, hardware rotations, ...
> Most of the time those features work just fine when enabled
> independently, but activating all of them at the
Display controllers usually provide a lot features like overlay planes,
hardware scalers, hardware rotations, ...
Most of the time those features work just fine when enabled
independently, but activating all of them at the same time tend to
show other limitations like the limited memory bus or
