mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: "Lee, Alvin" <Alvin.Lee2@amd.com>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	"Wheeler, Daniel" <Daniel.Wheeler@amd.com>,
	"Wu, Hersen" <hersenxs.wu@amd.com>,
	"Mahfooz, Hamza" <Hamza.Mahfooz@amd.com>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Subject: Re: regression/bisected/6.7rc1: Instead of desktop I see a horizontal flashing bar with a picture of the desktop background on white screen
Date: Thu, 16 Nov 2023 11:46:58 +0100	[thread overview]
Message-ID: <99ef9596-d4f8-49e2-acbe-ed7486310f84@amd.com> (raw)
In-Reply-To: <CABXGCsNpEh7GjFPvx=rz6ZeB7Kx4iqV-e8HyFKyhNau2S5gENw@mail.gmail.com>

Am 15.11.23 um 21:08 schrieb Mikhail Gavrilov:
> On Wed, Nov 15, 2023 at 11:39 PM Lee, Alvin <Alvin.Lee2@amd.com> wrote:
>> This change has a DMCUB dependency - are you able to update your DMCUB version as well?
>>
> I can confirm this issue was gone after updating firmware.
>
> ❯ dmesg | grep DMUB
> [   11.496679] [drm] Loading DMUB firmware via PSP: version=0x07002300
> [   12.000314] [drm] DMUB hardware initialized: version=0x07002300
>

Mhm, that's a quite ugly problem.

The driver is supposed to work with older firmware as well or at least 
issue a warning and provide a reasonable fallback.

How are we going to handle this?

Thanks,
Christian.

  reply	other threads:[~2023-11-16 10:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 10:55 Mikhail Gavrilov
2023-11-14 18:03 ` Mikhail Gavrilov
2023-11-15 18:10   ` Mikhail Gavrilov
2023-11-15 18:14     ` Hamza Mahfooz
2023-11-15 18:22       ` Mikhail Gavrilov
2023-11-15 18:39         ` Lee, Alvin
2023-11-15 20:08           ` Mikhail Gavrilov
2023-11-16 10:46             ` Christian König [this message]
2023-11-26 14:40               ` Linux regression tracking (Thorsten Leemhuis)
2023-11-27 18:11           ` Alex Deucher
2023-12-05 13:23             ` Linux regression tracking (Thorsten Leemhuis)
2023-12-11  7:30               ` Thorsten Leemhuis
2023-11-18 14:25 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-12-15 16:14 ` Hamza Mahfooz
2023-12-17 21:39   ` Mikhail Gavrilov
2023-12-19 17:01     ` Alex Deucher

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=99ef9596-d4f8-49e2-acbe-ed7486310f84@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Alvin.Lee2@amd.com \
    --cc=Daniel.Wheeler@amd.com \
    --cc=Hamza.Mahfooz@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=hersenxs.wu@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikhail.v.gavrilov@gmail.com \
    /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

all inboxes | Powered by JetHome®