On Wed, May 14, 2014 at 4:14 AM, Olof Kindgren <[email protected]>wrote:
> > I second that, having a more permissive license on that file would > > make a lot more sense. > > You need that or a similar file in basically any software project > > using OR1K, so all a too restrictive license do is prevent people from > > using openrisc. > > Unfortunately, that file has been composed by a large number of people > > over the year, so I don't think we can change the license of _that_ > > file without their permission. > > Tracking people down just to get a non-gpl license on that file seems > > like a lot of trouble though. > > That's why I suggested on IRC to make a "cleanroom" version of it by > > generating a new file from e.g. > > https://github.com/openrisc/mor1kx/blob/master/rtl/verilog/mor1kx-sprs.v > Ok, that's a good idea. I'll drop the copy I have and start from scratch. But if I generate it with a script that reads that file, the result will also be OHDL, right? Is that permissive enough? > Yes! I love this. Have had the same idea about a or1k-headers package > that everything else can depend on. > > FYI we have two open bugs about this as well, so please put some info > there when things are starting to move > http://bugzilla.opencores.org/show_bug.cgi?id=58 > http://bugzilla.opencores.org/show_bug.cgi?id=59 > > Also agree on using a BSD-style licensing for this file, and renaming > it to or1k-spr-defs.h or whatever > I think a 1-clause BSD license is appropriate. (See: https://urchin.earth.li/~twic/The_Amazing_Disappearing_BSD_License.html) I don't see any reason to restrict distribution of binaries compiled using these headers, since the headers won't contain any function prototypes. I only think it's important that the copyright notices on the source files themselves are maintained. > Do we have more files that could go in the header package? > I'm also going to add or1k-asm.h, which I wrote, so changing the license is simple. -Pete
_______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
