devkitPro

Hmmm, I now see that setting the timer to 25ms will not work as thought. The time difference is compared using ">" and not ">=" which means that timer packet sending will only be triggered every other timer interrupt. So with my patch timer based packets will still be sent every 50ms. However, as ...

Index: arm9/source/sgIP_TCP.c =================================================================== --- arm9/source/sgIP_TCP.c (revision 4063) +++ arm9/source/sgIP_TCP.c (working copy) @@ -316,6 +316,8 @@ tcpseq=htonl(tcp->seqnum); datalen=mb->totallength-(tcp->dataofs_>>4)*4; shouldReply=0; + if ...

Ok, things are looking very good now. I want to thank you for dswifi, after my small changes it works very good for me. Now will I have to iron out the bugs in the networking code of my game... One problem I had at the end was that I included the "sgIP_errno.h" file instead of "errno.h" and error ...

Yeah, I know the feeling. And I didn't really expect you to be too happy about me mucking around in there trying to get you to fix things instead of working on the next version :) But if I submit a patch with my changes will you consider checking if it's worth applying? I think that with my small ...

Thanks for your reply! I have some new comments. The reason it still sends 3 packets in both directions for each exchange is that sgIP_TCP_ReceivePacket() will set shouldReply whenever data was acked in the incoming packet. This means that the the first packet is the payload packet, this is directly ...

Well, it looks like replying to packets with payload works as good as my first change. This should also handle the re-ack of resent data case. Some more comments: - If I read the source correctly SGIP_TCP_TRANSMIT_IMMTHRESH=40 will avoid sending a packet directly until the send buffer contains at ...

Ok, thx! If you wait a week or so I will probably have a patch with some small changes for what works good for me and you can review it and see if it makes sense. One thing I am curious about is if the comment "Fixed bug causing lib to not re-ack data packets that were resent." to the original ...

Aight, then I probably won't spend that much time trying to get more out of TCP before I start using UPD instead. Thanks for the info.

Yeah, you are probably right. At the first I simply wanted to get something up and running and selected TCP instead of UPD. I still imagine switching to UDP. But I think I will spend some time trying to optimize tcp-communication in dswifi for my game. After all it took some time to learn how things ...

I have some findings in the DS Wifi layer that I'm currently trying to use with my homebrew game to communicate DS<->DS using tcp. I have experienced problems with slow communication and that the communication hangs after a while. As of now I have found out that the hang was caused by using a DSi XL ...