<tweakoz>
@Dolu - Is there an ETA for general Fpu and Amo support for mainline litex (for standard vexriscv, not vexriscv_smp) - I cannot get any soc to build with vexriscv_smp due to build errors. I also tried updating the VexRiscV repo in pythondata-cpu-vexriscv and I failed miserably there as well. I was able to build a verilog with the features directly from the current head of master of the VexRiscV using sbt - and I tried addin
<tweakoz>
g my variant to litex's variant list and it tried to use it, but failed (due to version mismatches I am sure) - So what would be the easy quick and dirty way to get functional IMACFD (+AMO) RiscV32 support into a litex SOC ?
<tweakoz>
actually I only need IMAFD (+AMO) RiscV32 (I dont need compression)
<tweakoz>
@Florent - what basic testing do you need done before I submit a pull request for litex-boards ? - I have a couple of boards I have got working and would like to merge (Nexys4, CmodA7, and Mercury2)
<tweakoz>
And not just testing, are there any specific requirements you need met to accept new board submissions ?
<tweakoz>
@Florent - I also have been working on a nanokernel based on top of litex bios / libbase that supports threads, memory allocation and other basics to get a minimal usable modern c++ system up. The nanokernel is itself written in c++ (because that is my native language and I work fastest in it) - I could port it to straight c after I work out a few of the issues - Is this something the litex repo would be interested in integ
<tweakoz>
rating as an optional firmware ? I myself decided for some projects I did not want the baggage of a full OS, but I wanted something a little more than litex bios offered. I could package it in a library and the user would just call a function in main() to transfer control to the nanokernel.
<tweakoz>
although maybe its not as useful for everyone - it is RiscV only.. to make everyone happy it would have to support all the CPU's
<tweakoz>
my little test program running on the nanokernel I think is about 40-60K of executable and runs fine even on a cmod-a7 - I am sure it would shrink a bit more if I ported to C.
Degi_ has joined #litex
Degi has quit [Ping timeout: 258 seconds]
Degi_ is now known as Degi
tweakoz has quit [Remote host closed the connection]
tweakoz has joined #litex
tweakoz has quit [Ping timeout: 268 seconds]
tweakoz has joined #litex
tweakoz_ has joined #litex
tweakoz has quit [Read error: Connection reset by peer]
pftbest has quit [Remote host closed the connection]
pftbest has joined #litex
_franck_ has quit [Ping timeout: 272 seconds]
_franck_3 is now known as _franck_
Coldberg has quit [Remote host closed the connection]
Coldberg has joined #litex
Coldberg has quit [Ping timeout: 258 seconds]
pftbest has quit [Remote host closed the connection]
<_florent_>
tweakoz: Hi, if the boards you want to add to LiteX-Boards are able to run the basic LiteX SoC, you can consider it's OK to create a PR.
pftbest has joined #litex
Coldberg has joined #litex
<_florent_>
tweakoz: For the nanokernel, that's definitely something interesting and I would be really curious to learn more about it. For now we are trying to keep software simple in LiteX, so not sure we could merge it directly, but that's clearly something we could encourage users to use if the have similar needs.