On Mon, Oct 25, 2021 at 06:54:34PM +0200, Sam Ravnborg wrote:
> Hi Maxime,
>
> On Mon, Oct 25, 2021 at 05:16:36PM +0200, Maxime Ripard wrote:
> > Hi Sam,
> >
> > On Thu, Oct 21, 2021 at 05:22:55PM +0200, Sam Ravnborg wrote:
> > > Hi Maxime,
> > >
> > > > Let me know what you think,
> > >
> > >
Hi Maxime,
On Mon, Oct 25, 2021 at 05:16:36PM +0200, Maxime Ripard wrote:
> Hi Sam,
>
> On Thu, Oct 21, 2021 at 05:22:55PM +0200, Sam Ravnborg wrote:
> > Hi Maxime,
> >
> > > Let me know what you think,
> >
> > apply the lot to drm-misc-next. Maybe wait for an r-b or a-b on the kirin
> > patch
Hi Sam,
On Thu, Oct 21, 2021 at 05:22:55PM +0200, Sam Ravnborg wrote:
> Hi Maxime,
>
> > Let me know what you think,
>
> apply the lot to drm-misc-next. Maybe wait for an r-b or a-b on the kirin
> patch but the rest is IMO good to go.
I had a compilation error since the rebase of the v4, so I s
Hi Maxime,
> Let me know what you think,
apply the lot to drm-misc-next. Maybe wait for an r-b or a-b on the kirin
patch but the rest is IMO good to go.
Sam
Hi,
We've encountered an issue with the RaspberryPi DSI panel that prevented the
whole display driver from probing.
The issue is described in detail in the commit 7213246a803f ("drm/vc4: dsi:
Only register our component once a DSI device is attached"), but the basic idea
is that since the panel i
