Skip to contentSkip to conversation

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

DISCUSSION Humberto Massa 2 participants 4 messages Apr 7, 2005 1 message not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 4 lines · Richard B. Johnson

Well it doesn't make any difference. If GPL has degenerated to where one can't upload microcode to a device as part of its initialization, without having the "source" that generated that microcode, we are in a lot of hurt. Intel isn't going to give their designs away.

I don't recall anyone asking Intel to give theirs designs away. This thread is about:

1. (mainly) some firmware hexdumps present in the kernel source tree are either expicitly marked as being GPL'd or unmarked, in which case one would assume that they would be GPL'd;

1a. this means that those firmware hexdumps are not legally distributable by any person besides the firmware copyright holder, because any other person could not comply with the terms of the Section 3 of the GPL (IOW, a third party cannot give you a source code they don't have);

1b. [1a], for its turn, means that the current pristine kernel tree is not legally distributable and that any distributor is an easy prey for lawyer attacks.

2. (collaterally) some firmware hexdumps present in the kernel source tree are marked with "(C) Holder All Rights Reserved";

2a. copyright law FORBIDS anyone to distribute such pieces of information without proper authorization.

3. (corolary) for each of the problematic hexdumps, the following steps should be taken:

3a. the copyright holder should be asked for the source code to the firmware -- if they do this, it would be great for a lot of Free Software reasons;

3b. if the copyright holder declines, it should be asked for a license to freely redistribute the firmware; and

3c. if the copyright holder declines, the firmware *must* be yanked from the pristine kernel tree;

3d. furthermore, all of this *should* be properly documented, IMHO, both in a centralized file, and in the file where the firmware hexdump appears.

Quoted 4 lines

Last time I checked, GPL was about SOFTware, not FIRMware, and not MICROcode. If somebody has decided to rename FIRMware to SOFTware, then they need to complete the task and call it DORKware, named after themselves.

Last time I checked, the GPL was a COPYRIGHT LICENSE and, as such, not "about" anything in particular. Yes, it was idealized to be used for the licensing of computer programs and libraries. OTOH, many works of many other kinds (music, literary works, etc) were licensed under the GPL.

Quoted 1 line

This whole thread and gotten truly bizarre.

Nah, it has a good reason to exist... With the passing of time, Debian, that is supposed to be a Free Software OS, is depending more and more of non-Free components. And yes, as it is today, the pristine kernel tree is non-free.

Regards,
Massa

#2 lore raw

Am Donnerstag, 7. April 2005 16:30 schrieb Humberto Massa:

Quoted 7 lines

I don't recall anyone asking Intel to give theirs designs away. This thread is about:

1. (mainly) some firmware hexdumps present in the kernel source tree are either expicitly marked as being GPL'd or unmarked, in which case one would assume that they would be GPL'd;

Quoted 5 lines

1a. this means that those firmware hexdumps are not legally distributable by any person besides the firmware copyright holder, because any other person could not comply with the terms of the Section 3 of the GPL (IOW, a third party cannot give you a source code they don't have);

As this has been discussed numerous times and consensus never achieved and is unlikely to be achieved, I suggest that you keep this discussion internal to Debian until at least you have patches which can be evaluated and discussed. Until then Debian may do to its kernel whatever it pleases and should be prepared to explain to its users why it removed or altered drivers.

Regards
Oliver

#3 lore raw
Quoted 10 lines · Oliver Neukum

As this has been discussed numerous times and consensus never achieved and is unlikely to be achieved, I suggest that you keep this discussion internal to Debian until at least you have patches which can be evaluated and discussed. Until then Debian may do to its kernel whatever it pleases and should be prepared to explain to its users why it removed or altered drivers.

Regards Oliver

Hi, Oliver.

You seemed to answer my e-mail without reading it; what I was explaining in it was: this is not a matter of patches, but of asking Where are the copyrights notices, Who are the copyright owners, and Which license are the firmwares under, and AFTER that, patching what should be patched.

Those three questions (Where, Who, Which) can only be answered by the kernel maintainers, and this is in *NO* way a Debian-only discussion. As I mentioned before, kernel.org kernel tree is, as of today, non-free and undistributable IMHO.

HTH,
Massa

#4 lore raw

Am Donnerstag, 7. April 2005 17:01 schrieb Humberto Massa:

Quoted 20 lines
Quoted 10 lines · Oliver Neukum

As this has been discussed numerous times and consensus never achieved and is unlikely to be achieved, I suggest that you keep this discussion internal to Debian until at least you have patches which can be evaluated and discussed. Until then Debian may do to its kernel whatever it pleases and should be prepared to explain to its users why it removed or altered drivers.

Regards Oliver

Hi, Oliver.

You seemed to answer my e-mail without reading it; what I was explaining in it was: this is not a matter of patches, but of asking Where are the copyrights notices, Who are the copyright owners, and Which license are the firmwares under, and AFTER that, patching what should be patched.

Quoted 4 lines

Those three questions (Where, Who, Which) can only be answered by the kernel maintainers, and this is in *NO* way a Debian-only discussion. As I mentioned before, kernel.org kernel tree is, as of today, non-free and undistributable IMHO.

Those who care got you after the second message at the latest. Anything more just annoys people. Some even pay for their online time. Who doesn't care will not start caring. Your oppinion on that matter frankly is exactly that.
If you care that deeply about it you'll have to track down copyright holders yourself. Good luck.

Regards
Oliver