From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pcnet: add loopback mode emulation
Date: Mon, 08 Sep 2008 08:18:48 +0200 [thread overview]
Message-ID: <48C4C3C8.5040005@web.de> (raw)
In-Reply-To: <48C46FD4.7020905@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
Anthony Liguori wrote:
> Jan Kiszka wrote:
>> This patch enhances the pcnet NIC emulation with better loopback mode
>> support, including CRC generation for looped-back packets in "raw" mode.
>> The patch has practically no impact on the normal RX and TX path.
>>
>> Successfully tested against an ancient proprietary pcnet driver that
>> does a lot of hardware checks on boot-up and now works fine over qemu as
>> well.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> hw/pcnet.c | 89
>> ++++++++++++++++++++++++++++++++++++++++---------------------
>> 1 file changed, 59 insertions(+), 30 deletions(-)
>>
>> Index: b/hw/pcnet.c
>> ===================================================================
>> --- a/hw/pcnet.c
>> +++ b/hw/pcnet.c
>> @@ -35,6 +35,8 @@
>> *
>> http://www.ibiblio.org/pub/historic-linux/early-ports/Sparc/NCR/NCR92C990.txt
>>
>> */
>>
>> +#include <netinet/in.h>
>>
>>
>
> That'll break the windows build. It's not immediately clear to me why
> you're including netinet/in.h. Is it for htonl? I think arpa/inet.h is
> where htonl is defined...
>
> At any rate, qemu_socket.h is probably what you want, but I'd like to
> know why you're adding it in the first place.
htonl, and it was fixed in SVN just as you suggested.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]
prev parent reply other threads:[~2008-09-08 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 11:42 [Qemu-devel] [PATCH] pcnet: add loopback mode emulation Jan Kiszka
2008-09-08 0:20 ` Anthony Liguori
2008-09-08 6:18 ` Jan Kiszka [this message]
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=48C4C3C8.5040005@web.de \
--to=jan.kiszka@web.de \
--cc=anthony@codemonkey.ws \
--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).