lkml.org 
[lkml]   [2005]   [Apr]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: non-free firmware in kernel modules, aggregation and unclear copyright notice.
From
Date
Scripsit Humberto Massa <humberto.massa@almg.gov.br>

> After a *lot* of discussion, it was deliberated on d-l that
> this is not that tricky at all, and that the "mere
> aggregation" clause applies to the combination, for various
> reasons, with a great degree of safety.

When was this alleged conclusion reached? I remember nothing like
that.

> No-one is saying that the linker "merely aggregates" object
> code for the driver; what *is* being said is: in the case of
> firmware, especially if the firmware is neither a derivative
> work on the kernel (see above) nor the firmware includes part
> of the kernel (duh), it is *fairly* *safe* to consider the
> intermixing of firmware bytes with kernel binary image bytes
> in an ELF object file as mere aggregation.

No, it is completely wrong to say that the object file is merely an
aggregation. The two components are being coupled much more tightly
than in the situation that the GPL discribes as "mere aggregation".

--
Henning Makholm "Hør, hvad er det egentlig
der ikke kan blive ved med at gå?"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-04-08 04:15    [W:0.079 / U:0.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site