Unverified Commit 92ba6734 authored by Sui Jingfeng's avatar Sui Jingfeng Committed by Javier Martinez Canillas
Browse files

video/aperture: Fix typos in comments 



EFI FB, VESA FB or VGA FB etc belong to firmware based framebuffer driver.

Signed-off-by: default avatarSui Jingfeng <suijingfeng@loongson.cn>
Reviewed-by: default avatarJavier Martinez Canillas <javierm@redhat.com>
Signed-off-by: default avatarJavier Martinez Canillas <javierm@redhat.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230404040101.2165600-1-suijingfeng@loongson.cn
parent 3e66f493

drivers/video/aperture.c

+4 −4
Original line number Diff line number Diff line
@@ -20,7 +20,7 @@ 
 * driver can be active at any given time. Many systems load a generic

 * graphics drivers, such as EFI-GOP or VESA, early during the boot process.

 * During later boot stages, they replace the generic driver with a dedicated,

 * hardware-specific driver. To take over the device the dedicated driver

 * hardware-specific driver. To take over the device, the dedicated driver

 * first has to remove the generic driver. Aperture functions manage

 * ownership of framebuffer memory and hand-over between drivers.

 *
@@ -203,7 +203,7 @@ static void aperture_detach_platform_device(struct device *dev) 


	/*

	 * Remove the device from the device hierarchy. This is the right thing

	 * to do for firmware-based DRM drivers, such as EFI, VESA or VGA. After

	 * to do for firmware-based fb drivers, such as EFI, VESA or VGA. After

	 * the new driver takes over the hardware, the firmware device's state

	 * will be lost.

	 *