Skip to contentSkip to conversation

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

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

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 8 lines · David Schmitt
Quoted 4 lines · Jes Sorensen

[snip] 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 5 lines

Then I would like to exercise my right under the GPL to aquire the source code for the firmware (and the required compilers, starting with genfw.c which is mentioned in acenic_firmware.h) since - as far as I know - firmware is coded today in VHDL, C or some assembler and the days of hexcoding are long gone.

First, there is *NOT* any requirement in the GPL at all that requires making compilers available. Otherwise it would not be possible, for instance, have a Visual Basic GPL'd application. And yes, it is possible.

Second, up until the present day I have personal experience with hardware producers that do not have enough money to buy expensive toolchains and used a lot of hand-work to code hardware parameters. So, at least for them, hand-hexcoding-days are still going.

HTH,

Massa

#2 lore raw
Quoted 20 lines · Humberto Massa
Quoted 8 lines · David Schmitt
Quoted 4 lines · Jes Sorensen

[snip] 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 5 lines

Then I would like to exercise my right under the GPL to aquire the source code for the firmware (and the required compilers, starting with genfw.c which is mentioned in acenic_firmware.h) since - as far as I know - firmware is coded today in VHDL, C or some assembler and the days of hexcoding are long gone.

First, there is *NOT* any requirement in the GPL at all that requires making compilers available. Otherwise it would not be possible, for instance, have a Visual Basic GPL'd application. And yes, it is possible.

Quoted 8 lines

Second, up until the present day I have personal experience with hardware producers that do not have enough money to buy expensive toolchains and used a lot of hand-work to code hardware parameters. So, at least for them, hand-hexcoding-days are still going.

HTH,

Massa

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.

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.

This whole thread and gotten truly bizarre.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.11 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached for review by Dictator Bush.
98.36% of all statistics are fiction.

#3 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Richard" == Richard B Johnson <[email protected]> writes:

Richard> Last time I checked, GPL was about SOFTware, not FIRMware, Richard> and not MICROcode.

Oh be real, there's no real difference between them and you know it. It's all about where the bits are stored and what they tend to do in a system design that makes the difference.

This entire arguement is meaningless until someone posts the patches to move firmware out of the kernel, and until I see that, it's not
worth re-hashing. And no, I don't have the time or knowledge to do
this.

John

#4 lore raw
In reply to Richard B. Johnson
Quoted 3 lines · Richard B. Johnson

Last time I checked, GPL was about SOFTware, not FIRMware, and not MICROcode. If somebody has decided to rename FIRMware to SOFTware,

Debian has undertaken to change the meaning of a whole lot of words, including "software" and "free".

Quoted 1 line

This whole thread and gotten truly bizarre.

Surprised?

Signature · 2 lines
Måns Rullgård
[email protected]
#5 lore raw
In reply to Richard B. Johnson
Quoted 5 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.

The GPL doesn't forbid that. The GPL forbids to put this microcode directly in the same binary as the GPL code. Of course, nothing forbids some GPL'ed code to take a binary elsewhere and to upload it into the hardware.

At least that's my opinion; AIUI, Sven Luther believes it is possible if the firmware has a decent (but not necessarily free) license.

Signature · 4 lines
 .''`.           Josselin Mouette        /\./\
: :' :           [email protected]
`. `'                        [email protected]
   `-  Debian GNU/Linux -- The power of freedom
#6 lore raw
Quoted 11 lines · Josselin Mouette
Quoted 5 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.

The GPL doesn't forbid that. The GPL forbids to put this microcode directly in the same binary as the GPL code. Of course, nothing forbids some GPL'ed code to take a binary elsewhere and to upload it into the hardware.

No, i am arguing, that we can consider here the binary as a media distribution, in the same way as we would clearly separate the compressor from the compressed data in a auto-uncompressing executable, or the firmware from the firmware flasher in a all-in-one firmware upgrade binary.

Quoted 2 lines

At least that's my opinion; AIUI, Sven Luther believes it is possible if the firmware has a decent (but not necessarily free) license.

Indeed, the sole problem is that the current copyright and licencing attributions de-facto sets those firmware blobs under the GPL, which of course makes them undistributable since the GPL clearly claims that we need source code for it, and if any condition of the GPL fails, the program becomes undistributable as a whole.

Friendly,

Sven Luther

#7 lore raw
In reply to Humberto Massa

Hi,

Quoted 6 lines · Humberto Massa

First, there is *NOT* any requirement in the GPL at all that requires making compilers available. Otherwise it would not be possible, for instance, have a Visual Basic GPL'd application. And yes, it is possible.

From section 3 of the GNU GPL, version 2:

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

I take that to mean the compiler's exempted if it's the normal one available on the platform, but if the software distributor had to modify gcc to produce the binaries it's distributing then you're entitled to the compiler too.

So a Visual BASIC application uses a standard VB compiler, but that's not necessarily the case for a Linux kernel running on an embedded box.

Cheers,

Ralph.