Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Mar 16 20:22
    hchenji opened #191
  • Mar 08 2021 23:54

    imphil on master

    Add LibreCores badge (compare)

  • Jan 16 2021 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)

Olof Kindgren
@olofk
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.
https://summerofcode.withgoogle.com/dashboard/organization/5353749657157632/proposal/4747401538043904/
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.