Replies: 1 comment 2 replies
-
It's very nice of you to ask! But I don't think it's necessary at all. Your CFU code is everything but similar to the original sources; so this is really your code and all the credit goes to you. Furthermore, CFU and CFS are literal submodules of this processor, which cannot function on their own. So it is clear where they come from. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have to add the code that I have elaborated in an appendix as code listings for my thesis, part of this code is neorv32_cp_cfu.vhd and neorv32_cfs.vhd modified versions for my use case; also there is my custom top module and testbench which are code snippets of the NEORV32 project stitched together in a snigle file.
Should I include the copyright notice on top of those files as stated by the BSD3 License or is it enough to add a caption with an IEEE citation to the github repository?
If so is it necessary for the top module and testbench too since they are code snippets stitched together?
For example neorv32_cp_cfu.vhd is:
Beta Was this translation helpful? Give feedback.
All reactions