From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-trivial@nongnu.org,
"Alistair Francis" <alistair@alistair23.me>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Laurent Vivier" <laurent@vivier.eu>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Niek Linnenbank" <nieklinnenbank@gmail.com>,
qemu-arm@nongnu.org, "Antony Pavlov" <antonynpavlov@gmail.com>,
"Joel Stanley" <joel@jms.id.au>
Subject: [PATCH v3 5/6] hw/net/can: ZynqMP CAN device requires PTIMER
Date: Sun, 31 Jan 2021 19:44:48 +0100 [thread overview]
Message-ID: <20210131184449.382425-6-f4bug@amsat.org> (raw)
In-Reply-To: <20210131184449.382425-1-f4bug@amsat.org>
Add a dependency XLNX_ZYNQMP -> PTIMER to fix:
/usr/bin/ld:
libcommon.fa.p/hw_net_can_xlnx-zynqmp-can.c.o: in function `xlnx_zynqmp_can_realize':
hw/net/can/xlnx-zynqmp-can.c:1082: undefined reference to `ptimer_init'
hw/net/can/xlnx-zynqmp-can.c:1085: undefined reference to `ptimer_transaction_begin'
hw/net/can/xlnx-zynqmp-can.c:1087: undefined reference to `ptimer_set_freq'
hw/net/can/xlnx-zynqmp-can.c:1088: undefined reference to `ptimer_set_limit'
hw/net/can/xlnx-zynqmp-can.c:1089: undefined reference to `ptimer_run'
hw/net/can/xlnx-zynqmp-can.c:1090: undefined reference to `ptimer_transaction_commit'
libcommon.fa.p/hw_net_can_xlnx-zynqmp-can.c.o:(.data.rel+0x2c8): undefined reference to `vmstate_ptimer'
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
hw/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/Kconfig b/hw/Kconfig
index 5ad3c6b5a4b..d4cec9e476c 100644
--- a/hw/Kconfig
+++ b/hw/Kconfig
@@ -81,3 +81,4 @@ config XLNX_ZYNQMP
bool
select REGISTER
select CAN_BUS
+ select PTIMER
--
2.26.2
next prev parent reply other threads:[~2021-01-31 18:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 18:44 [PATCH v3 0/6] hw/arm: Misc trivial fixes/cleanups Philippe Mathieu-Daudé
2021-01-31 18:44 ` [PATCH v3 1/6] hw/arm/stm32f405_soc: Add missing dependency on OR_IRQ Philippe Mathieu-Daudé
2021-02-01 19:54 ` Alistair Francis
2021-01-31 18:44 ` [PATCH v3 2/6] hw/arm/exynos4210: " Philippe Mathieu-Daudé
2021-01-31 18:44 ` [PATCH v3 3/6] hw/arm/xlnx-versal: Versal SoC requires ZDMA Philippe Mathieu-Daudé
2021-02-01 19:55 ` Alistair Francis
2021-01-31 18:44 ` [PATCH v3 4/6] hw/arm/xlnx-versal: Versal SoC requires ZynqMP peripherals Philippe Mathieu-Daudé
2021-02-01 19:56 ` Alistair Francis
2021-01-31 18:44 ` Philippe Mathieu-Daudé [this message]
2021-02-01 19:55 ` [PATCH v3 5/6] hw/net/can: ZynqMP CAN device requires PTIMER Alistair Francis
2021-01-31 18:44 ` [PATCH v3 6/6] hw/arm: Display CPU type in machine description Philippe Mathieu-Daudé
2021-01-31 21:53 ` Niek Linnenbank
2021-02-01 19:56 ` Alistair Francis
2021-02-02 16:48 ` [PATCH v3 0/6] hw/arm: Misc trivial fixes/cleanups 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=20210131184449.382425-6-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=alistair@alistair23.me \
--cc=antonynpavlov@gmail.com \
--cc=joel@jms.id.au \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=nieklinnenbank@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).