qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: deller@kernel.org
To: qemu-devel@nongnu.org
Cc: "Helge Deller" <deller@gmx.de>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"BALATON Zoltan" <balaton@eik.bme.hu>
Subject: [PULL 03/11] pci_ids/tulip: Add PCI vendor ID for HP and use it in tulip
Date: Wed, 18 Oct 2023 22:40:22 +0200	[thread overview]
Message-ID: <20231018204030.391572-4-deller@kernel.org> (raw)
In-Reply-To: <20231018204030.391572-1-deller@kernel.org>

From: Helge Deller <deller@gmx.de>

Signed-off-by: Helge Deller <deller@gmx.de>
---
 hw/net/tulip.c           | 2 +-
 include/hw/pci/pci_ids.h | 2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/hw/net/tulip.c b/hw/net/tulip.c
index 915e5fb595..11d866e431 100644
--- a/hw/net/tulip.c
+++ b/hw/net/tulip.c
@@ -1020,7 +1020,7 @@ static void tulip_class_init(ObjectClass *klass, void *data)
     k->exit = pci_tulip_exit;
     k->vendor_id = PCI_VENDOR_ID_DEC;
     k->device_id = PCI_DEVICE_ID_DEC_21143;
-    k->subsystem_vendor_id = 0x103c;
+    k->subsystem_vendor_id = PCI_VENDOR_ID_HP;
     k->subsystem_id = 0x104f;
     k->class_id = PCI_CLASS_NETWORK_ETHERNET;
     dc->vmsd = &vmstate_pci_tulip;
diff --git a/include/hw/pci/pci_ids.h b/include/hw/pci/pci_ids.h
index 85469b9b53..f1a53fea8d 100644
--- a/include/hw/pci/pci_ids.h
+++ b/include/hw/pci/pci_ids.h
@@ -179,6 +179,8 @@
 #define PCI_DEVICE_ID_AMD_LANCE          0x2000
 #define PCI_DEVICE_ID_AMD_SCSI           0x2020
 
+#define PCI_VENDOR_ID_HP                 0x103c
+
 #define PCI_VENDOR_ID_TI                 0x104c
 
 #define PCI_VENDOR_ID_MOTOROLA           0x1057
-- 
2.41.0



  parent reply	other threads:[~2023-10-18 20:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 20:40 [PULL 00/11] C3700 patches deller
2023-10-18 20:40 ` [PULL 01/11] target/hppa: Update to SeaBIOS-hppa version 10 deller
2023-10-18 20:40 ` [PULL 02/11] hw/hppa: Require at least " deller
2023-10-18 20:40 ` deller [this message]
2023-10-18 20:40 ` [PULL 04/11] lasips2: LASI PS/2 devices are not user-createable deller
2023-10-18 20:40 ` [PULL 05/11] hw/pci-host: Add Astro system bus adapter found on PA-RISC machines deller
2023-10-18 20:40 ` [PULL 06/11] pci-host: Wire up new Astro/Elroy PCI bridge deller
2023-10-18 20:40 ` [PULL 07/11] MAINTAINERS: Update HP-PARISC entries deller
2023-10-18 20:40 ` [PULL 08/11] hw/hppa: Export machine name, BTLBs, power-button address via fw_cfg deller
2023-10-18 20:40 ` [PULL 09/11] hw/hppa: Provide RTC and DebugOutputPort on CPU #0 deller
2023-10-18 20:40 ` [PULL 10/11] hw/hppa: Split out machine creation deller
2023-10-18 20:40 ` [PULL 11/11] hw/hppa: Add new HP C3700 machine deller
2023-10-19 17:19 ` [PULL 00/11] C3700 patches Stefan Hajnoczi
2023-10-19 23:07   ` Helge Deller
  -- strict thread matches above, loose matches on Subject: below --
2023-10-19 22:52 deller
2023-10-19 22:52 ` [PULL 03/11] pci_ids/tulip: Add PCI vendor ID for HP and use it in tulip deller

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=20231018204030.391572-4-deller@kernel.org \
    --to=deller@kernel.org \
    --cc=balaton@eik.bme.hu \
    --cc=deller@gmx.de \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).