Hot-unplug all firmware-framebuffer devices as part of removing them via remove_conflicting_framebuffers() et al. Releases all memory regions to be acquired by native drivers. Firmware, such as EFI, install a framebuffer while posting the computer. After removing the firmware-framebuffer device from fbdev, a native driver takes over the hardware and the firmware framebuffer becomes invalid. Firmware-framebuffer drivers, specifically simplefb, don't release their device from Linux' device hierarchy. It still owns the firmware framebuffer and blocks the native drivers from loading. This has been observed in the vmwgfx driver. [1] Initiating a device removal (i.e., hot unplug) as part of remove_conflicting_framebuffers() removes the underlying device and returns the memory range to the system. [1] https://lore.kernel.org/dri-devel/20220117180359.18114-1-zack@kde.org/ v2: * rename variable 'dev' to 'device' (Javier)
Showing the changes to include (1 of 2 files). Show all
Unified · Split
| @@ -502,6 +502,7 @@ struct fb_info { · 501 unmodified lines | ||
| 502 | 502 | } *apertures; |
| 503 | 503 | |
| 504 | 504 | bool skip_vt_switch; /* no VT switch on suspend/resume required */ |
| 505 | + bool forced_out; /* set when being removed by another driver */ | |
| 505 | 506 | }; |
| 506 | 507 | |
| 507 | 508 | static inline struct apertures_struct *alloc_apertures(unsigned int max_num) { |