> As for the copyright, I haven't been able to find much information on > whether or not generated files are even copyrightable. One might > argue that they > don't have sufficient 'creative value' to be copyrightable. Or > arguably, they are as copyrightable by the generator author as by the > author or the .mhs file. > I admit in this case, I've followed the safe route by claiming a > copyright, which at least at Xilinx has significant precedent. Also, thinking about your idea of sticking bits in BRAM etc... what would be nice would be the ability to "merge" trees. We've been talking about that multiple times, it would be useful at several levels: - We could provide pre-made DTs for known CPUs (ie, 440GP, 440GX, 405EX, ...) - Boards can then include that, and then "override" some properties (clocks, PHY wiring, ...) - That could be done at the binary level too so that the BRAM contains on "overlay" on top of the base ref. platform device-tree that comes with the kernel for example. This is slightly different between doing that in the .dts source via some kind of #include vs. doing that by merging blobs but we could make it be essentially be the same internally: The #include generates a blob that is then "merged in". Just random thoughts... Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
