Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757889AbbGGOYb (ORCPT ); Tue, 7 Jul 2015 10:24:31 -0400 Received: from bytesatwork.ch ([91.135.72.15]:49388 "EHLO bytesatwork.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757797AbbGGOYV (ORCPT ); Tue, 7 Jul 2015 10:24:21 -0400 From: =?UTF-8?q?Urs=20F=C3=A4ssler?= To: daniel.vetter@ffwll.ch, linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, oliver.staebler@bytesatwork.ch, plagnioj@jcrosoft.com, tomi.valkeinen@ti.com, urs.fassler@bytesatwork.ch, geert@linux-m68k.org Subject: [PATCH 0/2 v2] video/logo: add option to return largest logo for a given resolution Date: Tue, 7 Jul 2015 16:24:10 +0200 Message-Id: <1436279052-17237-1-git-send-email-urs.fassler@bytesatwork.ch> X-Mailer: git-send-email 2.1.4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1117 Lines: 28 With this patches, the largest boot logo for a given display resolution is used. We need that functionality since it is common that a product has variants which differ only minimal in the hardware. Thus, we have the same kernel binary but different device trees for different hardware / displays. This patches allow use to show a full screen boot logo for every hardware variant. This is a rework of the patch from 3 Jul 2015 which respects the runtime-check on m68k. Urs Fässler (2): logo: add option to return largest logo for a given resolution fbdev: use largest logo if possible drivers/video/fbdev/core/fbmem.c | 21 ++++++---- drivers/video/logo/Kconfig | 7 ++++ drivers/video/logo/logo.c | 86 ++++++++++++++++++++++++++++++++-------- include/linux/linux_logo.h | 4 ++ 4 files changed, 94 insertions(+), 24 deletions(-) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/