Skip to contentSkip to conversation

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

DISCUSSION Humberto Massa 7 participants 19 messages Apr 7, 2005 – Apr 11, 2005 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 08Gc5.A.AFC.QJPVCB@murphy

#1 lore raw
Quoted 10 lines · David Schwartz
Quoted 8 lines

Well whoever wrote that seems to have taken the stand that the openfirmware package was were the firmware came from. The person obviously made a lot of statements without bothering checking out the real source. Well it didn't come from there, I got it from Alteon under a written agreement stating I could distribute the image under the GPL. Since the firmware is simply data to Linux, hence keeping it under the GPL should be just fine.

Quoted 6 lines

You cannot distribute anything under the GPL if you cannot also distribute the source code (the preferred form of the software for the purpose of making modifications to it). How Linux sees it is irrelevant. For any piece of software, one can imagine some processor that can only see it as data. The GPL doesn't distinguish between processors.

I think this is undisputed.

Quoted 10 lines

Alteon's written agreement notwithstanding, you cannot distribute the firmware under the GPL if you cannot provide the preferred form of the firmware for the purpose of making modifications to it. The firmware does not run on Linux, so saying "linux sees it as data" is as absurd as saying I can distribute the x86 Linux kernel without the source because my calculator can only see it as data.

You cannot distribute the firmware binary under the GPL. Period.

This is where you are wrong IMMHO. All that is needed for you to distribute the hexdump blob under the GPL is a declaration from the copyright holder saying "this, to me, is the preferred form for modification of the firmware and hence the source code under the GPL."

Quoted 6 lines

Now, if you were trying to say that you could aggregate the firmware with another work and distribute the result under the GPL, the test would be whether the final result is "mere aggregation" or not. This is a fantastically tricky question and I don't think anyone on this list could give you particularly useful guidance.

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. (Safer than that, only after court) :-)

Quoted 7 lines

My own opinion is that it's a threshold issue based upon several factors. For example -- has the firmware been specifically designed to work with the Linux driver or is it "generic" firmware? If you can't take the thing you're distributing (the combined binary) and extract two works from it (the firmware and the work whose source you are offering), I cannot see how you can claim it's mere aggregation.

Now, if the firmware was specifically designed to work with the linux driver, than it *is* a derivative work on the kernel as a whole and the source code should be provided upon redistribution as per GPL section 3 etc.

*BUT* this does not preclude Broadcom from stating: "our engineers generated by hand the hex codes that make our hardware work."

Quoted 6 lines

If you believe the linker "merely aggregates" the object code for the driver with the data for the firmware, I can't see how you can argue that any linking is anything but mere aggregation. In neither case can you separate the linked work into the two separate works and in both cases the linker provides one work direct access to the other.

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.

Quoted 4 lines

If you only distribute the source to the driver and don't put a GPL notice in the files that contain the firmware data, I think you're okay. I think you're asking for trouble if you distribute a combined compiled/linked driver.

Disagreed.

Quoted 1 line

DS

HTH,

Massa

#2 lore raw

Scripsit Humberto Massa <[email protected]>

Quoted 4 lines

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.

Quoted 7 lines

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".

Signature · 2 lines
Henning Makholm                                   "Hør, hvad er det egentlig
                                          der ikke kan blive ved med at gå?"
#3 lore raw
Quoted 9 lines
Quoted 8 lines

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.

Quoted 3 lines

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".

Would you maintain this position even if the firmware is identical
across operating systems and the Linux driver is identical across different firmware builds for different hardware implementations?

Say, for example, Intel comes out with a new super-smart and
sophisticated network card. They also offer firmware that makes it look just like an NE2000. They don't create this firmware for Linux, they create it for any set of operating systems that don't have specific drivers for this card.

Similarly, the NE2000 driver wasn't specifically designed to use
this firmware. Both the firmware and the driver were independently developed to implement the same de facto standard.

Now, someone combines the firmware and the driver into a package
that checks what card you are using, and if it has the appropriate firmware to make the card work with the driver, uploads it.

