From: Robert Hancock <hancock@sedsystems.ca>
To: netdev@vger.kernel.org
Cc: anirudh@xilinx.com, John.Linn@xilinx.com, andrew@lunn.ch,
Robert Hancock <hancock@sedsystems.ca>
Subject: [PATCH net-next v3 04/19] net: axienet: add X86 and ARM as supported platforms
Date: Tue, 4 Jun 2019 15:43:31 -0600 [thread overview]
Message-ID: <1559684626-24775-5-git-send-email-hancock@sedsystems.ca> (raw)
In-Reply-To: <1559684626-24775-1-git-send-email-hancock@sedsystems.ca>
This driver should now build on (at least) X86 and ARM platforms, so add
them as supported platforms for the driver in Kconfig.
Signed-off-by: Robert Hancock <hancock@sedsystems.ca>
---
drivers/net/ethernet/xilinx/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/xilinx/Kconfig b/drivers/net/ethernet/xilinx/Kconfig
index af96e05..5f50764 100644
--- a/drivers/net/ethernet/xilinx/Kconfig
+++ b/drivers/net/ethernet/xilinx/Kconfig
@@ -6,7 +6,7 @@
config NET_VENDOR_XILINX
bool "Xilinx devices"
default y
- depends on PPC || PPC32 || MICROBLAZE || ARCH_ZYNQ || MIPS || X86 || COMPILE_TEST
+ depends on PPC || PPC32 || MICROBLAZE || ARCH_ZYNQ || MIPS || X86 || ARM || COMPILE_TEST
---help---
If you have a network (Ethernet) card belonging to this class, say Y.
@@ -26,7 +26,7 @@ config XILINX_EMACLITE
config XILINX_AXI_EMAC
tristate "Xilinx 10/100/1000 AXI Ethernet support"
- depends on MICROBLAZE
+ depends on MICROBLAZE || X86 || ARM || COMPILE_TEST
select PHYLIB
---help---
This driver supports the 10/100/1000 Ethernet from Xilinx for the
--
1.8.3.1
next prev parent reply other threads:[~2019-06-04 21:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 21:43 [PATCH net-next v3 00/19] Xilinx axienet driver updates (v3) Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 01/19] net: axienet: Fix casting of pointers to u32 Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 02/19] net: axienet: Use standard IO accessors Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 03/19] net: axienet: fix MDIO bus naming Robert Hancock
2019-06-04 21:43 ` Robert Hancock [this message]
2019-06-04 21:43 ` [PATCH net-next v3 05/19] net: axienet: Use clock framework to get device clock rate Robert Hancock
2019-06-04 22:12 ` Andrew Lunn
2019-06-04 21:43 ` [PATCH net-next v3 06/19] net: axienet: fix teardown order of MDIO bus Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 07/19] net: axienet: Re-initialize MDIO registers properly after reset Robert Hancock
2019-06-04 22:18 ` Andrew Lunn
2019-06-04 22:39 ` Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 08/19] net: axienet: Cleanup DMA device reset and halt process Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 09/19] net: axienet: Make RX/TX ring sizes configurable Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 10/19] net: axienet: Add DMA registers to ethtool register dump Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 11/19] net: axienet: Support shared interrupts Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 12/19] net: axienet: Add optional support for Ethernet core interrupt Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 13/19] net: axienet: Fix race condition causing TX hang Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 14/19] net: axienet: Make missing MAC address non-fatal Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 15/19] net: axienet: stop interface during shutdown Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 16/19] net: axienet: Fix MDIO bus parent node detection Robert Hancock
2019-06-04 22:03 ` Andrew Lunn
2019-06-04 21:43 ` [PATCH net-next v3 17/19] net: axienet: document axistream-connected attribute Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 18/19] net: axienet: make use of axistream-connected attribute optional Robert Hancock
2019-06-04 21:43 ` [PATCH net-next v3 19/19] net: axienet: convert to phylink API Robert Hancock
2019-06-04 21:58 ` [PATCH net-next v3 00/19] Xilinx axienet driver updates (v3) Andrew Lunn
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=1559684626-24775-5-git-send-email-hancock@sedsystems.ca \
--to=hancock@sedsystems.ca \
--cc=John.Linn@xilinx.com \
--cc=andrew@lunn.ch \
--cc=anirudh@xilinx.com \
--cc=netdev@vger.kernel.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).