From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Arnd Bergmann <arnd@arndb.de>, Borislav Petkov <bp@alien8.de>,
Daniel Vetter <daniel@ffwll.ch>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Airlie <airlied@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"H. Peter Anvin" <hpa@zytor.com>, Helge Deller <deller@gmx.de>,
Ingo Molnar <mingo@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Sam Ravnborg <sam@ravnborg.org>,
Thomas Gleixner <tglx@linutronix.de>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation
Date: Fri, 30 Jun 2023 20:31:15 +0300 [thread overview]
Message-ID: <ZJ8RY7ZUlryrPB50@smile.fi.intel.com> (raw)
In-Reply-To: <20230629225113.297512-1-javierm@redhat.com>
On Fri, Jun 30, 2023 at 12:51:02AM +0200, Javier Martinez Canillas wrote:
> This patch series splits the fbdev core support in two different Kconfig
> symbols: FB and FB_CORE. The motivation for this is to allow CONFIG_FB to
> be disabled, while still having the the core fbdev support needed for the
> CONFIG_DRM_FBDEV_EMULATION to be enabled. The motivation is automatically
> disabling all fbdev drivers instead of having to be disabled individually.
>
> The reason for doing this is that now with simpledrm, there's no need for
> the legacy fbdev (e.g: efifb or vesafb) drivers anymore and many distros
How does simpledrm works with earlycon=efi?
> now disable them. But it would simplify the config a lot fo have a single
> Kconfig symbol to disable all fbdev drivers.
>
> I've build tested with possible combinations of CONFIG_FB, CONFIG_FB_CORE,
> CONFIG_DRM_FBDEV_EMULATION and CONFIG_FB_DEVICE symbols set to 'y' or 'n'.
>
> Patch 1/2 makes the CONFIG_FB split that is mentioned above and patch 2/2
> makes DRM fbdev emulation depend on the new FB_CORE symbol instead of FB.
--
With Best Regards,
Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: x86@kernel.org, linux-fbdev@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Helge Deller <deller@gmx.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org, Maxime Ripard <mripard@kernel.org>,
Sam Ravnborg <sam@ravnborg.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
dri-devel@lists.freedesktop.org, "H. Peter Anvin" <hpa@zytor.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation
Date: Fri, 30 Jun 2023 20:31:15 +0300 [thread overview]
Message-ID: <ZJ8RY7ZUlryrPB50@smile.fi.intel.com> (raw)
In-Reply-To: <20230629225113.297512-1-javierm@redhat.com>
On Fri, Jun 30, 2023 at 12:51:02AM +0200, Javier Martinez Canillas wrote:
> This patch series splits the fbdev core support in two different Kconfig
> symbols: FB and FB_CORE. The motivation for this is to allow CONFIG_FB to
> be disabled, while still having the the core fbdev support needed for the
> CONFIG_DRM_FBDEV_EMULATION to be enabled. The motivation is automatically
> disabling all fbdev drivers instead of having to be disabled individually.
>
> The reason for doing this is that now with simpledrm, there's no need for
> the legacy fbdev (e.g: efifb or vesafb) drivers anymore and many distros
How does simpledrm works with earlycon=efi?
> now disable them. But it would simplify the config a lot fo have a single
> Kconfig symbol to disable all fbdev drivers.
>
> I've build tested with possible combinations of CONFIG_FB, CONFIG_FB_CORE,
> CONFIG_DRM_FBDEV_EMULATION and CONFIG_FB_DEVICE symbols set to 'y' or 'n'.
>
> Patch 1/2 makes the CONFIG_FB split that is mentioned above and patch 2/2
> makes DRM fbdev emulation depend on the new FB_CORE symbol instead of FB.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-30 17:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 22:51 [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation Javier Martinez Canillas
2023-06-29 22:51 ` Javier Martinez Canillas
2023-06-29 22:51 ` [PATCH 1/2] fbdev: Split frame buffer support in FB and FB_CORE symbols Javier Martinez Canillas
2023-06-29 22:51 ` Javier Martinez Canillas
2023-06-30 9:01 ` Arnd Bergmann
2023-06-30 9:01 ` Arnd Bergmann
2023-06-30 10:51 ` Javier Martinez Canillas
2023-06-30 10:51 ` Javier Martinez Canillas
2023-06-30 11:34 ` Arnd Bergmann
2023-06-30 11:34 ` Arnd Bergmann
2023-06-30 12:22 ` Javier Martinez Canillas
2023-06-30 12:22 ` Javier Martinez Canillas
2023-06-29 22:51 ` [PATCH 2/2] drm: Make fbdev emulation depend on FB_CORE instead of FB Javier Martinez Canillas
2023-06-29 22:51 ` Javier Martinez Canillas
2023-06-30 11:19 ` [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation Thomas Zimmermann
2023-06-30 11:19 ` Thomas Zimmermann
2023-06-30 12:33 ` Javier Martinez Canillas
2023-06-30 12:33 ` Javier Martinez Canillas
2023-06-30 12:41 ` Thomas Zimmermann
2023-06-30 12:41 ` Thomas Zimmermann
2023-07-01 19:49 ` Arnd Bergmann
2023-07-01 19:49 ` Arnd Bergmann
2023-06-30 17:31 ` Andy Shevchenko [this message]
2023-06-30 17:31 ` Andy Shevchenko
2023-06-30 17:38 ` Javier Martinez Canillas
2023-06-30 17:38 ` Javier Martinez Canillas
2023-06-30 17:42 ` Andy Shevchenko
2023-06-30 17:42 ` Andy Shevchenko
2023-06-30 17:43 ` Andy Shevchenko
2023-06-30 17:43 ` Andy Shevchenko
2023-06-30 20:29 ` Javier Martinez Canillas
2023-06-30 20:29 ` Javier Martinez Canillas
2023-07-03 8:21 ` Andy Shevchenko
2023-07-03 8:21 ` Andy Shevchenko
2023-07-03 8:43 ` Javier Martinez Canillas
2023-07-03 8:43 ` Javier Martinez Canillas
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=ZJ8RY7ZUlryrPB50@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=airlied@gmail.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=daniel@ffwll.ch \
--cc=dave.hansen@linux.intel.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mingo@redhat.com \
--cc=mripard@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=tzimmermann@suse.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.