Friday, 2019-11-22

*** tpb has joined #litex00:00
*** nrossi has joined #litex01:09
*** rohitksingh has quit IRC02:24
*** freemint has quit IRC08:25
*** freemint has joined #litex08:35
*** CarlFK has joined #litex08:58
*** freemint has quit IRC09:10
*** freemint has joined #litex09:15
*** freemint has quit IRC11:02
*** freemint has joined #litex11:03
_florent_davidc__: re CommUDP, that's probably a mistake, i'll test with one socket and will fix if working11:32
*** freemint has quit IRC12:05
*** freemint has joined #litex12:21
*** freemint has quit IRC13:39
*** freemint has joined #litex14:43
*** freemint has quit IRC14:51
*** freemint has joined #litex15:37
*** ambro718 has joined #litex16:43
davidc___florent_: I have it tested with one socket, and it works for me. Though - I don't know what you're using it with (because it was binding to a weird port, anything that talked to it had to hardcode the return port)17:06
davidc___florent_: saw your patch - the socket.bind should be superfluous because sendto() is called first. The current patch won't support two clients on one host, or the client and server on the same host, since they'll try and use the same UDP port17:53
davidc__IIRC, just dropping socket.bind() should be fine17:54
*** CarlFK has quit IRC18:03
*** freemint has quit IRC18:58
*** nrossi has quit IRC19:07
*** freemint has joined #litex19:10
*** freemint has quit IRC19:47
*** CarlFK has joined #litex20:35
*** freemint has joined #litex20:40
*** freemint has quit IRC21:24
_florent_davidc__: thanks, i'll test without socket.bind()22:30
davidc___florent_: it might require a tweak to the server code; some of the server code I saw was explicitly specifying the port on the client-side (which is strange)22:34
davidc__rather than just returning to whatever the src port on the client was22:34
_florent_davidc__: feel free to create issue/send pull request on this if you think things could be improved22:37

Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!