Note that the issue is not whether the GPL describes this as "mere
aggregation" because the GPL doesn't get to set its own scope. The issue is whether the resulting binary is a single work (that is derivative of the GPL'd driver) or whether it's two works with a license boundary between them.

It would not be obviously unreasonable to argue that the NE2000 API
constitutes a license boundary between the two works, each of which stays on its own side of that API.

Lacking clear court guidance, I see it as a threshold issue. One
primary issue (I think) is to what extent that firmware and the driver have been customized for each other. A work that is carefully designed to mesh tightly with another work is analogous to a sequel, which is a derivative work.

I think we have a real problem, however, in cases where the source
file that holds only the firmware data contains a GPL notice.

DS

#4 lore raw

Scripsit "David Schwartz" <[email protected]>
[quoting me]

Quoted 7 lines
Quoted 3 lines

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".

Would you maintain this position even if the firmware is identical
across operating systems and the Linux driver is identical across different firmware builds for different hardware implementations?

Yes I would. Linking forms a tighter coupling than just placing the two parts side by side on a filesystem designed for general storage of byte streams. There is more to say about the situation than the naked fact that that they are aggreated on the same medium; ergo the sutiation does not constitute *only* aggregation, and the "mere aggregation" language of the GPL does not apply.

In particular, the end of GPL #2 does not provide a blanket exception for all forms of aggregation; it specifically speaks about aggregation "on a volume of a storage or distribution medium".

Quoted 2 lines

Note that the issue is not whether the GPL describes this as "mere
aggregation" because the GPL doesn't get to set its own scope.

The scope of the copyright of the original work includes situation where part of that original work is being copied (excluding fair use and other jurisdiction-specific exceptions). In order to do such copying, you need permission from the copyright holder of the original work. If all the permission you have is the GPL, the copyihg you are doing had better fall into the class of copying that the GPL provides a permission for.

It *is*, therefore, relevant, whether the GPL's special conditions for works "that in whole or in part contains the Program" apply to the linked object files.

Quoted 3 lines

