From: Prasanna Kumar T S M <ptsm@linux.microsoft.com>
To: dri-devel@lists.freedesktop.org, linux-hyperv@vger.kernel.org,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ssengar@linux.microsoft.com, mhklinux@outlook.com,
ptsm@linux.microsoft.com, rdunlap@infradead.org,
bartosz.golaszewski@linaro.org, gonzalo.silvalde@gmail.com,
arnd@arndb.de, tzimmermann@suse.de, decui@microsoft.com,
wei.liu@kernel.org, deller@gmx.de, kys@microsoft.com,
haiyangz@microsoft.com
Subject: [PATCH 1/2] fbdev/hyperv_fb: deprecate this in favor of Hyper-V DRM driver
Date: Wed, 17 Sep 2025 07:03:05 -0700 [thread overview]
Message-ID: <1758117785-20653-1-git-send-email-ptsm@linux.microsoft.com> (raw)
In-Reply-To: <E5C2A201B1BD>
The Hyper-V DRM driver is available since kernel version 5.14 and it
provides full KMS support and fbdev emulation via the DRM fbdev helpers.
Deprecate this driver in favor of Hyper-V DRM driver.
Signed-off-by: Prasanna Kumar T S M <ptsm@linux.microsoft.com>
---
drivers/video/fbdev/Kconfig | 5 ++++-
drivers/video/fbdev/hyperv_fb.c | 2 ++
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig
index c21484d15f0c..48c1c7417f6d 100644
--- a/drivers/video/fbdev/Kconfig
+++ b/drivers/video/fbdev/Kconfig
@@ -1773,13 +1773,16 @@ config FB_BROADSHEET
a bridge adapter.
config FB_HYPERV
- tristate "Microsoft Hyper-V Synthetic Video support"
+ tristate "Microsoft Hyper-V Synthetic Video support (DEPRECATED)"
depends on FB && HYPERV
select DMA_CMA if HAVE_DMA_CONTIGUOUS && CMA
select FB_IOMEM_HELPERS_DEFERRED
help
This framebuffer driver supports Microsoft Hyper-V Synthetic Video.
+ This driver is deprecated, please use the Hyper-V DRM driver at
+ drivers/gpu/drm/hyperv (CONFIG_DRM_HYPERV) instead.
+
config FB_SIMPLE
tristate "Simple framebuffer support"
depends on FB
diff --git a/drivers/video/fbdev/hyperv_fb.c b/drivers/video/fbdev/hyperv_fb.c
index 75338ffc703f..c99e2ea4b3de 100644
--- a/drivers/video/fbdev/hyperv_fb.c
+++ b/drivers/video/fbdev/hyperv_fb.c
@@ -1357,6 +1357,8 @@ static int __init hvfb_drv_init(void)
{
int ret;
+ pr_warn("Deprecated: use Hyper-V DRM driver instead\n");
+
if (fb_modesetting_disabled("hyper_fb"))
return -ENODEV;
--
2.49.0
next parent reply other threads:[~2025-09-17 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E5C2A201B1BD>
2025-09-17 14:03 ` Prasanna Kumar T S M [this message]
2025-09-17 14:41 ` [PATCH 1/2] fbdev/hyperv_fb: deprecate this in favor of Hyper-V DRM driver Thomas Zimmermann
2025-09-18 4:01 ` Michael Kelley
2025-09-30 19:26 ` Helge Deller
2025-09-18 8:04 ` Saurabh Singh Sengar
2025-09-17 14:03 ` [PATCH 2/2] MAINTAINERS: Mark hyperv_fb driver Obsolete Prasanna Kumar T S M
2025-09-17 14:42 ` Thomas Zimmermann
2025-09-18 4:03 ` Michael Kelley
2025-09-18 8:05 ` Saurabh Singh Sengar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1758117785-20653-1-git-send-email-ptsm@linux.microsoft.com \
--to=ptsm@linux.microsoft.com \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=decui@microsoft.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gonzalo.silvalde@gmail.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=rdunlap@infradead.org \
--cc=ssengar@linux.microsoft.com \
--cc=tzimmermann@suse.de \
--cc=wei.liu@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).