LKML Archive on
help / color / mirror / Atom feed
From: Alistair Francis <>
To: Fabio Estevam <>,
	Shawn Guo <>,
	Sascha Hauer <>,
	dl-linux-imx <>, Marek Vasut <>,,
	Linux Kernel Mailing List <>,
	Alistair Francis <>
Subject: Revert "video: fbdev: mxsfb: Remove driver"
Date: Sun, 15 Aug 2021 22:16:47 +1000	[thread overview]
Message-ID: <> (raw)


Commit f225f1393f034 "video: fbdev: mxsfb: Remove driver" removed the
mxsfb fbdev driver.

I am now working on getting mainline Linux running on the reMarkable 2
eInk reader [1]. Unfortunately the rM2 doesn't use the standard EPD
controller on the i.MX SoC, but instead uses the LCD controller.

eInk panels are complex to control and require writing temperature
dependent waveforms. As these waveforms are proprietary [2] the rM
team runs closed source software called SWTCON in userspace to control
the panel [3].

This closed source software expects the fbdev mxsfb driver and it
doesn't work with the DRM mxsfb driver (at least not that I can get it

The NXP fork of Linux also re-adds the fbdev driver [4], so they also
see some uses for it.

I was wondering if the community would be open to re-adding the fbdev
mxsfb driver to mainline? It could be re-added with a different
dt-binding so that it is not used by default and only enabled for
boards when required (like for the rM2).



             reply	other threads:[~2021-08-15 12:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-15 12:16 Alistair Francis [this message]
2021-08-15 12:31 ` Revert "video: fbdev: mxsfb: Remove driver" Marek Vasut
2021-08-16  7:34   ` Alistair Francis
2021-08-16  7:55     ` Marek Vasut
2021-08-17  9:08       ` Alistair Francis
2021-08-17 10:03         ` Marek Vasut
2021-08-17 12:16           ` Alistair Francis
     [not found]             ` <YR1R7/>
2021-08-19  8:16               ` Alistair Francis
     [not found]             ` <YR1Th65KKRS4D/>
2021-08-19  9:10               ` Alistair Francis
     [not found]                 ` <>
2021-08-19 22:36                   ` Alistair Francis
2021-10-14  9:56                     ` Alistair Francis
2021-10-21 10:42                       ` Alistair Francis

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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).