From: Javier Martinez Canillas <javierm@redhat.com>
To: Ilya Trukhanov <lahvuun@gmail.com>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev,
linux-efi@vger.kernel.org, linux-pm@vger.kernel.org,
tzimmermann@suse.de, ardb@kernel.org, rafael@kernel.org,
len.brown@intel.com, pavel@ucw.cz,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [REGRESSION]: drivers/firmware: move x86 Generic System Framebuffers support
Date: Thu, 11 Nov 2021 12:13:09 +0100 [thread overview]
Message-ID: <1b6c6fbe-0b20-95e7-c1ed-bc2b2c13c044@redhat.com> (raw)
In-Reply-To: <20211111105232.apk2msip4ng7hgsw@lahvuun>
Hello Ilya,
On 11/11/21 11:52, Ilya Trukhanov wrote:
> On Thu, Nov 11, 2021 at 10:24:56AM +0100, Javier Martinez Canillas wrote:
>> On 11/11/21 08:31, Javier Martinez Canillas wrote:
>>
>> [snip]
>>
>>>>> And for each check /proc/fb, the kernel boot log, and if Suspend-to-RAM works.
>>>>>
>>>>> If the explanation above is correct, then I would expect (1) and (2) to work and
>>>>> (3) to also fail.
>>>>>
>>>
>>> Your testing confirms my assumptions. I'll check how this could be solved to
>>> prevent the efifb driver to be probed if there's already a framebuffer device.
>>>
>>
>> I've posted [0] which does this and also for the simplefb driver.
>>
>> [0]: https://lore.kernel.org/dri-devel/20211111092053.1328304-1-javierm@redhat.com/T/#u
>
> I applied the patch and it fixes the issue for me.
> Thank you!
>
Great! And thanks for tracking this down.
Feel free to add your Tested-by to v2.
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
prev parent reply other threads:[~2021-11-11 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 20:02 [REGRESSION]: drivers/firmware: move x86 Generic System Framebuffers support Ilya Trukhanov
2021-11-10 22:24 ` Ard Biesheuvel
2021-11-10 23:21 ` Ilya Trukhanov
2021-11-10 23:25 ` Ard Biesheuvel
2021-11-11 0:08 ` Ilya Trukhanov
2021-11-10 23:07 ` Javier Martinez Canillas
2021-11-11 0:45 ` Ilya Trukhanov
2021-11-11 7:31 ` Javier Martinez Canillas
2021-11-11 9:24 ` Javier Martinez Canillas
2021-11-11 10:52 ` Ilya Trukhanov
2021-11-11 11:13 ` Javier Martinez Canillas [this message]
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=1b6c6fbe-0b20-95e7-c1ed-bc2b2c13c044@redhat.com \
--to=javierm@redhat.com \
--cc=ardb@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lahvuun@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).