From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Emilio G . Cota" <cota@braap.org>,
"Sven Schnelle" <svens@stackframe.org>,
"Richard Henderson" <rth@twiddle.net>
Subject: [PATCH-for-5.0] hw/alpha/dp264: Use the DECchip Tulip network interface
Date: Thu, 5 Dec 2019 00:39:18 +0100 [thread overview]
Message-ID: <20191204233918.6073-1-philmd@redhat.com> (raw)
Commit 34ea023d4b9 introduced the Tulip PCI NIC.
Since this better models the DP264 hardware, use it.
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
---
hw/alpha/dp264.c | 4 ++--
hw/alpha/Kconfig | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/alpha/dp264.c b/hw/alpha/dp264.c
index 51b3cf7a61..4424551ba1 100644
--- a/hw/alpha/dp264.c
+++ b/hw/alpha/dp264.c
@@ -85,9 +85,9 @@ static void clipper_init(MachineState *machine)
/* VGA setup. Don't bother loading the bios. */
pci_vga_init(pci_bus);
- /* Network setup. e1000 is good enough, failing Tulip support. */
+ /* Network setup */
for (i = 0; i < nb_nics; i++) {
- pci_nic_init_nofail(&nd_table[i], pci_bus, "e1000", NULL);
+ pci_nic_init_nofail(&nd_table[i], pci_bus, "tulip", NULL);
}
/* 2 82C37 (dma) */
diff --git a/hw/alpha/Kconfig b/hw/alpha/Kconfig
index 15c59ff264..552e6a4c23 100644
--- a/hw/alpha/Kconfig
+++ b/hw/alpha/Kconfig
@@ -2,7 +2,7 @@ config DP264
bool
imply PCI_DEVICES
imply TEST_DEVICES
- imply E1000_PCI
+ imply TULIP
select I82374
select I8254
select I8259
--
2.21.0
next reply other threads:[~2019-12-04 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 23:39 Philippe Mathieu-Daudé [this message]
2019-12-05 20:38 ` [PATCH-for-5.0] hw/alpha/dp264: Use the DECchip Tulip network interface Richard Henderson
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=20191204233918.6073-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=cota@braap.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=svens@stackframe.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).