_florent_ changed the topic of #litex to: LiteX FPGA SoC builder and Cores / Github : https://github.com/enjoy-digital, https://github.com/litex-hub / Logs: https://libera.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
tpb has joined #litex
<zyp> I'd expect the last signal to both mark the end of a received packet and terminate a packet to be sent, but I haven't looked to see if it actually works that way
<rowang077[m]> at least the transmitting from the FPGA gives no control over sending packets. That's hardcoded by the send_level on the tx side. https://github.com/enjoy-digital/liteeth/blob/master/liteeth/frontend/stream.py#L11
<rowang077[m]> But I don't know enough about the migen/litex to understand what is going on the receive side
Degi_ has joined #litex
Degi has quit [Ping timeout: 240 seconds]
Degi_ is now known as Degi
FabM has joined #litex
FabM has joined #litex
<_florent_> Hi rowang077[m], the LiteEthStream2UDPTX/LiteEthUDP2StreamRX are packetizing/depacketizing the frames to simplify use, so don't give you delimiter control/status.
<_florent_> to have them, you have to compose/extract the packet with your logic and then work directly with the UDP Port.
<_florent_> I could however have a look to see if we could support it in LiteEthStream2UDPTX/LiteEthUDP2StreamRX, but that was not the initial aim
<rowang077[m]> @florent Clear! It's not that big of an issue for me right now. Just wanted to make sure for the RX side.
<rowang077[m]> _florent_: This is the right tag :)
<rowang077[m]> The only thing I'm worried about withouth having control over UDP packets is if a packet is lost. Let's say I transmit 1000 bytes "frame". Liteeth will make 2 udp packets out of that (as an example). The header consists of of some kind of packet id and a length. Now the second udp packet is dropped. The application has no way to detect this dropped packet except by adding a crc check. But even then you are now "desynchronized" in some
<rowang077[m]> unpredictable way.
<rowang077[m]> Basically since you have no control over packets you have to thread it as a lossy bytestream.
<rowang077[m]> instead of a lossy packet stream
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
MoeIcenowy has quit [Quit: ZNC 1.8.2 - https://znc.in]
MoeIcenowy has joined #litex
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
FabM has quit [Ping timeout: 268 seconds]
<mithro> _florent_: The University of Washington people behind bjump.org are looking at replacing their FPGA RTL with LiteX -> https://docs.google.com/drawings/d/1iXQW7JOGi_LUP37g6Y4jMcrJRuAju48vB42z3v-9pm4/edit
<tpb> Title: ASIC with FPGA Harness - Google Zeichnungen (at docs.google.com)
<_florent_> mithro: good choice :)
<_florent_> rowang077[m]: sorry, I haven't been able to have a look at your questions today, will do tomorrow
xenador77 has joined #litex
peeps has joined #litex
peeps[zen] has quit [Ping timeout: 244 seconds]