On Fri, Feb 15, Haiyang Zhang wrote:
> @@ -508,6 +544,18 @@ static int __init vesafb_init(void)
> int ret;
> char *option = NULL;
>
> +#if IS_ENABLED(CONFIG_HYPERV_FB)
> + /*
> + * On Hyper-V both the emulated and synthetic video devices are
> + * available. To avoid conflicts, we disable vesafb for the emulated
> + * video if hyperv_fb is configured.
> + */
> + if (is_hyperv()) {
> + pr_info("Disabled vesafb on Hyper-V.\n");
> + return -ENODEV;
> + }
> +#endif
What is the reason for this hook? Is it not possible to claim the
display like its appearently done by other drivers (like radeonfb can
take over display from vesafb)?
Olaf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
