Hi Daniel,
On Wed, Aug 14, 2019 at 05:01:31PM +0200, Daniel Vetter wrote:
> On Thu, Aug 08, 2019 at 10:48:43PM +0300, Laurent Pinchart wrote:
> > On Thu, Jul 18, 2019 at 07:01:03PM +0200, Daniel Vetter wrote:
> >> On Sun, Jul 07, 2019 at 09:19:02PM +0300, Laurent Pinchart wrote:
> >>> Most bridge
Hi Laurent,
On Thu, Aug 08, 2019 at 10:48:43PM +0300, Laurent Pinchart wrote:
> Hi Daniel,
>
> On Thu, Jul 18, 2019 at 07:01:03PM +0200, Daniel Vetter wrote:
> > On Sun, Jul 07, 2019 at 09:19:02PM +0300, Laurent Pinchart wrote:
> > > Most bridge drivers create a DRM connector to model the
Hi Daniel,
On Thu, Jul 18, 2019 at 07:01:03PM +0200, Daniel Vetter wrote:
> On Sun, Jul 07, 2019 at 09:19:02PM +0300, Laurent Pinchart wrote:
> > Most bridge drivers create a DRM connector to model the connector at the
> > output of the bridge. This model is historical and has worked pretty
> >
On Sun, Jul 07, 2019 at 09:19:02PM +0300, Laurent Pinchart wrote:
> Most bridge drivers create a DRM connector to model the connector at the
> output of the bridge. This model is historical and has worked pretty
> well so far, but causes several issues:
>
> - It prevents supporting more complex
Most bridge drivers create a DRM connector to model the connector at the
output of the bridge. This model is historical and has worked pretty
well so far, but causes several issues:
- It prevents supporting more complex display pipelines where DRM
connector operations are split over multiple
