[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171231125326.6e4d912b@alans-desktop>
Date: Sun, 31 Dec 2017 12:53:26 +0000
From: Alan Cox <gnomes@...rguk.ukuu.org.uk>
To: Oliver Neukum <oneukum@...e.com>
Cc: Daniel Vetter <daniel@...ll.ch>, Max Staudt <mstaudt@...e.de>,
bernhard.rosenkranzer@...aro.org, dri-devel@...ts.freedesktop.org,
philm@...jaro.org, michal@...kovi.net, b.zolnierkie@...sung.com,
Stefan Dirsch <sndirsch@...e.com>,
Takashi Iwai <tiwai@...e.com>, linux-fbdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 03/13] bootsplash: Flush framebuffer after
drawing
On Tue, 19 Dec 2017 15:07:53 +0100
Oliver Neukum <oneukum@...e.com> wrote:
> Am Dienstag, den 19.12.2017, 14:57 +0100 schrieb Daniel Vetter:
> > > Would you like me to extend the FB API or not?
> >
> > Yes. Well for real I'd like you to do kms, so maybe you need to explain
> > why exactly you absolutely have to use fbdev (aka which driver isn't
> > supported by drm that you want to enable this on).
>
> Hi,
>
> those would be at a minimum efifb, vesafb, xenfb
> Those are obviously not sexy, but from a practical point of view
> they are the minimum you need to support.
I think it's more constructive to look at it the other way around. What
drivers do we have that actually need to be used which don't have DRM
equivalents - and how do we fix that instead ?
Alan
Powered by blists - more mailing lists