From: Christopher Covington <cov@codeaurora.org>
To: Martin Townsend <martin.townsend@xsilon.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Request for help
Date: Wed, 01 Oct 2014 12:41:51 -0400 [thread overview]
Message-ID: <542C2ECF.5040400@codeaurora.org> (raw)
In-Reply-To: <542C06BA.50705@xsilon.com>
Hi Martin,
On 10/01/2014 09:50 AM, Martin Townsend wrote:
> Hi,
>
> I'm looking into creating a virtualised test bed for an 802.15.4 network.
> Currently I have QEMU running and emulating our HW which bridges the
> Ethernet from the guest to the host. What I would like to do is something
> similar with the 802.15.4 network interface. The host doesn't have a
> physical 802.15.4 interface but if I could get the data out of the guest
> and into QEMU I could communicate with a central network simulator to deal
> with the packets.
>
> My first thought was to write a virtual device for QEMU that would
> interface with our 802.15.4 driver in the guest but then I realise that the
> real device hangs of an AMBA bus
What exactly is your objection to this? Aren't there plenty of "AMBA bus"
peripherals that you can reference attached to the Versatile Express for example?
> so my next idea was to write a PCI driver for 802.15.4 on the guest making
> it possible to write a PCI virtual QEMU device.
>
> I just wanted to confirm that this is possible and whether there is a
> better solution?
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-10-01 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 13:50 [Qemu-devel] Request for help Martin Townsend
2014-10-01 16:41 ` Christopher Covington [this message]
2014-10-01 20:41 ` Martin Townsend
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=542C2ECF.5040400@codeaurora.org \
--to=cov@codeaurora.org \
--cc=martin.townsend@xsilon.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).