[RFC PATCH 0/3] staging: remove fbdev drivers
benh at kernel.crashing.org
Thu Dec 8 21:23:30 UTC 2016
On Thu, 2016-12-08 at 10:01 +0200, Tomi Valkeinen wrote:
> > DRM drivers don't strike me as suitable for small/slow cores with dumb
> > framebuffers or simple 2D only accel, such as the one found in the ASpeed
> > BMCs.
> Then the DRM framework should be improved to be suitable.
Dave ? :-)
> > With drmfb you basically have to shadow everything into memory & copy
> > over everything, and locks you out of simple 2D accel. For a simple text
> > console the result is orders of magnitude slower and memory hungry than
> > a simple fbdev.
> I don't think that's true. You can have a single fbdev buffer and blit
> there all you want, afaik.
Well, I had that argument with Dave Airlie which I CCed. The "dumb" ones like
bochsdrmfb, cirrusdrmfb, astdrmfb ... all use shadowing, meaning they use a
lot more memory and cannot do any 2D acceleration for fbcon.
>From memory, David claimed you cannot directly work on the fb with a "proper"
DRM driver. Maybe I misunderstood but then the DRM shines by its complete
absence of useful documentation mixed with bazillion layers of APIs and helpers
so it's pretty hard to get ones head around it without wasting very large amounts
of time which I don't have at the moment.
> > Not everything has a powerful 3D GPU.
> We don't use GPU on OMAPs (except for 3D).
The CPU in an OMAP is order of magnitude faster than what I have in an
Aspeed BMC though.
More information about the dri-devel