On Thu, 31 Jul 2025 03:11:15 + pr-tracker-...@kernel.org wrote:
>
> The pull request you sent on Wed, 30 Jul 2025 07:05:51 +1000:
>
> > https://gitlab.freedesktop.org/drm/kernel.git tags/drm-next-2025-07-30
>
> has been merged into torvalds/linux.git:
> https://git.kernel.org/torvalds/c/260f6f4
On Thu, Jul 31, 2025 at 2:01 PM Linus Torvalds
wrote:
>
> On Thu, 31 Jul 2025 at 06:09, Alex Deucher wrote:
> >
> > I think it may be fixed here:
> > https://patchwork.freedesktop.org/patch/663973/
>
> Yes, this patch fixes the problem for me.
>
> I don't know if it's due to the pointer validatio
On Thu, 31 Jul 2025 at 06:09, Alex Deucher wrote:
>
> I think it may be fixed here:
> https://patchwork.freedesktop.org/patch/663973/
Yes, this patch fixes the problem for me.
I don't know if it's due to the pointer validation (ie this part):
- if (!dsc)
+ if (!dsc || !dsc->ctx || !
On Thu, Jul 31, 2025 at 9:09 AM Alex Deucher wrote:
>
> On Thu, Jul 31, 2025 at 3:03 AM Linus Torvalds
> wrote:
> >
> > On Wed, 30 Jul 2025 at 21:58, Linus Torvalds
> > wrote:
> > >
> > > d7b618bc41ee3d44c070212dff93949702ede997 is the first bad commit
> > > drm/amd/display: Refactor DSC cap
fail any of the DSC checks.
-Dillon
-Original Message-
From: Alex Deucher
Sent: Thursday, July 31, 2025 9:10 AM
To: Linus Torvalds
Cc: Dave Airlie ; Varone, Dillon ;
LIPSKI, IVAN ; Wheeler, Daniel ;
Deucher, Alexander ; Liu, Wenjing
; Simona Vetter ; dri-devel
; LKML
Subject: Re: [gi
On Thu, Jul 31, 2025 at 3:03 AM Linus Torvalds
wrote:
>
> On Wed, 30 Jul 2025 at 21:58, Linus Torvalds
> wrote:
> >
> > d7b618bc41ee3d44c070212dff93949702ede997 is the first bad commit
> > drm/amd/display: Refactor DSC cap calculations
> >
> > Let me go see how painful it is to just revert it
On 7/31/25 10:37 AM, Linus Torvalds wrote:
On Wed, 30 Jul 2025 at 21:58, Linus Torvalds
wrote:
d7b618bc41ee3d44c070212dff93949702ede997 is the first bad commit
drm/amd/display: Refactor DSC cap calculations
Let me go see how painful it is to just revert it from top-of-tree.
So with
On Thu, 31 Jul 2025 at 14:59, Linus Torvalds
wrote:
>
> On Wed, 30 Jul 2025 at 21:48, Linus Torvalds
> wrote:
> >
> > Well, it's one of these:
> >
> > 3f2b24a1ef35 drm/amd/display: Monitor patch to ignore EDID audio SAB check
> > aef3af22a456 drm/amd/display: Add definitions to support DID Ty
On Wed, 30 Jul 2025 at 21:58, Linus Torvalds
wrote:
>
> d7b618bc41ee3d44c070212dff93949702ede997 is the first bad commit
> drm/amd/display: Refactor DSC cap calculations
>
> Let me go see how painful it is to just revert it from top-of-tree.
So with that reverted (didn't require a lot of fixi
On Wed, 30 Jul 2025 at 21:48, Linus Torvalds
wrote:
>
> Well, it's one of these:
>
> 3f2b24a1ef35 drm/amd/display: Monitor patch to ignore EDID audio SAB check
> aef3af22a456 drm/amd/display: Add definitions to support DID Type5
> descriptors
> d7b618bc41ee drm/amd/display: Refactor DSC cap
On Wed, 30 Jul 2025 at 21:36, Dave Airlie wrote:
>
> https://lore.kernel.org/dri-devel/20250717204819.731936-1-mustela@erminea.space/
>
> is the only thing I can see that might not be in the merge.
Well, it's one of these:
3f2b24a1ef35 drm/amd/display: Monitor patch to ignore EDID audio SAB ch
On Thu, 31 Jul 2025 at 14:32, Dave Airlie wrote:
>
> On Thu, 31 Jul 2025 at 14:27, Linus Torvalds
> wrote:
> >
> > On Wed, 30 Jul 2025 at 21:21, Dave Airlie wrote:
> > >
> > > Okay I don't have an rx580, but I have an rx480 which is pretty close,
> > > but it is booting fine with your tree at le
On Thu, 31 Jul 2025 at 14:27, Linus Torvalds
wrote:
>
> On Wed, 30 Jul 2025 at 21:21, Dave Airlie wrote:
> >
> > Okay I don't have an rx580, but I have an rx480 which is pretty close,
> > but it is booting fine with your tree at least, DP and HDMI connected,
> > so it's not widespread AMD breakag
On Wed, 30 Jul 2025 at 21:26, Linus Torvalds
wrote:
>
> The good news is that it's bisecting without any ambiguity. So nowhere
> near as painful as last merge window.
Right now it's in the range 1b556bcc3837..63b8c9fdfb7f.
A few more bisections and I'll have it down to a dozen or fewer commits.
On Wed, 30 Jul 2025 at 21:21, Dave Airlie wrote:
>
> Okay I don't have an rx580, but I have an rx480 which is pretty close,
> but it is booting fine with your tree at least, DP and HDMI connected,
> so it's not widespread AMD breakage, anything in journalctl/dmesg?
The machine doesn't come up far
On Thu, 31 Jul 2025 at 14:03, Linus Torvalds
wrote:
>
> On Wed, 30 Jul 2025 at 20:40, Linus Torvalds
> wrote:
> >
> > I'm very unhappy with the end result, because it just results in a
> > black screen at boot for me. No signal.
>
> It's not something in the merge, and it's not something in my tr
On Wed, 30 Jul 2025 at 20:40, Linus Torvalds
wrote:
>
> I'm very unhappy with the end result, because it just results in a
> black screen at boot for me. No signal.
It's not something in the merge, and it's not something in my tree - I
see the same plain "just a black screen" if I try that commit
On Wed, 30 Jul 2025 at 20:47, Dave Airlie wrote:
>
> Is that the Polaris card still?
Same old boring Radeon RX 580.
lspci calls it "Ellesmere", don't know about the Polaris codename..
Linus
On Wed, 30 Jul 2025 at 20:39, Dave Airlie wrote:
> >
> > But I do think that the drm people are doing actively wrong things
> > with the random cherry-picks back and forth: they cause these
> > conflicts, and I *really* think you should look at maybe using stable
> > fixes branches instead.
> >
>
On Thu, 31 Jul 2025 at 13:41, Linus Torvalds
wrote:
>
> On Wed, 30 Jul 2025 at 20:05, Linus Torvalds
> wrote:
> >
> > Again: I'm not going to guarantee that I got it right. I *think* I did
> > - I'm not feeling particularly unhappy with my merge end result.
>
> I spoke too soon.
>
> I'm very unha
On Wed, 30 Jul 2025 at 20:05, Linus Torvalds
wrote:
>
> Again: I'm not going to guarantee that I got it right. I *think* I did
> - I'm not feeling particularly unhappy with my merge end result.
I spoke too soon.
I'm very unhappy with the end result, because it just results in a
black screen at b
On Thu, 31 Jul 2025 at 13:05, Linus Torvalds
wrote:
>
> ,
>
> On Tue, 29 Jul 2025 at 14:06, Dave Airlie wrote:
> >
> > I've done a pass at merging mostly taking from drm-tip:
> > https://github.com/airlied/linux/tree/drm-next-6.17-rc1-merged
>
> Hmm. My resolution is pretty different, but part of
The pull request you sent on Wed, 30 Jul 2025 07:05:51 +1000:
> https://gitlab.freedesktop.org/drm/kernel.git tags/drm-next-2025-07-30
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/260f6f4fda93c8485c8037865c941b42b9cba5d2
Thank you!
--
Deet-doot-dot, I am a bot.
ht
,
On Tue, 29 Jul 2025 at 14:06, Dave Airlie wrote:
>
> I've done a pass at merging mostly taking from drm-tip:
> https://github.com/airlied/linux/tree/drm-next-6.17-rc1-merged
Hmm. My resolution is pretty different, but part of it is that your
test-merge has a different top-of-tree than the tree
24 matches
Mail list logo
