Skip to contentSkip to conversation

Binary-only firmware covered by the GPL?

DISCUSSION Matt Reuther 3 participants 3 messages Mar 26, 2004

lore
Share & tools
lore
#0 lore raw

I think the real question is this: if this binary blob is not GPL, then how can it be in the kernel? It should be pulled out and put in a separate file, which can be loaded with the firmware mechanism.

If it is firmware, then would it be legal to reverse engineer the assembler, assuming one can find the instruction set for the chip?

Matt

_________________________________________________________________
Get rid of annoying pop-up ads with the new MSN Toolbar � FREE! http://toolbar.msn.com/go/onm00200414ave/direct/01/

#1 lore raw
Quoted 3 lines · Matt Reuther

I think the real question is this: if this binary blob is not GPL, then how can it be in the kernel? It should be pulled out and put in a separate file, which can be loaded with the firmware mechanism.

Correct.

Quoted 2 lines

If it is firmware, then would it be legal to reverse engineer the assembler, assuming one can find the instruction set for the chip?

That depends on your local jurisdiction.

Signature · 1 line
Matthew Garrett | [email protected]
#2 lore raw
Quoted 9 lines
Quoted 5 lines · Matt Reuther

I think the real question is this: if this binary blob is not GPL, then how
can it be in the kernel? It should be pulled out and put in a separate file,
which can be loaded with the firmware mechanism.

Quoted 7 lines

Correct.

Quoted 3 lines

If it is firmware, then would it be legal to reverse engineer the assembler,
assuming one can find the instruction set for the chip?

That depends on your local jurisdiction.

IANAL, but I believe you have the absolute right to reverse engineer and
modify it. All of that engineering and modification would be to/from a file that was placed under the GPL, and the GPL contains no restrictions against reverse engineering or modification. It specifically prohibits the imposition of any addional restrictions upon those who receive the file as far as how they can use, modify, and distribute it.

There might be a question if the reverse engineering exceeds the scope of
the file itself. For example, if you reverse engineer the hardware that the firmware runs on or if the firmware runs on a custom processor and you have to reverse engineer the processor itself. But I certainly think you can reverse engineer the contents of the firmware file (disassemble it) and make modified versions of that firmware with absolute impunity.

DS