[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180430195931.GC2456@t60.musicnaut.iki.fi>
Date: Mon, 30 Apr 2018 22:59:31 +0300
From: Aaro Koskinen <aaro.koskinen@....fi>
To: Tomi Valkeinen <tomi.valkeinen@...com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
linux-fbdev@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH] video: fbdev: omap2: remove rfbi
Hi,
On Mon, Apr 30, 2018 at 10:06:11AM +0300, Tomi Valkeinen wrote:
> On 27/04/18 21:12, Aaro Koskinen wrote:
> >> You should be targeting omapdrm driver instead, fbdev subsystem is closed
> >> for the new hardware support.
> >
> > AFAIK, based on N950 display support discussion, it's impossible to get
> > anything new into omapdrm for a long time. And based on Tomi's comments,
> > restoring RFBI support with omapfb should be a minor thing.
>
> I was perhaps a bit vague, but I didn't say it should be a minor thing.
> I meant that there should be no architectural obstacles in omapfb, and I
> think all the generic plumbing to enable N800 display is there in omapfb.
>
> That said, it still needs a real amount of work with the rfbi driver,
> the encoder driver and the panel driver on N800 (the encoder and the
> panel driver are not in mainline anymore).
Let's see first if I get anything working. After that we can evaluate
the impact properly once we see the actual patches needed.
A.
Powered by blists - more mailing lists