[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#c24
--- Comment #24 from Thomas Zimmermann
(In reply to Takashi Iwai from comment #22)
The kernel should avoid setting such a known bad config combo, or at least, it should give more useful information at runtime if the known bad kconfig combo must be still applicable.
Wouldn't the best solution be to implement efifb as drm driver? I assume it uses runtime callback hooks beyond just accessing the memory area like simpledrm does.
I considered the idea of implementing some sort of 'efidrm'. It's not really the fix here, but would make the whole situation less confusing.
Also, I would ask to avoid upstream fixes as depending on "ARM" just because we happened to encounter it there - please make it !X86 or whatever applicable. RISC-V, C-Sky or MIPS may well run into similar simple-framebuffer issues.
The term *ERROR* in the bug report is somewhat misleading. There's nothing broken here, there's no loss of functionality. It's a minor problem with how we deal with the framebuffer resource. Is is possible that the ARM EFI stubs create the EFI framebuffer from some other source than the DT's simple-framebuffer node? -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com