From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 09A57C55172 for ; Tue, 4 Aug 2026 07:15:11 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 3B74110E652; Tue, 4 Aug 2026 07:15:11 +0000 (UTC) Received: from mx1.white.stw.pengutronix.de (mx1.white.stw.pengutronix.de [185.203.200.13]) by gabe.freedesktop.org (Postfix) with ESMTPS id DE6AD10E0E8 for ; Tue, 4 Aug 2026 05:25:42 +0000 (UTC) Received: from drehscheibe.grey.stw.pengutronix.de (drehscheibe.grey.stw.pengutronix.de [IPv6:2a0a:edc0:0:c01:1d::a2]) (Authenticated sender: relay-from-drehscheibe.grey.stw.pengutronix.de) by mx1.white.stw.pengutronix.de (Postfix) with ESMTPSA id C99062006F0; Tue, 04 Aug 2026 07:25:40 +0200 (CEST) Received: from pty.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::c5]) by drehscheibe.grey.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wr7em-002oRb-2O; Tue, 04 Aug 2026 07:25:40 +0200 Received: from uol by pty.whiteo.stw.pengutronix.de with local (Exim 4.98.2) (envelope-from ) id 1wr7em-0000000ALgp-2dXe; Tue, 04 Aug 2026 07:25:40 +0200 From: =?utf-8?Q?Ulrich_=C3=96lmann?= To: =?utf-8?Q?M=C3=A0xim?= Pedraza Padilla Cc: Rob Herring , Conor Dooley , Thomas Zimmermann , devicetree@vger.kernel.org, Helge Deller , linux-fbdev@vger.kernel.org, Maxime Ripard , linux-kernel@vger.kernel.org, Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= , dri-devel@lists.freedesktop.org, kernel@pengutronix.de, Krzysztof Kozlowski Subject: Re: [RFC PATCH 0/6] Boot logo supplied by the device tree In-Reply-To: (=?utf-8?Q?=22M=C3=A0xim?= Pedraza Padilla"'s message of "Tue, 4 Aug 2026 00:04:23 +0200") References: <20260731215043.30392-1-maximpedraza@gmail.com> <6rbjbj74zh.fsf@pengutronix.de> User-Agent: mu4e 1.12.15; emacs 30.2 Date: Tue, 04 Aug 2026 07:25:40 +0200 Message-ID: <6r5x1q78yz.fsf@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 04 Aug 2026 07:15:10 +0000 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Hi Max, On Tue, Aug 04 2026 at 00:04 +0200, M=C3=A0xim Pedraza Padilla wrote: > El lun, 3 ago 2026 a las 14:39, Ulrich =C3=96lmann > () escribi=C3=B3: >> independently of the specific implementation, please keep in mind that >> the kernel is distributed under the GPLv2, which may have implications >> for a proprietary image embedded in the device tree. That doesn't >> necessarily have to be a deal-breaker, but it's probably something that >> should be considered carefully. > > Good point, I had not considered it. > > A warning could be added to the binding documentation about the licensing > implications of a proprietary logo, aimed at anyone thinking of > submitting a device tree carrying one to the kernel tree. I am happy to > add that in v2 if it is considered useful. I think the issue is broader than upstream submissions. Once such a device tree is shipped as part of a GPL kernel in a product, the GPL obligations already apply to that distribution. Therefore, the licensing implications of embedding a proprietary logo are not limited to upstream acceptance, they also affect downstream product distributions. > Patches 4 and 5 also avoid the question by construction: there the image > is a separate binary the bootloader loads, and the device tree carries > only a phandle to the reserved region. Right, here everything is clearly uncoupled. > In any case, whether such device trees are accepted is ultimately for the > device tree maintainers to decide. As mentioned above, the issue also extends to deployed products. Those were just my thoughts on the licensing aspect. Best regards, Ulrich > Best regards, > Max --=20 Pengutronix e.K. | Ulrich =C3=96lmann = | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |