From: "Hervé Poussineau" <hpoussin@reactos.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Herve Poussineau <hpoussin@reactos.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] slirp: Implement TFTP Blocksize option
Date: Sun, 17 Apr 2011 20:16:00 +0200 [thread overview]
Message-ID: <4DAB2E60.4080503@reactos.org> (raw)
In-Reply-To: <20110416091525.GA22205@stefanha-thinkpad.localdomain>
Hi,
Yes, I've tried booting with PXELINUX and gPXE, and I didn't see any
problem.
Hervé
Stefan Hajnoczi a écrit :
> On Mon, Apr 11, 2011 at 07:10:52PM +0000, Herve Poussineau wrote:
>
>> From: Herv? Poussineau <hpoussin@reactos.org>
>>
>> This option is described in RFC 1783. As this is only an optional field,
>> we may ignore it in some situations and handle it in some others.
>> Here, if client requests a block size bigger than the block size we emit
>> (512 bytes), accept the option with a value of 512
>>
>> Signed-off-by: Herv? Poussineau <hpoussin@reactos.org>
>> ---
>> slirp/tftp.c | 40 ++++++++++++++++++++++++++++++++--------
>> 1 files changed, 32 insertions(+), 8 deletions(-)
>>
>
> Have you tested PXELINUX and gPXE?
>
> Stefan
>
>
>
next prev parent reply other threads:[~2011-04-17 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 19:10 [Qemu-devel] [PATCH 0/3] slirp: misc fixes Herve Poussineau
2011-04-11 19:10 ` [Qemu-devel] [PATCH 1/3] slirp: Implement TFTP Blocksize option Herve Poussineau
2011-04-11 19:10 ` [Qemu-devel] [PATCH 2/3] slirp: Handle more than 65535 blocks in TFTP transfers Herve Poussineau
2011-04-11 19:10 ` [Qemu-devel] [PATCH 3/3] slirp: improve TFTP performance Herve Poussineau
2011-04-18 14:04 ` Aurelien Jarno
2011-04-18 14:02 ` [Qemu-devel] [PATCH 2/3] slirp: Handle more than 65535 blocks in TFTP transfers Aurelien Jarno
2011-04-16 9:15 ` [Qemu-devel] [PATCH 1/3] slirp: Implement TFTP Blocksize option Stefan Hajnoczi
2011-04-17 18:16 ` Hervé Poussineau [this message]
2011-04-17 19:53 ` Stefan Hajnoczi
2011-04-17 12:39 ` Avi Kivity
2011-04-18 14:02 ` Aurelien Jarno
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=4DAB2E60.4080503@reactos.org \
--to=hpoussin@reactos.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.