On Tue, 23 Jan 2024, Jani Nikula wrote:
> On Tue, 23 Jan 2024, Thomas Zimmermann wrote:
>> This reverts commit 60aebc9559492cea6a9625f514a8041717e3a2e4.
>>
>> Commit 60aebc9559492cea ("drivers/firmware: Move sysfb_init() from
>> device_initcall to subsys_initcall_sync") messes up initialization
On Tue, 23 Jan 2024, Thomas Zimmermann wrote:
> This reverts commit 60aebc9559492cea6a9625f514a8041717e3a2e4.
>
> Commit 60aebc9559492cea ("drivers/firmware: Move sysfb_init() from
> device_initcall to subsys_initcall_sync") messes up initialization order
> of the graphics drivers and leads to
Thomas Zimmermann writes:
> This reverts commit 60aebc9559492cea6a9625f514a8041717e3a2e4.
>
> Commit 60aebc9559492cea ("drivers/firmware: Move sysfb_init() from
> device_initcall to subsys_initcall_sync") messes up initialization order
> of the graphics drivers and leads to blank displays on
Hi
Am 23.01.24 um 14:12 schrieb Huacai Chen:
I'm very sorry to hear that, If Jaak can respond, I think I can find
the root cause and fix that...
No problem, don't worry. We wanted to revert that patch anyway. And the
*real* fix here is to track the framebuffer ownership more closely.
Best
I'm very sorry to hear that, If Jaak can respond, I think I can find
the root cause and fix that...
Huacai
On Tue, Jan 23, 2024 at 8:09 PM Thomas Zimmermann wrote:
>
> This reverts commit 60aebc9559492cea6a9625f514a8041717e3a2e4.
>
> Commit 60aebc9559492cea ("drivers/firmware: Move sysfb_init()
This reverts commit 60aebc9559492cea6a9625f514a8041717e3a2e4.
Commit 60aebc9559492cea ("drivers/firmware: Move sysfb_init() from
device_initcall to subsys_initcall_sync") messes up initialization order
of the graphics drivers and leads to blank displays on some systems. So
revert the commit.
To