Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Mar 08 23:54

    imphil on master

    Add LibreCores badge (compare)

  • Jan 16 02:53
    hchenji commented #189
  • Dec 10 2020 17:53
    hchenji commented #190
  • Dec 10 2020 15:52
    hchenji commented #189
  • Dec 02 2020 19:23
    koenenwmn commented #189
  • Nov 25 2020 23:32
    imphil commented #189
  • Nov 25 2020 23:28
    imphil reopened #189
  • Nov 25 2020 23:28
    imphil commented #189
  • Nov 25 2020 23:28
    imphil closed #189
  • Nov 25 2020 23:28
    imphil commented #189
  • Nov 24 2020 00:01
    hchenji commented #189
  • Nov 20 2020 08:04
    deadspace99 commented #189
  • Nov 09 2020 17:13
    hchenji commented #189
  • Nov 08 2020 10:57
    deadspace99 commented #189
  • Nov 07 2020 11:48
    deadspace99 opened #190
  • Nov 03 2020 18:05
    hchenji opened #189
  • May 16 2020 14:24
    ppenna unassigned #82
  • May 04 2020 22:12

    imphil on master

    README: Fix name of license file (compare)

  • May 04 2020 21:29

    imphil on master

    Update README Make it a bit mo… (compare)

  • May 04 2020 21:29
    imphil closed #188
Pedro Henrique Penna
@ppenna
thanks for the directions @imphil
Pedro Henrique Penna
@ppenna
Dear all, I shall start working on the points that we have discusses last hangouts Session today...
I'll let you know about my progress.
Philipp Wagner
@imphil
great, thanks!
Pedro Henrique Penna
@ppenna
@imphil I have worked on the documentation for building Linux this morning. Could you take a look on it before I open a PR to the upstream optimsoc-web? https://github.com/ppenna/optimsoc-web/blob/master/_posts/2017-09-04-gsoc2917.md
Pedro Henrique Penna
@ppenna
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
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
thats unfortunate its pretty fast
Created a pr to fix it
openrisc/mor1kx#57
Plus I have an old PR still open
openrisc/mor1kx#56
@olofk what are your tips for managing local development versions of cores with fusesoc? I have my local versions ahead of fusesoc-cores and orpsoc-cores in my PATH
but... sometimes if I don't have the versions just right it takes the non local versions
So I have to be very careful and always do fusesoc core-info and watch which versions are pulled in
Olof Kindgren
@olofk
Yeah, same here
You can keep multiple workspaces with different fusesoc.conf
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
ah, that might be nice
Olof Kindgren
@olofk
Or if you're just working on a specific core, you can pull that one in with fusesoc --cores-root=/path/to/core sim ...
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
that is good too, I didn't know
need to read the manual
Thanks, I thought I would ask while I have your attention :)
Olof Kindgren
@olofk
Reading the manual won't help you much :)
I think it would be nice to extend list-cores to also show locations of the cores. That way you don't have to run core-info for every single one
You should get on https://gitter.im/librecores/fusesoc to get the latest news too :)
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
Hi @imphil @wallento looks like I'm signed up to help work on a gsoc project to improve osd.
Can you view that link. If not I'll give you the details.
Philipp Wagner
@imphil
@stffrdhrn is it the core debug module proposal in timvideos?
Shivam Aggarwal
@shivmgg
Hi @stffrdhrn , I am a GSoC'18 student working on the project to integrate OSD into Litex firmware. Can you please check your mail?
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
@imphil thanks for the mail it really explained exactly what I was thinking of.