qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ashok Kumar <ashoks@broadcom.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] hw/arm/virt: Initialize NICs configured in PCI bus
Date: Wed, 6 Jan 2016 21:53:49 -0800	[thread overview]
Message-ID: <20160107055348.GF28462@ashoks@broadcom.com> (raw)
In-Reply-To: <CAFEAcA8OxXkpUWFXbg-s-B8U1+agDUB0B7XADRTYk95AttGoFg@mail.gmail.com>

On Wed, Jan 06, 2016 at 06:10:15PM +0000, Peter Maydell wrote:
Hi,

> On 6 January 2016 at 14:47, Ashok Kumar <ashoks@broadcom.com> wrote:
> > virtio model is used for default case.
> >
> > Signed-off-by: Ashok Kumar <ashoks@broadcom.com>
> 
> Could you explain why you think this needs to be done?
Yes, for -net. Honestly, I didn't know this is obsolete and the
only syntax I knew for networking. 

> Virtio networking works OK for me...
I tried the new syntax now and it is working fine.

> 
> I guess from the patch that this is adding support for
> the legacy '-net' way of configuring networking, but do
> we need that if we never supported it in the first place?
> (If virt is the only PCI machine which doesn't support
> -net syntax that would probably be a strong argument for
> supporting it.)
Fine with me. But there are some documentation for e.g [1] which says "-net" is
still supported.

[1] http://www.linux-kvm.org/page/Networking#Compatibility

Thanks,
Ashok
> 
> thanks
> -- PMM
> 

  reply	other threads:[~2016-01-07  5:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 14:47 [Qemu-devel] [PATCH] hw/arm/virt: Initialize NICs configured in PCI bus Ashok Kumar
2016-01-06 18:10 ` Peter Maydell
2016-01-07  5:53   ` Ashok Kumar [this message]
     [not found]   ` <568dfd6e.2966420a.4f765.fffff89dSMTPIN_ADDED_BROKEN@mx.google.com>
2016-01-07 14:47     ` Peter Maydell
2016-01-07 15:21       ` Paolo Bonzini
2016-01-11  2:54         ` Jason Wang
2016-01-11 13:24           ` Peter Maydell

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=20160107055348.GF28462@ashoks@broadcom.com \
    --to=ashoks@broadcom.com \
    --cc=peter.maydell@linaro.org \
    --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).