From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932431AbeAQU4Q (ORCPT ); Wed, 17 Jan 2018 15:56:16 -0500 Received: from mx2.suse.de ([195.135.220.15]:34361 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932240AbeAQU4I (ORCPT ); Wed, 17 Jan 2018 15:56:08 -0500 From: Max Staudt To: b.zolnierkie@samsung.com, linux-fbdev@vger.kernel.org Cc: mstaudt@suse.de, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, tiwai@suse.com, oneukum@suse.com, msrb@suse.com, sndirsch@suse.com, michal@markovi.net, philm@manjaro.org, bernhard.rosenkranzer@linaro.org, kernel.max@enpas.org Subject: [RFC PATCH v3 00/13] Kernel based bootsplash Date: Wed, 17 Jan 2018 21:54:22 +0100 Message-Id: <20180117205435.2860-1-mstaudt@suse.de> X-Mailer: git-send-email 2.12.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear fbdev/fbcon/dri developers, Thanks for all the valuable feedback. I've looked into the suggestions you made, and found that it doesn't currently make sense to continue working on the splash code, given the low practical interest I've received on LKML. The code is, and always has been, intended primarily as a study of what can be done, and at this point it has fulfilled this requirement. Please find attached my latest version of the patchset in which I've clarified the documentation a bit, as well as added a FAQ and To-Do section for anyone wishing to pick up the code. The code is still based on v4.14-rc5, sorry about that. In particular, I hope to have clarified in the FAQ why I'm building on top of fbdev and fbcon, as I think I haven't made myself clear enough in the previous discussion. If you still think that my reasoning is wrong, I'd be thankful for pointers towards a better solution. I'll be happy to rebase it and continue to work on it if interest arises. This project has been a valuable experience - so huge thanks to everyone involved in any way, from user feedback over code reviews and all the way to architectural discussion. Max