Re: [RFC PATCH 0/6] Boot logo supplied by the device tree
MÃ xim Pedraza Padilla <[email protected]> Tue, 4 Aug 2026 00:04:23 +0200
| Newsgroups | org.freedesktop.lists.dri-devel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-fbdev,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAEUXW=EHD1Y1zHQWE=jFhONM5Hg6TTc_uPYHgp-GS-4YWYJN3A@mail.gmail.com> |
El lun, 3 ago 2026 a las 14:39, Ulrich =C3=96lmann (<[email protected]>) 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. 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. In any case, whether such device trees are accepted is ultimately for the device tree maintainers to decide. Best regards, Max