cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #litex
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #litex
Degi_ has joined #litex
Degi has quit [Ping timeout: 246 seconds]
Degi_ is now known as Degi
indy_ has joined #litex
nanoric[m] has joined #litex
<nanoric[m]>
Hello, I'm new to FPGA. Am I free to ask questions about FPGA here?
<sensille>
nanoric[m]: i'm not the owner of this channel but i'd say it is quiet enough that you can. there's also ##fpga which is just general fpga talk with regular newbie questions
<sensille>
(and it is very inconvenient to have to click on a link to see your question, i'm on the irc side)
<nanoric[m]>
sensille: Thank you for your recommand!
<sensille>
my question would be, how do you know it is many clocks later?
<nanoric[m]>
Because I can wait many clocks later to read it. Read operation is not eager.
<nanoric[m]>
For example, I have a single to control the write from clock A, and another signal to control the read from clock B. The two signals are far apart in time.
<nanoric[m]>
* in time(eg, 10 or more clocks).
<sensille>
nanoric[m]: it should work (3 cycles should be plenty). the document might offer more solutions