*** tpb has joined #litex | 00:00 | |
*** tweakoz has joined #litex | 02:01 | |
*** rohitksingh_work has joined #litex | 05:12 | |
*** rohitksingh_wor1 has joined #litex | 05:27 | |
*** rohitksingh_work has quit IRC | 05:27 | |
*** tweakoz has quit IRC | 09:32 | |
daveshah | somlo: seems the problem is between c907899 and the yosys 0.9 rc (so not from the abc9 PR). I'm bisecting it now | 11:19 |
---|---|---|
*** rohitksingh_wor1 has quit IRC | 13:09 | |
somlo | daveshah: just noticed you said you were bisecting -- missed this when I got into the office earlier this morning :) Thanks again for the fix | 15:05 |
* somlo goes to work on updating to the new LiteX memory map... | 15:05 | |
_florent_ | somlo: if you want to keep the old memory map for you SoC, you can still force it to the old memory map by doing something similar to this: https://github.com/litex-hub/linux-on-litex-vexriscv/blob/master/soc_linux.py#L25-L33 | 16:02 |
tpb | Title: linux-on-litex-vexriscv/soc_linux.py at master · litex-hub/linux-on-litex-vexriscv · GitHub (at github.com) | 16:02 |
somlo | _florent_: it looks like main ram is still at 0x4000_0000, and all I need to do for the rest is update the DTS blob I'm compiling into BBL | 17:03 |
somlo | so I think I'll be OK for now... | 17:04 |
somlo | however (and feel free to ignore me, just thinking out loud here) -- I'm wondering how much of a disruption, and how difficult it would be to *swap* the MMIO/CSR/etc. and main-ram around the 0x8000_0000 boundary -- have uncached accesses below that address, and cached above | 17:05 |
somlo | based on the intuition that main-ram might grow bigger, faster than the need for MMIO/CSR register space | 17:06 |
_florent_ | somlo: yes i also want to see if we can improve that | 17:45 |
*** tweakoz has joined #litex | 19:38 | |
*** Dolu has quit IRC | 21:00 | |
*** Dolu has joined #litex | 23:01 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!