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

[Marco Colombo <marco@esi.it>]

On Wed, 2005-04-13 at 21:47 +0200, Sven Luther wrote:
> On Wed, Apr 13, 2005 at 04:53:56PM +0200, Marco Colombo wrote:
> > > > This is different. They are not giving the source at all. The licence
> > > > for those object files _has_ to be different. _They_ want it to be
> > > > different.
> > > 
> > > Sure, but in this case, the binary firmware blob is also a binary without
> > > sources. If they really did write said firmware directly as it is, then they
> > > should say so, but this is contrary to everyone's expectation, and a dangerous
> > > precedent to set.
> > 
> > You should realize that any author can publish his work in the form he
> > likes. He's not bound to "everyone's expectation". I see no danger in
> > that.
> 
> I think there may be some limitation of using the GPL as licence in this case
> though, as such behavior may limit its value, and the GPL itself is by no
> means free software.

That GPL isn't the best license in this case (firmware included as
hexstring in the driver source), we already know. But fixing it is up
to the copyright holder. We or GPL face no risk.

Note that the holder does. I'd be interesting if someone produced a
derivative work, such a translation. A translation from the hex form
to some kind of textual formally defined language, such as, say,
assembler, or C. That would be covered by GPL. And would be
distributable under it. Say that the resulting binary is slightly
different. You are _required_ by GPL to provide the source in the
preferred form, this time, preferred by _you_. What if that is C?
Interesting enough. Can the hexstring be reverse-engineered into C,
if it's placed under GPL? Can the copyright holder really prevent that?

Something new to think of. :-)

Have a nice day,
.TM.
-- 
      ____/  ____/   /
     /      /       /                   Marco Colombo
    ___/  ___  /   /                  Technical Manager
   /          /   /                      ESI s.r.l.
 _____/ _____/  _/                      Colombo@ESI.it