On Sat, Nov 22, 2008 at 07:39:10PM +0000, paul_c wrote:
> As has already been pointed out, there is one file (as an example) claiming
> to
> be GPL2, pluto_step_rbf.h - In it's self, an autogenerated file from
> pluto_step.rbf - The HDL sources are labelled as "GPL ver 2 or later"..
> Now, if Epler can provide the tools to generate the intermediate rbf file
> then
> the GPL T&C can be satisfied.
Paul,
Thanks for giving me a chance to clarify this.
The pluto_step.rbf file is built from the source files in
pluto_step_firmware using the proprietary Quartus II development
environment from Altera.
The process of building in the Quartus GUI seems unscriptable; instead,
I describe the process in prose in the manual:
The src/hal/drivers/pluto_servo_firmware/ and
src/hal/drivers/pluto_step_firmware/ subdirectories contain the
Verilog source code plus additional files used by Quartus for the
FPGA firmwares. Altera's Quartus II software is required to rebuild
the FPGA firmware. To rebuild the firmware from the .hdl and other
source files, open the .qpf file and press CTRL-L. Then, recompile
emc2.
Like the HAL hardware driver, the FPGA firmware is licensed under
the terms of the GNU General Public License.
The gratis version of Quartus II runs only on Microsoft Windows,
although there is apparently a paid version that runs on Linux.
http://linuxcnc.org/docs/html/hal_drivers.html#r1_8_7
As described in the gpl version 2 faq, the use of a proprietary
toolchain is not problematic in gpl2 software:
Q: Can I release a program under the GPL which I developed using
non-free tools?
A: Which programs you used to edit the source code, or to compile it,
or study it, or record it, usually makes no difference for issues
concerning the licensing of that source code.
However, if you link non-free libraries with the source code, that
would be an issue you need to deal with. It does not preclude releasing
the source code under the GPL, but if the libraries don't fit under the
“system library” exception, you should affix an explicit notice giving
permission to link your program with them. The FSF can give you advice
on doing this.
http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#NonFreeTools
(pluto_step and pluto_servo do not use any "libraries", they just use
the standard facilities of the verilog language)
Jeff
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
