qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alexander Graf <agraf@suse.de>, Fabien Chouteau <chouteau@adacore.com>
Cc: Scott Wood <scottwood@freescale.com>,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	"qemu-ppc@nongnu.org list:PowerPC" <qemu-ppc@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH V2] Add Enhanced Three-Speed Ethernet Controller (eTSEC)
Date: Tue, 10 Dec 2013 22:59:15 +1100	[thread overview]
Message-ID: <52A70213.50806@ozlabs.ru> (raw)
In-Reply-To: <A6F6CA19-B347-4E94-AA34-8C102BAB5B78@suse.de>

On 12/10/2013 02:15 AM, Alexander Graf wrote:
> 
> On 22.07.2013, at 18:00, Fabien Chouteau <chouteau@adacore.com> wrote:
> 
>> This implementation doesn't include ring priority, TCP/IP Off-Load, QoS.
>>
>> Signed-off-by: Fabien Chouteau <chouteau@adacore.com>
> 
> Thanks, applied to ppc-next. Could you please follow up with a patch that makes this available as -net nic,model=etsec and generate a respective device tree node for it?

This does not compile:

  CC    ppc-softmmu/hw/net/fsl_etsec/rings.o
In file included from /home/alexey/p/qemu/hw/net/fsl_etsec/rings.c:24:0:
/home/alexey/p/qemu/include/net/checksum.h:51:31: error: ‘struct iovec’
declared inside parameter list [-Werror]
/home/alexey/p/qemu/include/net/checksum.h:51:31: error: its scope is only
this definition or declaration, which is probably not what you want [-Werror]
/home/alexey/p/qemu/hw/net/fsl_etsec/rings.c: In function ‘fill_rx_bd’:
/home/alexey/p/qemu/hw/net/fsl_etsec/rings.c:396:5: error: format ‘%llx’
expects argument of type ‘long long unsigned int’, but argument 2 has type
‘hwaddr’ [-Werror=format]
/home/alexey/p/qemu/hw/net/fsl_etsec/rings.c:396:5: error: format ‘%u’
expects argument of type ‘unsigned int’, but argument 3 has type ‘size_t’
[-Werror=format]
/home/alexey/p/qemu/hw/net/fsl_etsec/rings.c: In function ‘etsec_walk_rx_ring’:
/home/alexey/p/qemu/hw/net/fsl_etsec/rings.c:583:28: error: format ‘%d’
expects argument of type ‘int’, but argument 3 has type ‘size_t’
[-Werror=format]
/home/alexey/p/qemu/hw/net/fsl_etsec/rings.c:649:5: error: format ‘%u’
expects argument of type ‘unsigned int’, but argument 2 has type ‘size_t’
[-Werror=format]
cc1: all warnings being treated as errors
make[1]: *** [hw/net/fsl_etsec/rings.o] Error 1
make[1]: *** Waiting for unfinished jobs....
/home/alexey/p/qemu/hw/net/fsl_etsec/etsec.c: In function ‘etsec_realize’:
/home/alexey/p/qemu/hw/net/fsl_etsec/etsec.c:389:53: error: ‘SysBusDevice’
has no member named ‘qdev’
make[1]: *** [hw/net/fsl_etsec/etsec.o] Error 1
make: *** [subdir-ppc-softmmu] Error 2



-- 
Alexey

  reply	other threads:[~2013-12-10 11:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 16:00 [Qemu-devel] [PATCH V2] Add Enhanced Three-Speed Ethernet Controller (eTSEC) Fabien Chouteau
2013-12-09 15:15 ` Alexander Graf
2013-12-10 11:59   ` Alexey Kardashevskiy [this message]
2013-12-10 12:48     ` Alexander Graf
2013-12-10 17:15       ` Fabien Chouteau
2013-12-10 17:20         ` Alexander Graf
2014-02-05 13:43           ` Fabien Chouteau

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=52A70213.50806@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=agraf@suse.de \
    --cc=chouteau@adacore.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=scottwood@freescale.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 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).