mennovf

I would love to have this option as well. I currently have to disable '#' comments in the parser and preprocess the string to remove '#' line comments because the...

I was unaware of the ongoing effort on the next branch when I made this pull request. I could copy over its code into this pull request or just close...

> * Use a positive value to CONFIG_NET_RECV_BUFSIZE this way the readhead buffers are freed early Sadly this is not a solution as it is also bugged. The comparison is...

Yes that's the dual problem of what I'm experiencing. I think the essential issue is that neither write nor read should be able to starve the other's memory, so compiling...

> @mennovf with your change how to handle the case described by @zhhyu7 : > > If the sending direction is unthrottled, during the TCP sending process, if the buffer...

I think the THROTTLE option is a dead-end due to the TCP remarks. IMO the memory management needs an overhaul. In the meantime I can resolve my issue by fixing...

Yes, I will remove and squash all of this eventually, but thanks for pointing them out. I posted this as a draft for guidance on how to proceed. I will...

> * please don't create a completely new way of dealing with efuses. We should have the existing bits under `soc`, generated from the relevant csv I believe. The esp32s2...

I have put more time into figuring this out and have used a different board. I am now using the V2 version of the efuse where a line calibration is...