From: Steven J Abner <pheonix.sja@att.net>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: Kernels >= 6.3 disable video output
Date: Mon, 12 May 2025 16:07:26 -0400 [thread overview]
Message-ID: <EWZ5WS.K2DTZM5DEZCL2@att.net> (raw)
In-Reply-To: <1Q10WS.BHBZBX486I3M2@att.net>
On Fri, May 9 2025 at 03:01:13 PM +0000, Steven J Abner
<pheonix.sja@att.net> wrote:
> On Fri, May 9 2025 at 02:05:16 PM +0000, Alex Deucher
> <alexdeucher@gmail.com> wrote:
>> bisect between 6.2.16 and 6.2.17 to identify the commit which broke
>
> Are you asking for a 'diff' output of drm and amdgpu directories
> between 6.2.16 (last of the 6.2 series) and 6.3 (start of the 6.3
> series)?
I'm willing to revert/test code on my machine, problem is I don't know
sequence nor what I can safely revert. I haven't messed with video
drivers/code since DOS days of having to write ones own graphics
routines. I could force? kernel to build with '-g' on drm/amdgpu? and
walk it I guess. But don't know what I'm looking for. :(
Steve
next prev parent reply other threads:[~2025-05-13 8:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6DWYVS.BXJ4YUZ0KN5B3.ref@att.net>
2025-05-09 0:07 ` Kernels >= 6.3 disable video output Steven J Abner
2025-05-09 13:11 ` Alex Deucher
2025-05-09 13:39 ` Steven J Abner
2025-05-09 14:05 ` Alex Deucher
2025-05-09 14:38 ` Steven J Abner
2025-05-09 15:01 ` Steven J Abner
2025-05-12 20:07 ` Steven J Abner [this message]
2025-05-12 20:10 ` Alex Deucher
2025-05-15 16:11 ` Steven J Abner
2025-05-15 16:16 ` Alex Deucher
2025-05-15 17:59 ` Harry Wentland
2025-05-15 18:42 ` Steven J Abner
2025-05-16 15:02 ` Michel Dänzer
2025-05-16 15:38 ` Steven J Abner
2025-05-16 15:56 ` Steven J Abner
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=EWZ5WS.K2DTZM5DEZCL2@att.net \
--to=pheonix.sja@att.net \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox