Hi
Am 12.04.21 um 12:41 schrieb Jani Nikula:
On Mon, 12 Apr 2021, Thomas Zimmermann wrote:
Hi
Am 12.04.21 um 11:36 schrieb Jani Nikula:
Please test the documentation build before applying.
I did and I'm pretty sure it looked correct. But I'll double check.
Cool, maybe someone added more
On Mon, 12 Apr 2021, Thomas Zimmermann wrote:
> Hi
>
> Am 12.04.21 um 11:36 schrieb Jani Nikula:
>> Please test the documentation build before applying.
>
> I did and I'm pretty sure it looked correct. But I'll double check.
Cool, maybe someone added more smarts to kernel-doc. :)
BR,
Jani.
--
Hi
Am 12.04.21 um 11:36 schrieb Jani Nikula:
On Mon, 12 Apr 2021, Thomas Zimmermann wrote:
+ * DRM drivers should call drm_aperture_remove_conflicting_framebuffers()
+ * at the top of their probe function. The function removes any generic
+ * driver that is currently associated with the given
On Mon, 12 Apr 2021, Thomas Zimmermann wrote:
> + * DRM drivers should call drm_aperture_remove_conflicting_framebuffers()
> + * at the top of their probe function. The function removes any generic
> + * driver that is currently associated with the given framebuffer memory.
> + * If the framebuffe
Platform devices might operate on firmware framebuffers, such as VESA
or EFI. Before a native driver for the graphics hardware can take over
the device, it has to remove any platform driver that operates on the
firmware framebuffer. Aperture helpers provide the infrastructure for
native drivers to
