[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <61f2e4e2af40cb9d853504d0a6fe01829ff8ca60.camel@linuxfromscratch.org>
Date: Mon, 04 Jul 2022 18:29:00 +0800
From: Xi Ruoyao <xry111@...uxfromscratch.org>
To: Javier Martinez Canillas <javierm@...hat.com>,
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 Mon, 2022-07-04 at 17:36 +0800, Xi Ruoyao wrote:
> > Yes, please do. Either with CONFIG_SYSFB_SIMPLEFB disabled and CONFIG_FB_EFI
> > enabled (so that "efi-framebuffer" is registered and efifb probed) or with
> > CONFIG_SYSFB_SIMPLEFB but CONFIG_FB_SIMPLE enabled (so "simple-framebuffer
> > is used too but with simplefb instead of simpledrm).
> >
> > I'm not able to reproduce, it would be useful to have another data point.
>
> Also happening for me with CONFIG_SYSFB_SIMPLEFB, on a Intel Core i7-
> 1065G7 (with iGPU).
>
> Reverting this commit on top of 5.19-rc5 "fixes" the issue.
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.
Powered by blists - more mailing lists