The issue is whether the resulting binary is a single work (that is derivative of the GPL'd driver) or whether it's two works with a license boundary between them.

A reasonable person can disagree about whether the word "work" in GPL #2(b) is meant to exclude non-trivial aggregations that do not add creative choice to that already expressed in the components.

However, I don't think a reasonable person can argue that even if 2(b) had said "byte stream" instead of "work" it would not have been legally potent to demand GPL-compatible licensing of the firmware as a condition for the permission to copy the GPL-covered part of the byte stream.

Quoted 3 lines

It would not be obviously unreasonable to argue that the NE2000 API
constitutes a license boundary between the two works, each of which stays on its own side of that API.

No, it wouldn't be obviously unreasonable for a license to recognize such a "license boundary". However, as I see it the GPL happens not to do this.

Quoted 5 lines

Lacking clear court guidance, I see it as a threshold issue. One
primary issue (I think) is to what extent that firmware and the driver have been customized for each other. A work that is carefully designed to mesh tightly with another work is analogous to a sequel, which is a derivative work.

I think the "derivative work" angle is a red herring. I do not think that either of the two parts that are being linked together (i.e. the driver and the firmware) are derivates of the other. The relevant point is that distribution of the linked _result_ is nevertheless subject to the condition in GPL #2, which is in general the only source we have for a permission to distribute a non-verbatim-source form of the driver.

Signature · 1 line
Henning Makholm                             "... and that Greek, Thucydides"
#5 lore raw
Quoted 7 lines · Henning Makholm

Scripsit "David Schwartz" <[email protected]>
[quoting me]

Quoted 3 lines
Quoted 3 lines

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".

Quoted 7 lines
Quoted 3 lines

Would you maintain this position even if the firmware is identical
across operating systems and the Linux driver is identical across different firmware builds for different hardware implementations?

Yes I would. Linking forms a tighter coupling than just placing the two parts side by side on a filesystem designed for general storage of byte streams. There is more to say about the situation than the naked

So, why didn't you say it when i posted my analysis to debian-legal a month ago and asked for comments ?

Quoted 7 lines

fact that that they are aggreated on the same medium; ergo the sutiation does not constitute *only* aggregation, and the "mere aggregation" language of the GPL does not apply.

In particular, the end of GPL #2 does not provide a blanket exception for all forms of aggregation; it specifically speaks about aggregation "on a volume of a storage or distribution medium".

Read my argumentation, comment on it, and be prepared to consider the same copy of the firmware as a derived work if shipped on a prom on the device itself.

Friendly,

Sven Luther

#6 lore raw
In reply to Henning Makholm
Quoted 8 lines

I think the "derivative work" angle is a red herring. I do not think that either of the two parts that are being linked together (i.e. the driver and the firmware) are derivates of the other. The relevant point is that distribution of the linked _result_ is nevertheless subject to the condition in GPL #2, which is in general the only source we have for a permission to distribute a non-verbatim-source form of the driver.

If the thing distributed is not the covered work and not a derivative work,
why does the GPL apply to it at all?

DS

#7 lore raw

Scripsit "David Schwartz" <[email protected]>

Quoted 10 lines
Quoted 7 lines

I think the "derivative work" angle is a red herring. I do not think that either of the two parts that are being linked together (i.e. the driver and the firmware) are derivates of the other. The relevant point is that distribution of the linked _result_ is nevertheless subject to the condition in GPL #2, which is in general the only source we have for a permission to distribute a non-verbatim-source form of the driver.

If the thing distributed is not the covered work and not a
derivative work, why does the GPL apply to it at all?

You are free to not apply the GPL to it.

However, then you cannot legally copy it at all, because it contains part of the original author's copyrightedwork and therefore can only legally be copied with the permission of the author.

Signature · 4 lines
Henning Makholm                   "The great secret, known to internists and
                         learned early in marriage by internists' wives, but
               still hidden from the general public, is that most things get
         better by themselves. Most things, in fact, are better by morning."
#8 lore raw
Quoted 11 lines

Scripsit "David Schwartz" <[email protected]>

Quoted 7 lines
Quoted 7 lines

I think the "derivative work" angle is a red herring. I do not think that either of the two parts that are being linked together (i.e. the driver and the firmware) are derivates of the other. The relevant point is that distribution of the linked _result_ is nevertheless subject to the condition in GPL #2, which is in general the only source we have for a permission to distribute a non-verbatim-source form of the driver.

Quoted 8 lines
Quoted 2 lines

If the thing distributed is not the covered work and not a
derivative work, why does the GPL apply to it at all?

You are free to not apply the GPL to it.

However, then you cannot legally copy it at all, because it contains part of the original author's copyrighted work and therefore can only legally be copied with the permission of the author.

The way you stop someone from distributing part of your work is by arguing
that the work they are distributing is a derivative work of your work and they had no right to *make* it in the first place. See, for example, Mulcahy v. Cheetah Learning.

My point is that the reason the derivative work issue is so important is
because it's the only way (in U.S. law anyway) that the GPL can apply to anything other than the exact thing the author chose to apply it to. The GPL applies to distributing a Linux binary I just made even though nobody ever chose to apply the GPL to the binary I just made only because the binary I just made is a derivative work of the Linux kernel, and the authors of that work chose to apply the GPL to it.

DS

#9 lore raw

(Henning Makholm, I assume; I seem to be missing the actual message and David's mailer forgot to put a quote header on the original reply):

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

I think the "derivative work" angle is a red herring. I do not think that either of the two parts that are being linked together (i.e. the driver and the firmware) are derivates of the other. The relevant

The two parts are not derivatives of each other, of course; that's obvious. (If I take your firmware, David's firmware loader, and link them together, I havn't change either of your works.) The resulting linked binary, however, is a derivative work of both.

I've heard the claim, several times, that that creating a derivative work requires creative input, that linking stuff together with "ld" is completely uncreative, therefore no derivative work is created. (I'm not sure if you're making (here or elsewhere) that claim, but it seems like it.) What's the basis for this claim? (If you're not making it, anybody that does believe this is free to respond.)

The case David referred to[1] says "A derivative work may itself be copyrighted if it has the requisite originality." This seems to imply that something can be a derivative work without creative input (though no new copyright would exist beyond that of the source objects). It seems that while "creative input" is required for copyright to exist, it is not required for creating a derivative work.

[1] http://caselaw.lp.findlaw.com/data2/circs/8th/033112p.pdf

Quoted 4 lines · David Schwartz

The way you stop someone from distributing part of your work is by arguing
that the work they are distributing is a derivative work of your work and they had no right to *make* it in the first place. See, for example, Mulcahy v. Cheetah Learning.

Er, that's one way, but not *the* way. I could grant you permission to create derivatives of my work, but not to redistribute them. To stop you from distributing them, I'd argue that you had no right to distribute them--you *did* have the right to make it in the first place.

The GPL does this. Note GPL #2b: "any work that you distribute or publish". If you don't distribute or publish the derivative work, the work does not need to be "licensed ... under the terms of this License." It very carefully separates the permissions granted for merely creating a derivative work, and the permissions granted for distributing those works; if you distribute a linked binary in violation of the GPL, you may very well have had permission to make it in the first place.

(Of course, if whether the work is a derivative is in question, that would need to be established--you would, indeed, need to argue that the work they are distributing is a derivative work--but you wouldn't necessarily further argue that they had no right to make it in the first place.)

Signature · 1 line
Glenn Maynard
#10 lore raw
Quoted 11 lines · David Schwartz
Quoted 8 lines

The way you stop someone from distributing part of your
work is by arguing
that the work they are distributing is a derivative work of your work and
they had no right to *make* it in the first place. See, for example, Mulcahy
v. Cheetah Learning.

Quoted 4 lines

Er, that's one way, but not *the* way. I could grant you permission to create derivatives of my work, but not to redistribute them. To stop you from distributing them, I'd argue that you had no right to distribute them--you *did* have the right to make it in the first place.

You could do that be means of a contract, but I don't think you could it do
by means of a copyright license. The problem is that there is no right to control the distribution of derivative works for you to withhold from me.

Quoted 11 lines

The GPL does this. Note GPL #2b: "any work that you distribute or publish".
If you don't distribute or publish the derivative work, the work does not need to be "licensed ... under the terms of this License." It very carefully
separates the permissions granted for merely creating a derivative work, and the permissions granted for distributing those works; if you distribute
a linked binary in violation of the GPL, you may very well have had permission
to make it in the first place.

Yes, but this would be valid if and only if there was a right to restrict
the distribution of derivative works that was recognized under copyright law. I can find no record of the existence of such a right.

Quoted 6 lines

(Of course, if whether the work is a derivative is in question, that would need to be established--you would, indeed, need to argue that the work they
are distributing is a derivative work--but you wouldn't necessarily further
argue that they had no right to make it in the first place.)

Well that's the problem. While copyright law does permit you to restrict
the right to create derivative works, it doesn't permit you to restrict the distribution of lawfully created derivative works to licensees of the original work. As far as I know, no law has ever granted this right to copyright holders and no court has ever recognized this right. And I've looked. Courts have specifically recognized the absence of this right.

DS

#11 lore raw
Quoted 6 lines · David Schwartz

Well that's the problem. While copyright law does permit you to restrict
the right to create derivative works, it doesn't permit you to restrict the distribution of lawfully created derivative works to licensees of the original work. As far as I know, no law has ever granted this right to copyright holders and no court has ever recognized this right. And I've looked. Courts have specifically recognized the absence of this right.

The GPL is very clear in its implementation: it grants wider permission to create derivative works than to distribute them, implementing its "virality" in terms of restrictions on distribution, not creation. So, it seems that you're claiming that the GPL is broken or unenforcable in some aspects. (If you're not, I'd like to know where I'm confused.)

If that's the case, it's a claim I'm not qualified to debate, but would be interested in hearing the FSF's response.

Signature · 1 line
Glenn Maynard
#12 lore raw
Quoted 12 lines · David Schwartz
Quoted 9 lines

Well that's the problem. While copyright law does permit
you to restrict
the right to create derivative works, it doesn't permit you to restrict the
distribution of lawfully created derivative works to licensees of the original work. As far as I know, no law has ever granted this right to copyright holders and no court has ever recognized this right. And I've looked. Courts have specifically recognized the absence of this right.

Quoted 3 lines

The GPL is very clear in its implementation: it grants wider permission to create derivative works than to distribute them, implementing its "virality" in terms of restrictions on distribution, not creation.

It doesn't even need to do this. First sale grants the right to use a work
one lawfully possesses. One cannot "use" the Linux kernel source without compiling it. So one doesn't need the GPL to create at least some derivative works.

Quoted 6 lines

So,
it seems that you're claiming that the GPL is broken or unenforcable in some aspects. (If you're not, I'd like to know where I'm confused.)

If that's the case, it's a claim I'm not qualified to debate, but would be interested in hearing the FSF's response.

It has always been the FSF's position that you don't need to agree to the
GPL to use the covered work. One cannot use the Linux kernel without compiling it and linking it. One cannot use a library without creating a work that uses the library, including the header files, and compiling/linking to form a result. So you can *create* a broad array of derivative works without invoking the GPL's restrictions (under first sale and how source code is ordinarily used).

The argument that you cannot distribute a derived work unless the GPL says
you can *because* you must have agreed to the GPL in order to lawfully create the derivative work is pure bunk. I don't know that the FSF relies upon the argument, however, it came up in this thread, which is why I refuted it (at least four times now). ;)

DS

#13 lore raw
In reply to David Schwartz
Quoted 4 lines · David Schwartz

You could do that be means of a contract, but I don't think you
could it do by means of a copyright license. The problem is that there is no right to control the distribution of derivative works for you to withhold from me.

While you are may be reporting your thoughts accurately, this problem doesn't seem to be a legal issue.

The GPL explicitly discusses this issue (section 5), and a number of people have already posted with similar commentary.

Anyways, one thing to keep in mind here is that if copyright law doesn't allow the GPL's grant of permission to be conditional then copyright law would not allow other copyright grants to be conditional.

Another way of looking at this is that the GPL is a copyright license -- it represents the terms and conditions under which copyrights are granted, and it also represents those permissions.

Signature · 1 line
Raul
#14 lore raw
In reply to Glenn Maynard
Quoted 6 lines · Glenn Maynard

I've heard the claim, several times, that that creating a derivative work requires creative input, that linking stuff together with "ld" is completely uncreative, therefore no derivative work is created. (I'm not sure if you're making (here or elsewhere) that claim, but it seems like it.) What's the basis for this claim? (If you're not making it, anybody that does believe this is free to respond.)

It's based on Title 17 USC, Sec. 101, where "derivative work" is defined:

A “derivative work” is a work based upon one or more preexisting works, such as a translation, musical arrangement, dramatization, fictionalization, motion picture version, sound recording, art reproduction, abridgment, condensation, or any other form in which a work may be recast, transformed, or adapted. A work consisting of editorial revisions, annotations, elaborations, or other modifications which, as a whole, represent an ORIGINAL WORK OF AUTHORSHIP, is a “derivative work”. (emphasis added)

#15 lore raw
In reply to David Schwartz

Scripsit "David Schwartz" <[email protected]>

Quoted 8 lines
Quoted 3 lines

However, then you cannot legally copy it at all, because it contains part of the original author's copyrighted work and therefore can only legally be copied with the permission of the author.

The way you stop someone from distributing part of your work
is by arguing that the work they are distributing is a derivative work of your work and they had no right to *make* it in the first place. See, for example, Mulcahy v. Cheetah Learning.

You don't need to argue that the thing being distributed is a derivative work. It is enough that it _contains_ your copyrighted work.

Quoted 4 lines

My point is that the reason the derivative work issue is so
important is because it's the only way (in U.S. law anyway) that the GPL can apply to anything other than the exact thing the author chose to apply it to.

The taske of the GPL is to _give permission_ when certain conditions hold. Therefore, if the GPL does not apply yet you still need permission from the author (beacuse what you're distributing contains his work), then you do not have that permission and cannot distribute _at all_.

I'm not sure whether meant instead that the original _copyright_ only influences things that are derivative works, but that would have even more bizarre consequences.

Quoted 5 lines

The GPL applies to distributing a Linux binary I just made even though nobody ever chose to apply the GPL to the binary I just made only because the binary I just made is a derivative work of the Linux kernel, and the authors of that work chose to apply the GPL to it.

How can the binary be a derivative work when it does *not* contain firmware, but suddenly cease to be a derivative work if one *does* add firmware into it?

Signature · 4 lines
Henning Makholm            "Vi skal nok ikke begynde at undervise hinanden i
                    den store regnekunst her, men jeg vil foreslå, at vi fra
             Kulturministeriets side sørger for at fremsende tallene og også
          give en beskrivelse af, hvordan man læser tallene. Tak for i dag!"
#16 lore raw
Quoted 10 lines
Quoted 6 lines

The GPL applies to distributing a Linux binary I just made even though nobody ever chose to apply the GPL to the binary I just made only because the binary I just made is a derivative work of the Linux kernel, and the authors of that work chose to apply the GPL to it.

How can the binary be a derivative work when it does *not* contain firmware, but suddenly cease to be a derivative work if one *does* add firmware into it?

Because, the argument would go, the binary with the firmware linked in is
not a work, it is two works that are aggregated because there's a license boundary between them. The argument would be that the binary with the firmware is *a* *derivative* *work* of the Linux kernel source. The "a" is a critical part of the argument that cannot be omitted. Showing that the linked binary was two works would be sufficient to significantly weaken the argument that it can't be distributed.

You can't argue that only the GPL gives you the right to distribute the
result, regardless of what it is, because there are other sources of such rights. These include fair use, first sale, and the fact that the law does not create a special right to restrict the distribution of lawfully-created derivative works (to licensees of the original work).

My point is not simply that the question of whether or not linking creates
a single work that is a derivative work of all the things linked is important to the question of whether you can distribute GPL'd works linked with non-GPL'd works. And the standard is copyright law, not what the GPL says. (Though that's also important, because then you would have even more rights.)

DS

#17 lore raw
In reply to David Schwartz
Quoted 2 lines · David Schwartz

I think we have a real problem, however, in cases where the source
file that holds only the firmware data contains a GPL notice.

Sure: the GPL notice isn't completely valid. But I think people have already decided that this is an issue that needs to be fixed. And, I think most of the approach for fixing these is fairly clear.

That said... perhaps it's worth going over a hierarchy of copyright issues:

First, there's the issue of whether or not work is protected by copyright. I think we're talking about stuff that's protected by copyright.

If it is protected by copyright, there's the question of whether the things being done with that work are regulated by copyright law. I think we're talking about activities (making copies of linux and distributing it) which are regulated by copyright law.

If both hold, the next question is whether or not the copyright license allows this use. As you've indicated, we do have some real issues here.

Finally, if you're dealing with regulated activity and the license doesn't allow it, it's up to the copyright holder to decide whether or not to prosecute. So far, the copyright holders haven't said much about these issues.

We probably have some issues where what we're doing is only by the good graces of the copyright holder(s). We should fix those things, of course, but currently there aren't any deadlines we have to meet.

Signature · 1 line
Raul
#18 lore raw
In reply to Henning Makholm
Quoted 9 lines · Henning Makholm

Scripsit Humberto Massa <[email protected]>

Quoted 4 lines

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.

http://lists.debian.org/debian-legal/2005/03/msg00273.html

and :

http://lists.debian.org/debian-legal/2005/03/msg00283.html

and the following thread. These where linked from the original mail in this thread.

Quoted 11 lines
Quoted 7 lines

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".

So read the analysis and comment on it if you disagree, but let's take it to debian-legal alone, ok ?

Friendly,

Sven Luther

#19 lore raw
In reply to Humberto Massa
Quoted 5 lines · Humberto Massa

This is where you are wrong IMMHO. All that is needed for you to distribute the hexdump blob under the GPL is a declaration from the copyright holder saying "this, to me, is the preferred form for modification of the firmware and hence the source code under the GPL."

I strongly disagree. This could be an open door to to anyone claiming that whatever binary is the prefered form of modification.

Friendly,

Sven Luther