drm: remove drivers trying to take the framebuffer

[YusufKhan-gamedev]

Signed-off-by: Yusuf Khan yusisamerican@gmail.com

[mtijanic]

Hey, just a heads up, this isn't being ignored, it has just stalled while waiting on some of our key engineers to become available. The few of us that do have the bandwidth don't have enough domain expertise to understand all the implications.

Someone will hopefully get to this soon enough. Thanks for the patience!

[muellerjoel]

I used with ArchLinux Kernel 5.19.11 and nvidia-open-git-dkms package and didn’t fix me issue with the framebuffer

[TheDevMinerTV]

Found a typo

[TheDevMinerTV]

Suggested change

	/* Linux 6.0-rc1 has this, the drm apreture func wraps this */
	/* Linux 6.0-rc1 has this, the drm aperture function wraps this */

[vars1ty]

It's been almost an entire year, how is this still not merged? Surely there has been enough time for people to look at it (and other PRs).

[aaronp24]

It's been almost an entire year, how is this still not merged? Surely there has been enough time for people to look at it (and other PRs).

I don't think this can be merged as-is, since in addition to removing conflicting drivers such as nouveau, it will also remove important drivers such as efifb or vesafb. I think removing those without replacing the console will cause the console to stop working completely.

I have a series of changes to add support for framebuffer consoles, similar to #342 but integrated with the rest of the driver. In that change, the driver calls drm_aperture_remove_conflicting_pci_framebuffers only if it is installing its own framebuffer console. I'll close this pull request once a driver with those changes is released.