mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
To: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<michal.simek@amd.com>, <deller@gmx.de>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-fbdev@vger.kernel.org>,
	<dri-devel@lists.freedesktop.org>, <git@amd.com>,
	Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Subject: [PATCH 0/2] fbdev: remove the Xilinx framebuffer driver
Date: Fri, 6 Nov 2026 22:39:00 +0530	[thread overview]
Message-ID: <20261106170902.3656809-1-radhey.shyam.pandey@amd.com> (raw)

The Xilinx framebuffer is legacy soft IP for the ML300 and ML403 reference
designs, built with the long discontinued Xilinx Platform Studio and ISE
Design Suite. Nothing upstream carries any of its five compatible strings.
Patch 1 removes the driver, patch 2 its documentation in 
bindings/xilinx.txt. 


Radhey Shyam Pandey (2):
  fbdev: xilinxfb: remove the driver
  dt-bindings: xilinx: Remove description for framebuffer IP

 Documentation/devicetree/bindings/xilinx.txt |  13 -
 drivers/video/fbdev/Kconfig                  |   9 -
 drivers/video/fbdev/Makefile                 |   1 -
 drivers/video/fbdev/xilinxfb.c               | 502 -------------------
 4 files changed, 525 deletions(-)
 delete mode 100644 drivers/video/fbdev/xilinxfb.c


base-commit: ddfe51b0a0f5dc9e415cc2c8ad8db17532dd426b
-- 
2.44.4


             reply	other threads:[~2026-11-06 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 17:09 Radhey Shyam Pandey [this message]
2026-11-06 17:09 ` [PATCH 1/2] fbdev: xilinxfb: remove the driver Radhey Shyam Pandey
2026-11-06 17:09 ` [PATCH 2/2] dt-bindings: xilinx: Remove description for framebuffer IP Radhey Shyam Pandey
2026-11-09  7:29 ` [PATCH 0/2] fbdev: remove the Xilinx framebuffer driver Michal Simek

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=20261106170902.3656809-1-radhey.shyam.pandey@amd.com \
    --to=radhey.shyam.pandey@amd.com \
    --cc=conor+dt@kernel.org \
    --cc=deller@gmx.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=git@amd.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=robh@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

all inboxes | Powered by JetHome®