LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com> To: Fabio Estevam <festevam@gmail.com>, Shawn Guo <shawnguo@kernel.org>, Sascha Hauer <kernel@pengutronix.de>, dl-linux-imx <linux-imx@nxp.com>, Marek Vasut <marex@denx.de>, b.zolnierkie@samsung.com, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Alistair Francis <alistair@alistair23.me> Subject: Revert "video: fbdev: mxsfb: Remove driver" Date: Sun, 15 Aug 2021 22:16:47 +1000 [thread overview] Message-ID: <CAKmqyKMLyx+CvBQbLz-xQvwLS692tx-4xOgU7b-V2J676D29yg@mail.gmail.com> (raw) Hello, 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 to). 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). 1: https://remarkable.com/store/remarkable-2 2: https://goodereader.com/blog/e-paper/e-ink-waveforms-are-a-closely-guarded-secret 3: https://remarkablewiki.com/tech/rm2_framebuffer 4: https://source.codeaurora.org/external/imx/linux-imx/log/drivers/video/fbdev/mxsfb.c?h=lf-5.10.35-2.0.0 Alistair
next 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/nIUIN3LA7t@ravnborg.org> 2021-08-19 8:16 ` Alistair Francis [not found] ` <YR1Th65KKRS4D/6+@ravnborg.org> 2021-08-19 9:10 ` Alistair Francis [not found] ` <YR58MvAYYEjBQ7l5@ravnborg.org> 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: 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=CAKmqyKMLyx+CvBQbLz-xQvwLS692tx-4xOgU7b-V2J676D29yg@mail.gmail.com \ --to=alistair23@gmail.com \ --cc=alistair@alistair23.me \ --cc=b.zolnierkie@samsung.com \ --cc=festevam@gmail.com \ --cc=kernel@pengutronix.de \ --cc=linux-imx@nxp.com \ --cc=linux-kernel@vger.kernel.org \ --cc=marex@denx.de \ --cc=shawnguo@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: linkBe 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).