[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0425d2f4-a859-46c7-b184-e32efe7165a2@redhat.com>
Date: Mon, 4 Jul 2022 14:22:32 +0200
From: Javier Martinez Canillas <javierm@...hat.com>
To: Xi Ruoyao <xry111@...uxfromscratch.org>,
Zack Rusin <zackr@...are.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: "linux-fbdev@...r.kernel.org" <linux-fbdev@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"deller@....de" <deller@....de>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
Linux-graphics-maintainer <Linux-graphics-maintainer@...are.com>,
"kraxel@...hat.com" <kraxel@...hat.com>,
"tzimmermann@...e.de" <tzimmermann@...e.de>,
"daniel.vetter@...ll.ch" <daniel.vetter@...ll.ch>,
"lersek@...hat.com" <lersek@...hat.com>
Subject: Re: [PATCH v6 3/5] fbdev: Disable sysfb device registration when
removing conflicting FBs
On 7/4/22 14:11, Xi Ruoyao wrote:
> On Mon, 2022-07-04 at 13:04 +0200, Javier Martinez Canillas wrote:
>> Hello Xi,
>>>
>>> With CONFIG_SYSFB_SIMPLEFB and CONFIG_FB_SIMPLE enabled, there is no
>>> issue.
>>>
>>> I guess it's something going wrong on a "drm -> drm" pass over. For now
>>> I'll continue to use simpledrm with this commit reverted.
>>>
>>
>> Yes, we need to also cherry-pick b84efa28a48 ("drm/aperture: Run fbdev
>> removal before internal helpers") now that the sysfb_disable() patches
>> are in v5.19-rc5.
>
> I confirm that cherry-picking b84efa28a48 fixes the issue for v5.19-rc5.
>
Thanks for testing it! Thomas is getting that patch through the drm-fixes
path, so it should make it to the v5.19-rc cycle at some point.
--
Best regards,
Javier Martinez Canillas
Linux Engineering
Red Hat
Powered by blists - more mailing lists