Re: non-free firmware in kernel modules, aggregation and unclear copyright notice.

Zan Lynx
2005-04-13T02:28:50Z

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

On Tue, 2005-04-12 at 20:45 +0200, Sven Luther wrote:
[snip]
> > A did put a GPL notice on it. He can't change his mind later.
> Then he should give us the source.
[snip]
> The fact remains that those firmware blob have no licence, and thus defacto
> fall under the GPL.
>
> > Moreover, the firmare in not in binary form, but is part of a C source
> > file.
>
> It is in binary form. Disguised binary form maybe but still binary form.
[snip]
> And where did those hexstrings come from ?

It seems to me, that to be consistent with the argument you seem to be
presenting concerning binary data in GPLd code, that you also need to be
demanding the "source" hardware design for binary register values.

Why not consider the binary firmware in the same category as binary
register programming information? You poke these magic bytes into these
memory locations and it works.

Where do you draw the lines between "write this byte to set the input
gate here and the output gate to there" and "write this byte sequence to
send the input byte through this loop, into this buffer, add it to the
last byte entered, and output it over there"?
--
Zan Lynx <zlynx@acm.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]