ah ok, I'll look briefly through the PR, a more substantial review probably can be done by Stafford ahead of sending it to LKML
on the report, I'm looking through it right now
Pedro Henrique Penna
@ppenna
Ty... I still need to write the building and testing section... I should finish it after Lynch
Ler me know what are you expecting there, if anything especial
Philipp Wagner
@imphil
will do
Philipp Wagner
@imphil
@ppenna I've added some comments to the document. Make sure to keep the deadline from google in mind. Until this time you need to publish that to your blog and give the URL to google in the final evaluation form.
Pedro Henrique Penna
@ppenna
Surge
**sure ty
Philipp Wagner
@imphil
most importantly, the report needs to list all prs and other code contributions that you made
@ppenna hm, strange. I've created the readme and somehow it got removed again!?
anyways, its there again and I can also fork the repo now
Pedro Henrique Penna
@ppenna
now it works!
Philipp Wagner
@imphil
@ppenna I've looked through the report again, looks mostly good! Please open a issue on GitHub for the two remaining issues you mentioned at the end so that can get tracked (and also link to the issue # in your report)
Pedro Henrique Penna
@ppenna
@imphil thanks! I'm working on the pull requests... Once I'm done with that I'll open the issues
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
Hello, sorry I missed the call, yesterday was a long day I was in bed a few hours before the meeting
If it is ok for you, let me know which task I should work on next: dib in the interrupt system bug or update the documentation for the NoC driver
@imphil the blog post has the build instructions for Linux on OpTiMSoC. I thought that the documentation of the driver itself should be on the Linux source tree... but I don't know...
Philipp Wagner
@imphil
@ppenna Thanks for the blog post draft. How about making a bit more of a story what you did, and possibly add a nice screenshot or a screencast of how things are working? Let's get people excited about what you did!
Pedro Henrique Penna
@ppenna
@imphil sure. I was saving that for the final implementation, but I guess that you want to have something closer to the report that I have written, right?
Philipp Wagner
@imphil
@ppenna in a project like that, there's never a "final" version :) Just take the chance of GSoC ending to tell the world what you did and how much better the world is now :)
Pedro Henrique Penna
@ppenna
=D
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
Hello. It's a bit late maybe but I put some comments on the Linux pull request and the gsoc gdoc
Olof Kindgren
@olofk
@stffrdhrn The latest fix for mor1kx with Icarus broke modelsim :/
** Error: ../src/mor1kx_5.0-r2/rtl/verilog/mor1kx_cpu_cappuccino.v(1132): External function 'mor1kx_rf_cappuccino.calc_rf_addr_width' may not be used in a constant expression.
** Error: ../src/mor1kx_5.0-r2/rtl/verilog/mor1kx_cpu_cappuccino.v(1132): Parameter value must be constant.
woah... that wasn't my intention :)
MAKE IT BIG
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
Ah
But not quartus or iverilog
Any suggestion? Make the function
Sorry. I leave
I mean. Move the function to utils?
Olof Kindgren
@olofk
That's probably a good idea. Should be pretty tool-agnostic
And just pull in the function with an `include, you mean ?
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
Yes
Philipp Wagner
@imphil
it's too bad icarus verilog is not supporting any recent SV standards, so it's become pretty much unusable on my side