We already track the memory ranges in drm aperture helpers. We'd need to
move the code to a more prominent location (e.g., <linux/aperture.h>)
and change fbdev to use it. Sysfb and DT code needs to insert platform
devices upon creation. We can then implement the more fancy stuff, such
as tracking native-device memory. (And if we ever get to fix all usage
of Linux' request-mem-region, we can even move all the functionality there).
Agreed. And as mentioned, the race that these patches attempt to fix are for
the less common case when a native driver probes but either no generic driver
registered a framebuffer yet or the platform device wasn't registered yet.
But this can only happen if for example a native driver is built-in but the
generic driver is build as a module, which is not the common configuration.
What most distros do is the opposite, to have {simple,of,efi,vesa}fb or
simpledrm built-in and the native drivers built as modules.
So there's no rush to fix this by piling more hacks on top of the ones we
already have and instead try to fix it more properly as you suggested.
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature