From: Peter Mattern <pmattern@arcor.de>
To: dri-devel@lists.freedesktop.org
Subject: Re: drm/vc4: module dysfunctional on Raspberry Pi 3B as of 5.18.0
Date: Thu, 9 Jun 2022 15:37:09 +0200 [thread overview]
Message-ID: <a65f93bd-e45b-c074-b7b8-390df0b02a4b@arcor.de> (raw)
In-Reply-To: <20220609092351.t2muybqjnqaqzemz@houat>
> Could you start a bisection maybe?
I for one am having two issues here.
The harmless one is that I'm lacking a cooler for the RPi and my cross
compiling skills have become a bit rusty.
Both could be fixed quickly, of course.
The not so harmless one is that kernel 5.18.x is completely unusable due
to an other regression: the SD card is slow to a degree that makes it
rather unusable, rather simple tasks are tainting the kernel because of
this. E. g. a simple kernel update takes half an hour on 5.18.x.
Neither sure what's the culprit here nor how to deal with it.
Nonetheless:
Could the module be installed without updating the kernel as a whole, e.
g.by DKMS?
Is there a way to narrow down the commits in question, e. g. something
like 'git log ./drivers/gpu/drm/vc4/' in a Git checkout of the kernel
sources?
next prev parent reply other threads:[~2022-06-09 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 18:01 drm/vc4: module dysfunctional on Raspberry Pi 3B as of 5.18.0 Peter Mattern
2022-06-08 13:10 ` Peter Robinson
2022-06-08 14:36 ` Maxime Ripard
2022-06-08 15:14 ` Peter Robinson
2022-06-08 15:36 ` Maxime Ripard
2022-06-09 9:23 ` Maxime Ripard
2022-06-09 11:49 ` Peter Robinson
2022-06-09 13:37 ` Peter Mattern [this message]
2022-06-08 22:47 ` Stefan Wahren
2022-06-09 11:52 ` Peter Robinson
2022-06-09 21:33 ` Stefan Wahren
2022-06-10 20:06 ` Stefan Wahren
2022-06-10 22:02 ` Peter Robinson
2022-06-09 13:08 ` Peter Mattern
2022-06-05 23:57 Stefan Wahren
2022-06-09 12:49 Peter Mattern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a65f93bd-e45b-c074-b7b8-390df0b02a4b@arcor.de \
--to=pmattern@arcor.de \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.