Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

Andy Shevchenko writes: > On Fri, Jun 30, 2023 at 10:29:20PM +0200, Javier Martinez Canillas wrote: >> Andy Shevchenko writes: >> > On Fri, Jun 30, 2023 at 07:38:01PM +0200, Javier Martinez Canillas wrote: >> >> Andy Shevchenko writes: >> >> > On Fri, Jun 30, 2023 at 12:51:02AM +0200, Javier Ma

Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

On Fri, Jun 30, 2023 at 10:29:20PM +0200, Javier Martinez Canillas wrote: > Andy Shevchenko writes: > > On Fri, Jun 30, 2023 at 07:38:01PM +0200, Javier Martinez Canillas wrote: > >> Andy Shevchenko writes: > >> > On Fri, Jun 30, 2023 at 12:51:02AM +0200, Javier Martinez Canillas wrote: > >> >> T

Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

On Fri, Jun 30, 2023, at 13:19, Thomas Zimmermann wrote: > Am 30.06.23 um 00:51 schrieb Javier Martinez Canillas: >> 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 havi

Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

Andy Shevchenko writes: > On Fri, Jun 30, 2023 at 07:38:01PM +0200, Javier Martinez Canillas wrote: >> Andy Shevchenko writes: >> > 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 >> >> symbo

Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

On Fri, Jun 30, 2023 at 08:42:21PM +0300, Andy Shevchenko wrote: > On Fri, Jun 30, 2023 at 07:38:01PM +0200, Javier Martinez Canillas wrote: > > Andy Shevchenko writes: > > > On Fri, Jun 30, 2023 at 12:51:02AM +0200, Javier Martinez Canillas wrote: ... > > >> The reason for doing this is that no

Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

On Fri, Jun 30, 2023 at 07:38:01PM +0200, Javier Martinez Canillas wrote: > Andy Shevchenko writes: > > 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 motivati

Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

Andy Shevchenko writes: Hello Andy, > 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 hav

Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

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 th

Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

Hi Am 30.06.23 um 14:33 schrieb Javier Martinez Canillas: Thomas Zimmermann writes: Hello Thomas, Thanks a lot for your review. Hi Javier Am 30.06.23 um 00:51 schrieb Javier Martinez Canillas: This patch series splits the fbdev core support in two different Kconfig symbols: FB and FB_CORE

Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

Thomas Zimmermann writes: Hello Thomas, Thanks a lot for your review. > Hi Javier > > Am 30.06.23 um 00:51 schrieb Javier Martinez Canillas: >> 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 >

Re: [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

Hi Javier Am 30.06.23 um 00:51 schrieb Javier Martinez Canillas: 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

[PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation

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 disa