From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: Formal license ambiguity in arch/arm/boot/dts/sun?i-a*.dts
Date: Mon, 4 Aug 2014 21:25:10 +0200 [thread overview]
Message-ID: <20140804192510.GF3952@lukather> (raw)
In-Reply-To: <201408031959.27607.arnd@arndb.de>
On Sun, Aug 03, 2014 at 07:59:27PM +0200, Arnd Bergmann wrote:
> On Sunday 03 August 2014, Maxime Ripard wrote:
> > Thanks for reporting this.
> >
> > From a quick grep, the issue is actually broader than just
> > Allwinner. At least the following platforms seem to do the same:
> > - mvebu
> > - axm5516
> > - bcm
> > - berlin
> > - ea3250
> > - ecx-2000
> > - highbank
> > - imx / mxs
> > - lpc32xx
> > - phy3250
> > - picoxcell
> > - shmobile
> > - rockchip
> > - socfpga
> > - spear
> > - ste
> > - zynq
> >
> > Would you mind sending a patch to fix all these?
>
> I would actually prefer if we could migrate a lot of these files to BSD license,
> provided the original authors agree. We want the dtb blobs to be embeddable into
> boot loaders of any license.
Even though I'd be open to having my contributions to DTBs under the
BSD, is this really a thing?
I mean, for all I know, an OS/Bootloader would just parse a documented
binary file, and I don't see any derivative work there.
The same argument could be made for example for u-boot modifying a
DTB I guess.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140804/139c804a/attachment.sig>
next prev parent reply other threads:[~2014-08-04 19:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 19:20 Formal license ambiguity in arch/arm/boot/dts/sun?i-a*.dts Karsten Merker
2014-08-03 13:04 ` Maxime Ripard
2014-08-03 17:59 ` Arnd Bergmann
2014-08-04 19:25 ` Maxime Ripard [this message]
2014-08-04 21:23 ` Russell King - ARM Linux
2014-08-05 8:06 ` Arnd Bergmann
2014-08-07 13:20 ` Maxime Ripard
2014-09-02 10:22 ` Maxime Ripard
2014-09-02 10:40 ` Russell King - ARM Linux
2014-09-02 11:54 ` Chen-Yu Tsai
2014-09-02 12:27 ` Maxime Ripard
2014-09-02 12:35 ` Hans de Goede
2014-09-02 12:51 ` Maxime Ripard
2014-09-02 13:02 ` Arnd Bergmann
2014-09-02 13:37 ` Russell King - ARM Linux
2014-09-02 16:52 ` Russell King - ARM Linux
2014-09-02 14:42 ` Hans de Goede
2014-09-02 15:18 ` Maxime Ripard
2014-09-02 16:24 ` Russell King - ARM Linux
2014-08-05 8:01 ` Hans de Goede
2014-08-05 8:02 ` Hans de Goede
2014-08-03 20:41 ` Russell King - ARM Linux
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=20140804192510.GF3952@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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