mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Arnd Bergmann <arnd@kernel.org>
Cc: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"David Airlie" <airlied@gmail.com>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Helge Deller" <deller@gmx.de>, "Arnd Bergmann" <arnd@arndb.de>,
	"Christian König" <christian.koenig@amd.com>,
	"Dave Airlie" <airlied@redhat.com>,
	"Javier Martinez Canillas" <javierm@redhat.com>,
	"Jim Cromie" <jim.cromie@gmail.com>,
	"Sam Ravnborg" <sam@ravnborg.org>,
	"Arthur Grillo" <arthurgrillo@riseup.net>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] drm: fix up fbdev Kconfig defaults
Date: Tue, 12 Sep 2023 10:11:43 +0200	[thread overview]
Message-ID: <637afb25-8ee2-4188-9385-27ee6a97ec59@suse.de> (raw)
In-Reply-To: <CAMuHMdWizKkuLEcv8sFFOWPib-0e1onCRuQEZm6OhV592VWUKQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3015 bytes --]

Hi

Am 12.09.23 um 09:14 schrieb Geert Uytterhoeven:
[...]
>> --- a/drivers/gpu/drm/Kconfig
>> +++ b/drivers/gpu/drm/Kconfig
>> @@ -135,7 +135,7 @@ config DRM_FBDEV_EMULATION
>>          bool "Enable legacy fbdev support for your modesetting driver"
>>          depends on DRM
>>          select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
>> -       default y
>> +       default FB
> 
> While this is true for existing configs, it is no longer true in general,
> as DRM_FBDEV_EMULATION is no longer related to FB.

Would it make sense to make FRAMEBUFFER_CONSOLE an independent option 
and have FBDEV_EMULATION depend on it? Something like this:

FRAMEBUFFER_CONSOLE
	depends on DRM || FB
	select FB_CORE

FBDEV_EMULATION
	depends on DRM
	depends on FRAMEBUFFER_CONSOLE
	default y

So if any graphics subsystems are enabled, FRAMEBUFFER_CONSOLE is 
select-able. But for DRM, FBDEV_EMULATION disables the console. That 
option remains more for historical reasons than actual usefulness.

Best regards
Thomas

> 
>>          help
>>            Choose this option if you have a need for the legacy fbdev
>>            support. Note that this support also provides the linux console
>> diff --git a/drivers/video/console/Kconfig b/drivers/video/console/Kconfig
>> index b575cf54174af..83c2d7329ca58 100644
>> --- a/drivers/video/console/Kconfig
>> +++ b/drivers/video/console/Kconfig
>> @@ -74,6 +74,7 @@ config DUMMY_CONSOLE_ROWS
>>   config FRAMEBUFFER_CONSOLE
>>          bool "Framebuffer Console support"
>>          depends on FB_CORE && !UML
>> +       default DRM_FBDEV_EMULATION
> 
> Sounds good to me, although it looks a bit strange at first sight
> (FRAMEBUFFER_CONSOLE defaults to n on a system with real fbdev, but
> y on emulated fbdev?).
> So this is the fix for commit a5ae331edb02b ("drm: Drop select
> FRAMEBUFFER_CONSOLE for DRM_FBDEV_EMULATION").
> 
>>          select VT_HW_CONSOLE_BINDING
>>          select CRC32
>>          select FONT_SUPPORT
>> diff --git a/drivers/video/fbdev/core/Kconfig b/drivers/video/fbdev/core/Kconfig
>> index 114cb8aa6c8fd..804c2bec9b43c 100644
>> --- a/drivers/video/fbdev/core/Kconfig
>> +++ b/drivers/video/fbdev/core/Kconfig
>> @@ -28,7 +28,7 @@ config FIRMWARE_EDID
>>   config FB_DEVICE
>>          bool "Provide legacy /dev/fb* device"
>>          depends on FB_CORE
>> -       default y
>> +       default FB
> 
> Changing this means possibly causing regressions on systems running
> an fbdev userspace.
> 
>>          help
>>            Say Y here if you want the legacy /dev/fb* device file and
>>            interfaces within sysfs anc procfs. It is only required if you
> 
> Gr{oetje,eeting}s,
> 
>                          Geert
> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  parent reply	other threads:[~2023-09-12  8:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 20:52 Arnd Bergmann
2023-09-12  5:00 ` Javier Martinez Canillas
2023-09-12  7:14 ` Geert Uytterhoeven
2023-09-12  7:39   ` Arnd Bergmann
2023-09-12  7:50     ` Geert Uytterhoeven
2023-09-12  7:55     ` Javier Martinez Canillas
2023-09-12  7:48   ` Javier Martinez Canillas
2023-09-12  7:53     ` Geert Uytterhoeven
2023-09-12  7:58     ` Arnd Bergmann
2023-09-12  8:11   ` Thomas Zimmermann [this message]
2023-09-12  8:18     ` Geert Uytterhoeven
2023-09-12  8:38       ` Thomas Zimmermann
2023-09-12  8:50         ` Geert Uytterhoeven
2023-09-12  9:04       ` Arnd Bergmann
2023-09-18  7:25 ` Thomas Zimmermann
2023-09-18  8:57   ` 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=637afb25-8ee2-4188-9385-27ee6a97ec59@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=arthurgrillo@riseup.net \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=javierm@redhat.com \
    --cc=jim.cromie@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®