[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5683A48C.80203@laposte.net>
Date: Wed, 30 Dec 2015 10:31:56 +0100
From: Sebastian Frias <sf84@...oste.net>
To: Tomi Valkeinen <tomi.valkeinen@...com>,
laurent.pinchart@...asonboard.com, David Airlie <airlied@...ux.ie>
CC: Frans Klaver <fransklaver@...il.com>,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
linux-fbdev@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
mason <slash.tmp@...e.fr>,
Måns Rullgård <mans@...sr.com>,
dri-devel@...ts.freedesktop.org
Subject: Re: [RFC PATCH] fbdev: add support for Sigma Designs' smp8xxxfb.ko
Hi,
On 12/30/2015 09:06 AM, Tomi Valkeinen wrote:
>
> Also note that I don't want new fbdev drivers into the mainline kernel.
> You should implement a DRM based driver instead.
>
Thanks, is there a porting guide to go from fbdev to DRM?
Does DRM provides a "fbdev" backward compatible API? Would that be feasible?
I did not find much about that.
Currently our stack is something like:
Qt -> eglfs -> Mali -> fbdev -> mem -> output
(HW) (HW)
We don't control the eglfs/Mali (GPU) part.
From what I could see, Mali uses DRM with X11 which we do not need
(note: I'm not a Mali expert and just took a quick look at the code so I
may be wrong), which could be a problem.
If "implement a DRM driver" is a lot of work, it would end up as a
business decision and probably would not happen.
Would you say there are good solid arguments to shake our current stack
(other than for dusting it off)?
By the way, does DRM improves 2D acceleration support over fbdev?
Thanks,
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists