<sajattack[m]>
with my own litepcie_readl and litepcie_writel
<sajattack[m]>
not just bindings
shorne_ has joined #litex
<jevinskie[m]>
sajattack: I was able to make a litex_privesc runner for litex_sim that uses ambient capabilities to set up networking but I’m not sure if there is a capability for pcie access (same one as dev/mem maybe?)
<sajattack[m]>
I haven't used the sim much
<sajattack[m]>
I'm trying to run litex linux with the uart using litepcie
shorne has quit [Ping timeout: 256 seconds]
<sajattack[m]>
so I don't need a ftdi cable going into my pc basically lol
<sajattack[m]>
oh, you were referring to my question about the privileges
<sajattack[m]>
yeah it's probably whatever in linux mounts stuff with certain privileges
<sajattack[m]>
too lazy to google rn, happy to just chmod
pftbest has joined #litex
pftbest has quit [Remote host closed the connection]
pftbest has joined #litex
pftbest has quit [Remote host closed the connection]
pftbest has joined #litex
Coldberg has quit [Ping timeout: 252 seconds]
Coldberg has joined #litex
pauluzs has quit [Remote host closed the connection]
pauluzs has joined #litex
pftbest has quit [Ping timeout: 252 seconds]
pftbest has joined #litex
pftbest has quit [Remote host closed the connection]
pftbest has joined #litex
pftbest has quit [Ping timeout: 252 seconds]
pftbest has joined #litex
pftbest has quit [Remote host closed the connection]
pftbest has joined #litex
pftbest has quit [Ping timeout: 252 seconds]
peepsalot has quit [Read error: Connection reset by peer]
<bluecmd>
sajattack: did you manage to figure out your PCIe issue in the end?
<sajattack[m]>
not for linux-vexriscv
<sajattack[m]>
I've got the litex-boards pcie working
<sajattack[m]>
but the linux just seems broken when I try to add pcie to it
<kbeckmann>
_florent_: Just an update regarding the SDRAM read latency we discussed earlier: I managed to get the latency down to 10 cycles in the worst case (@50MHz). I changed to 1:1 gearing, and a 16 bit read port. I also drive the bus data signals with the read port directly while rdata.valid is high, so saved a cycle there too. I disable the refresh timer while a transaction is active (~100us in the worst
<kbeckmann>
case). Have tested it now with default speeds and it seems to work quite well.
pftbest has joined #litex
<jevinskie[m]>
kbeckmann: awesome news! :)
<jevinskie[m]>
I realized I can get 128 bits, four words per DFI cycle not one as I was misunderstanding, on the arty and that might just make my SPI emulator feasible with enough readahead
<jevinskie[m]>
@florent: is it expected that the sdram_calib will KO with errors on an arty with current, unmodified litex repos? That’s what I’m seeing even though the memtest reports OK