From: Paolo Bonzini <pbonzini@redhat.com>
To: Nehal J Wani <nehaljw.kkd1@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Query: Support for various hardware types
Date: Tue, 24 Sep 2013 12:52:57 +0200 [thread overview]
Message-ID: <52416F09.8030108@redhat.com> (raw)
In-Reply-To: <CAG6NSrm5_EOVkjwTXuNGxWShY5CtwogJV33FgiuCHDnugZVyhA@mail.gmail.com>
Il 24/09/2013 10:04, Nehal J Wani ha scritto:
> Hello!
> I am currently developing an API for libvirt to print out the
> leases info for a given network. Since dnsmasq supports hardware types
> other than ethernet, I want to know whether there are any on going
> developments or plans for introducing other hardware types (example:
> IEEE1394 clients use hardware type 24), so that I can make the API as
> extensible as possible.
No, not in QEMU.
Paolo
prev parent reply other threads:[~2013-09-24 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 8:04 [Qemu-devel] Query: Support for various hardware types Nehal J Wani
2013-09-24 10:52 ` Paolo Bonzini [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=52416F09.8030108@redhat.com \
--to=pbonzini@redhat.com \
--cc=nehaljw.kkd1@gmail.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).