[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
https://bugzilla.suse.com/show_bug.cgi?id=1204315
https://bugzilla.suse.com/show_bug.cgi?id=1204315#c20
--- Comment #20 from Takashi Iwai
(In reply to Takashi Iwai from comment #17)
Then maybe better to have as Kconfig dependency, e.g.
--- a/drivers/gpu/drm/tiny/Kconfig +++ b/drivers/gpu/drm/tiny/Kconfig @@ -69,6 +69,7 @@ config DRM_PANEL_MIPI_DBI config DRM_SIMPLEDRM tristate "Simple framebuffer driver" depends on DRM && MMU + depends on SYSFB=n select APERTURE_HELPERS select DRM_GEM_SHMEM_HELPER select DRM_KMS_HELPER
Why? It has nothing to do with the driver.
Then how would you "fix" it in the upstream side? It shouldn't rely on the random kconfig choice done by user. (In reply to Thomas Zimmermann from comment #19)
(In reply to Thomas Zimmermann from comment #18)
(In reply to Takashi Iwai from comment #17)
Then maybe better to have as Kconfig dependency, e.g.
--- a/drivers/gpu/drm/tiny/Kconfig +++ b/drivers/gpu/drm/tiny/Kconfig @@ -69,6 +69,7 @@ config DRM_PANEL_MIPI_DBI config DRM_SIMPLEDRM tristate "Simple framebuffer driver" depends on DRM && MMU + depends on SYSFB=n select APERTURE_HELPERS select DRM_GEM_SHMEM_HELPER select DRM_KMS_HELPER
Why? It has nothing to do with the driver.
It would, BTW, prevent it from being used on x86, etc.
Why x86 still needs sysfb when simpledrmfb is enabled? Do you think of the situation to allow user switching via boot option or such? And, what did you have in mind by "disabling CONFIG_SYSFB"? If it were only about ARM, you can put a restriction in the kconfig, too. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com