1cb1a66aed921060fa34d161b52e95d05de18ec1
According to RFC 1350 and RFC 2347, TFTP server should answer RRQ by either OACK or DATA packet. Qemu's internal TFTP server answers RRQ with additional options by sending both OACK and DATA packet, thus breaking the "lock-step" feature of the protocol, and also confuses client. Proposed solution would be to, in case of OACK packet, wait for ACK from client and just then start sending data. Attached patch implements this. Signed-off-by: Thomas Horsten <thomas@horsten.com> Signed-off-by: Milan Plzik <milan.plzik@gmail.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
Read the documentation in qemu-doc.html. Fabrice Bellard.
Description
A QEMU emulator for legacy Apple devices
557 MiB
0 Stars
1 Watchers
0 Forks
Languages
C
82.9%
C++
6.4%
Python
3.3%
Dylan
2.9%
Shell
1.6%
Other
2.7%