Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> writes: > Hi Arnd, > [...] >> >> That would leave CONFIG_FB_DEVICE as the only user visible option >> for DRM-only configs, which is slightly odd for the menuconfig, >> so I still wonder if that could be done differently. >> >> Is there actually a point in configurations for kernels with FB=y, >> DRM=n and FB_DEVICE=n? If we don't expect that to be a useful >> configuration, an easier way would be to have CONFIG_FB turn it >> on implicitly and instead have a user-visible Kconfig option >> below CONFIG_DRM_FBDEV_EMULATION that allows controlling the >> creation of /dev/fb*. > > Such a combination would allow the user to still have a text console > on a legacy fbdev, while not having to worry about possible security > ramifications of providing fbdev userspace access. > Exactly, it may be a possible combination. Not sure how useful what would be in practice but we shouldn't restrict that IMO. -- Best regards, Javier Martinez Canillas Core Platforms Red Hat
