From: Vikram Garhwal <fnu.vikram@xilinx.com>
To: qemu-devel@nongnu.org
Cc: jasowang@redhat.com
Subject: [PATCH 0/1] Introduce Xlnx ZynqMP CAN controller for QEMU
Date: Mon, 3 Feb 2020 13:06:49 -0800 [thread overview]
Message-ID: <1580764010-310744-1-git-send-email-fnu.vikram@xilinx.com> (raw)
Example for single CAN:
-object can-bus,id=canbus0 \
-global driver=xlnx.zynqmp-can,property=canbus0,value=canbus0 \
-object can-host-socketcan,id=socketcan0,if=vcan0,canbus=canbus0
Example for connecting both CAN:
-object can-bus,id=canbus0 -object can-bus,id=canbus1 \
-global driver=xlnx.zynqmp-can,property=canbus0,value=canbus0 \
-global driver=xlnx.zynqmp-can,property=canbus1,value=canbus1 \
-object can-host-socketcan,id=socketcan0,if=vcan0,canbus=canbus0 \
-object can-host-socketcan,id=socketcan1,if=vcan0,canbus=canbus1
Vikram Garhwal (1):
hw/net/can: Introduce Xlnx ZynqMP CAN controller for QEMU
hw/net/can/Makefile.objs | 1 +
hw/net/can/xlnx-zynqmp-can.c | 1106 ++++++++++++++++++++++++++++++++++++++
include/hw/net/xlnx-zynqmp-can.h | 77 +++
3 files changed, 1184 insertions(+)
create mode 100644 hw/net/can/xlnx-zynqmp-can.c
create mode 100644 include/hw/net/xlnx-zynqmp-can.h
--
2.7.4
next reply other threads:[~2020-02-03 21:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 21:06 Vikram Garhwal [this message]
2020-02-03 21:06 ` [PATCH 1/1] hw/net/can: Introduce Xlnx ZynqMP CAN controller for QEMU Vikram Garhwal
2020-02-05 5:46 ` Jason Wang
2020-02-06 18:39 ` Vikram Garhwal
2020-02-10 21:45 ` Vikram Garhwal
2020-02-11 3:09 ` Jason Wang
2020-02-25 6:22 ` Vikram Garhwal
2020-02-26 3:24 ` Jason Wang
2020-02-27 16:04 ` Vikram Garhwal
2020-02-05 3:17 ` [PATCH 0/1] " Jason Wang
2020-02-05 3:23 ` Vikram Garhwal
2020-02-05 5:48 ` Jason Wang
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=1580764010-310744-1-git-send-email-fnu.vikram@xilinx.com \
--to=fnu.vikram@xilinx.com \
--cc=jasowang@redhat.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).