From: "Hervé Poussineau" <hpoussin@reactos.org>
To: qemu-devel@nongnu.org
Cc: "Jan Kiszka" <jan.kiszka@siemens.com>,
"Hervé Poussineau" <hpoussin@reactos.org>
Subject: [Qemu-devel] [PATCH v3 0/2] slirp: tftp server improvements
Date: Thu, 13 Sep 2012 07:54:59 +0200 [thread overview]
Message-ID: <1347515701-5513-1-git-send-email-hpoussin@reactos.org> (raw)
These patches have already been sent in April 2011, and contain some fixes for the internal TFTP server.
With these patches, MS Windows PE can be booted via PXE, and 32MB file limitation has been removed.
This has been tested with MS Windows 2003 PXE boot client, PXELINUX and gPXE.
Indentation seems a little bit off in patch 2/2, because surrounding code indentation is one tab followed by spaces. I've indented new lines by replacing the tab by 8 spaces.
Patch 1/2 also has indentation errors reported by checkpatch.pl, but I kept indentation consistent.
Changes v1 -> v2
- rebased
- updated with Aurélien Jarno remarks
- improved commit messages
Changes v2 -> v3
- removed patch 1/3, already applied to slirp queue
- updated with Jan Kiszka remarks
Hervé Poussineau (2):
slirp: Handle more than 65535 blocks in TFTP transfers
slirp: Implement TFTP Blocksize option
slirp/tftp.c | 66 ++++++++++++++++++++++++++++++++++++++--------------------
slirp/tftp.h | 1 +
2 files changed, 44 insertions(+), 23 deletions(-)
--
1.7.10.4
next reply other threads:[~2012-09-13 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 5:54 Hervé Poussineau [this message]
2012-09-13 5:55 ` [Qemu-devel] [PATCH v3 1/2] slirp: Handle more than 65535 blocks in TFTP transfers Hervé Poussineau
2012-09-13 10:50 ` Jan Kiszka
2012-09-13 5:55 ` [Qemu-devel] [PATCH v3 2/2] slirp: Implement TFTP Blocksize option Hervé Poussineau
2012-09-13 8:39 ` Jan Kiszka
2012-09-13 19:56 ` Hervé Poussineau
2012-09-13 22:28 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1347515701-5513-1-git-send-email-hpoussin@reactos.org \
--to=hpoussin@reactos.org \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).