Hi Maxime,
maxime at cerno.tech (Maxime Ripard) writes:
> I'm not entirely sure what you expect by insisting on things getting
> broken *again*, but we got it, thanks.
I wanted to remind of the previous issue, which had the same symptoms,
and hence might be related and helpful in debugging.
Upon
Hello again,
I am facing the exact same symptoms as last September:
https://lists.freedesktop.org/archives/dri-devel/2021-September/324008.html
…meaning my (headless) Raspberry Pi 3 B and Raspberry Pi 3 B+ no longer
boot with Linux 5.16.3, while the (headless) Raspberry Pi 4 still boots.
This is
-Revert-drm-vc4-hdmi-Move-the-HSM-clock-enable-to-run.patch
On Sun, 19 Sept 2021 at 00:13, Linus Torvalds
wrote:
>
> On Sat, Sep 18, 2021 at 1:13 PM Michael Stapelberg
> wrote:
> >
> > > Michael - do things work if you revert those two (sadly, they don't
> > &g
On Sat, 18 Sept 2021 at 21:24, Linus Torvalds
wrote:
>
> On Sat, Sep 18, 2021 at 2:18 AM Michael Stapelberg
> wrote:
> >
> > torvalds at linux-foundation.org (Linus Torvalds) writes:
> > > Did I fix it up correctly? Who knows. The code makes more sense to me
&g
Hi,
torvalds at linux-foundation.org (Linus Torvalds) writes:
> Did I fix it up correctly? Who knows. The code makes more sense to me
> now and seems valid. But I really *really* want to stress how locking
> is important.
As far as I can tell, this merge conflict resolution made my Raspberry
Pi 3
