Re: MODULE_LICENSE usage

[Nathan Williams]

> b) if the binary blob is really a library to be run in kernel (host)
> space then there is no point in writing such driver - there are
> completely open-source drivers for ADSL devices and most (if not
> all) people will prefer them over any binary library.
>
> Perhaps you can convince the chipset manufacturer to open the source
> or publish the complete docs, but I wouldn't count on it.
> --
> Krzysztof Halasa
>

The binary blob is run in the kernel.  I wasn't aware of any
completely open-source drivers for ADSL modems, mine is a PCI ADSL
modem.  I have been referred to the BeWAN PCI driver as a guide for
conforming to GPL, but they use a binary library as well.

> I don't see any reason you cannot include the line 'MODULE_LICENSE("GPL")'
> in the source code for your module so long as that source code is not a
> derivative work of the binary. Whether or not you can distribute the
> resulting binary is, however, a complex legal question.
>
> > Additionally, I'm unsure of what is the meaning of
> >
> > "GPL and additional rights"     [GNU Public License v2 rights and more]
> >
> > Is it correct to say that my driver is licensed under GPL with
> > additional rights to use the binary library file?
>
> No. The "additional right" to use the binary library file is not a right
> under which your driver is licensed, so there are no additional rights to
> your driver. The binary library itself is offered under rights much less
> than the GPL.
>
> What exactly is the license under which the binary is offered? If it's "may
> be used with your driver" then you may have some interesting GPL issues when
> people want to modify your driver and continue to use the binary firmware
> with it.
>
> Does this "binary library" actually run on the host computer? Or is it
> firmware that runs on the modem only? Does it actually link in to the
> driver?
>
> DS

My company has been given documentation and the library source under
the terms of an NDA with the chipset manufacturer.  We are permitted
to compile the library and distribute the resultant binary blob, but
not release the source to the library.

The binary blob is linked into the driver we have written.  We don't
distribute this compiled module, customers are given the driver source
and the library blob, which they compile themselves.

Thanks for the help.

Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/