Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751005AbdLaMxs (ORCPT ); Sun, 31 Dec 2017 07:53:48 -0500 Received: from www.llwyncelyn.cymru ([82.70.14.225]:55598 "EHLO fuzix.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750739AbdLaMxq (ORCPT ); Sun, 31 Dec 2017 07:53:46 -0500 Date: Sun, 31 Dec 2017 12:53:26 +0000 From: Alan Cox To: Oliver Neukum Cc: Daniel Vetter , Max Staudt , bernhard.rosenkranzer@linaro.org, dri-devel@lists.freedesktop.org, philm@manjaro.org, michal@markovi.net, b.zolnierkie@samsung.com, Stefan Dirsch , Takashi Iwai , linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v2 03/13] bootsplash: Flush framebuffer after drawing Message-ID: <20171231125326.6e4d912b@alans-desktop> In-Reply-To: <1513692473.14829.14.camel@suse.com> References: <20171213194755.3409-1-mstaudt@suse.de> <20171213194755.3409-4-mstaudt@suse.de> <20171213213506.GD26573@phenom.ffwll.local> <20171219122313.GE26573@phenom.ffwll.local> <8bbb0497-4a10-2f81-0040-6e7cd4e7353c@suse.de> <20171219135715.GG26573@phenom.ffwll.local> <1513692473.14829.14.camel@suse.com> Organization: Intel Corporation X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 778 Lines: 21 On Tue, 19 Dec 2017 15:07:53 +0100 Oliver Neukum 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