All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: "Màxim Pedraza Padilla" <maximpedraza@gmail.com>
Cc: "Rob Herring" <robh@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	devicetree@vger.kernel.org, "Helge Deller" <deller@gmx.de>,
	linux-fbdev@vger.kernel.org, "Maxime Ripard" <mripard@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	dri-devel@lists.freedesktop.org, kernel@pengutronix.de,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>
Subject: Re: [RFC PATCH 0/6] Boot logo supplied by the device tree
Date: Tue, 04 Aug 2026 07:25:40 +0200	[thread overview]
Message-ID: <6r5x1q78yz.fsf@pengutronix.de> (raw)
In-Reply-To: <CAEUXW=EHD1Y1zHQWE=jFhONM5Hg6TTc_uPYHgp-GS-4YWYJN3A@mail.gmail.com> ("Màxim Pedraza Padilla"'s message of "Tue, 4 Aug 2026 00:04:23 +0200")

Hi Max,

On Tue, Aug 04 2026 at 00:04 +0200, Màxim Pedraza Padilla <maximpedraza@gmail.com> wrote:
> El lun, 3 ago 2026 a las 14:39, Ulrich Ölmann
> (<u.oelmann@pengutronix.de>) escribió:
>> 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
-- 
Pengutronix e.K.                           | Ulrich Ölmann               |
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 |

  reply	other threads:[~2026-08-04  5:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 21:50 [RFC PATCH 0/6] Boot logo supplied by the device tree Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 1/6] dt-bindings: display: add a device tree supplied boot logo Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 2/6] video: logo: allow the boot logo to come from the device tree Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 3/6] fbdev: honour the device tree boot logo placement properties Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 4/6] dt-bindings: display: allow the boot logo in a reserved memory region Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 5/6] video: logo: allow the boot logo to come from " Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 6/6] video: logo: add ppmtodtlogo host tool Max Pedraza
2026-08-01  8:08 ` [RFC PATCH 0/6] Boot logo supplied by the device tree Uwe Kleine-König
2026-08-01 20:44   ` Helge Deller
2026-08-01 22:01     ` Màxim Pedraza Padilla
2026-08-02 13:35       ` Uwe Kleine-König
2026-08-02 22:56         ` Màxim Pedraza Padilla
2026-08-03 12:39   ` Ulrich Ölmann
2026-08-03 22:04     ` Màxim Pedraza Padilla
2026-08-04  5:25       ` Ulrich Ölmann [this message]
2026-08-04 15:59         ` Màxim Pedraza Padilla
2026-08-04 13:58 ` Geert Uytterhoeven
2026-08-04 22:37   ` Màxim Pedraza Padilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6r5x1q78yz.fsf@pengutronix.de \
    --to=u.oelmann@pengutronix.de \
    --cc=conor+dt@kernel.org \
    --cc=deller@gmx.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maximpedraza@gmail.com \
    --cc=mripard@kernel.org \
    --cc=robh@kernel.org \
    --cc=tzimmermann@suse.de \
    --cc=u.kleine-koenig@baylibre.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.