All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Muizelaar <muizelaar@rogers.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Convert NE driver from Jeff Muizelaar (10/13)
Date: Mon, 17 Feb 2003 23:29:26 -0500	[thread overview]
Message-ID: <3E51B6A6.5000603@rogers.com> (raw)
In-Reply-To: <3E517226.4070405@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 382 bytes --]

Jeff Garzik wrote:

> Looks ok at quick glance.  I'll give it another look and a test 
> compile, and then [most likely] merge it...

Here is another patch that can go on top of the last one. All it does is 
add new PnP ids.
I am not certain about the first three but they look sane enough.
The last one is a card I have and is what I did my testing on so I know 
it works.

-Jeff


[-- Attachment #2: ne-patch.3b --]
[-- Type: text/plain, Size: 673 bytes --]

--- linux-2.5.59/drivers/net/ne.c	2003-01-26 14:25:28.000000000 -0500
+++ linux-2.5.59-patched/drivers/net/ne.c	2003-01-26 14:25:02.000000000 -0500
@@ -81,8 +81,16 @@
 	{.id = "AXE2011", .driver_data = 0},
 	/* NN NE2000 */
 	{.id = "EDI0216", .driver_data = 0},
+	/* Novell/Anthem NE1000 */
+	{.id = "PNP80d3", .driver_data = 0},
+	/* Novell/Anthem NE2000 */
+	{.id = "PNP80d4", .driver_data = 0},
+	/* NE1000 Compatible */
+	{.id = "PNP80d5", .driver_data = 0},
 	/* NE2000 Compatible */
 	{.id = "PNP80d6", .driver_data = 0},
+	/* National Semiconductor AT/LANTIC EtherNODE 16-AT3 */
+	{.id = "PNP8160", .driver_data = 0},
 };
 
 MODULE_DEVICE_TABLE(pnp, ne_pnp_table);

      reply	other threads:[~2003-02-18  4:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-17 18:24 [PATCH] Convert NE driver from Jeff Muizelaar (10/13) Adam Belay
2003-02-17 23:37 ` Jeff Garzik
2003-02-18  4:29   ` Jeff Muizelaar [this message]

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=3E51B6A6.5000603@rogers.com \
    --to=muizelaar@rogers.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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 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.