All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hanno Böck" <hanno@gmx.de>
To: David Weinehall <tao@acc.umu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patch for eepro100 to support more cards
Date: Wed, 6 Feb 2002 15:45:40 +0100	[thread overview]
Message-ID: <20020206144449Z290588-13996+17952@vger.kernel.org> (raw)
In-Reply-To: <20020201080545Z291604-13996+15441@vger.kernel.org> <20020206132727.H1735@khan.acc.umu.se>
In-Reply-To: <20020206132727.H1735@khan.acc.umu.se>

Because of some complains and as pre8 is out now, I made it again for the 2.4.18pre8-kernel.
I hope it is okay now.

I put up a site for the patch: http://www.int21.de/eepro100/

The Patch adds definitions for the Intel Pro/100 VE-card to the eepro100-driver.

--- linux-2.4.18-pre8/drivers/net/eepro100.c	Wed Feb  6 15:15:16 2002
+++ linux/drivers/net/eepro100.c	Wed Feb  6 15:19:14 2002
@@ -168,6 +168,9 @@
 #ifndef PCI_DEVICE_ID_INTEL_ID1030
 #define PCI_DEVICE_ID_INTEL_ID1030 0x1030
 #endif
+#ifndef PCI_DEVICE_ID_INTEL_ID1031          /* support for Intel Pro/100 VE */
+#define PCI_DEVICE_ID_INTEL_ID1031 0x1031
+#endif


 static int speedo_debug = 1;
@@ -2270,6 +2273,8 @@
 	{ PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ID1029,
 		PCI_ANY_ID, PCI_ANY_ID, },
 	{ PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ID1030,
+		PCI_ANY_ID, PCI_ANY_ID, },
+	{ PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ID1031,     /* support for Intel Pro/100 VE */
 		PCI_ANY_ID, PCI_ANY_ID, },
 	{ PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801BA_7,
 		PCI_ANY_ID, PCI_ANY_ID, },

  reply	other threads:[~2002-02-06 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  8:06 Patch for eepro100 to support more cards Hanno Böck
2002-02-06 12:27 ` David Weinehall
2002-02-06 14:45   ` Hanno Böck [this message]
2002-02-07 17:45     ` Josh Grebe

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=20020206144449Z290588-13996+17952@vger.kernel.org \
    --to=hanno@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tao@acc.umu.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.