Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dvb-firmware: new package
Date: Tue, 27 Dec 2022 22:43:54 +0100	[thread overview]
Message-ID: <20221227224354.3b1d1fdf@windsurf> (raw)
In-Reply-To: <20221226180353.1897840-1-bernd.kuhls@t-online.de>

Hello,

On Mon, 26 Dec 2022 19:03:53 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:

> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>

Do we know why these firmware files are not part of the linux-firmware
project? They are needed in conjunction with which kernel drivers?

> +DVB_FIRMWARE_VERSION = 1.4.2
> +DVB_FIRMWARE_SITE = $(call github,LibreELEC,dvb-firmware,$(DVB_FIRMWARE_VERSION))
> +DVB_FIRMWARE_LICENSE = PROPRIETARY
> +DVB_FIRMWARE_REDISTRIBUTE = NO

This DVB_FIRMWARE_REDISTRIBUTE = NO is not good, as it would actually
encourage people to violate the license of those firmware files. Indeed
what DVB_FIRMWARE_REDISTRIBUTE = NO says is "to not mention this
package in the manifest" and "do not copy the license files". However,
several license files in dvb-firmware explicitly *require* that the
license file should be distributed.

Quoting from LICENCE.go7007:

=====
The firmware files included in the firmware/ directory may be freely
redistributed only in conjunction with this document; but modification,
tampering and reverse engineering are prohibited.
=====

Quoting from LICENCE.xc5000

=====
// Permission to use, copy, modify, and/or distribute this software, only
// for use with Xceive ICs, for any purpose with or without fee is hereby
// granted, provided that the above copyright notice and this permission
// notice appear in all source code copies.
=====

Quoting from LICENCE.siano

=====
* Redistributions must reproduce the above copyright notice and the
following disclaimer in the documentation and/or other materials
provided with the distribution.
=====

If we want to create a package for this properly, we need to have a
mapping between the firmware files and the specific license file that
applies to them, so that we know which conditions apply to which
firmware file. As it is done today in this Github repo, it looks like
some firmware files are random binaries from the Internet, with no
clear licensing... which makes their redistribution not legal.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-12-27 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 18:03 [Buildroot] [PATCH 1/1] package/dvb-firmware: new package Bernd Kuhls
2022-12-27 21:43 ` Thomas Petazzoni via buildroot [this message]
2022-12-27 21:58   ` Yann E. MORIN
2022-12-28  8:37     ` Thomas Petazzoni via buildroot
     [not found] ` <20221227224354.3b1d1fdf__40547.9438648158$1672177457$gmane$org@windsurf>
2022-12-27 22:30   ` Bernd Kuhls
2022-12-28 10:00     ` Thomas Petazzoni via buildroot
2022-12-28 22:22       ` Bernd Kuhls

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=20221227224354.3b1d1fdf@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd.kuhls@t-online.de \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox