All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roberto Nibali <ratz@tac.ch>
To: Steve Hill <steve@navaho.co.uk>
Cc: linux-kernel@vger.kernel.org, becker@scyld.com,
	maurizio.quadrio@polimi.it, harry@navaho.co.uk
Subject: Re: Fix for Donald Becker's DP83815 network driver (v1.07)
Date: Tue, 17 Apr 2001 18:16:48 +0200	[thread overview]
Message-ID: <3ADC6C70.1590D9B7@tac.ch> (raw)
In-Reply-To: <Pine.LNX.4.21.0104171653110.4446-200000@sorbus.navaho>

Steve Hill wrote:
> 
> The attached patch fixes the following problems with the DP83815 driver
> (natsemi.c):
> 
> 1. When compiled into the kernel, the cards would be registered multiple
> times.

I assume this code fragment fixes this:

+       static int done = 0;

+
+       if (done) return -ENODEV;
        if (pci_drv_register(&natsemi_drv_id, dev) < 0)
                return -ENODEV;
+       done = 1;

My 2 questions are: 
Is this an acceptable fix for Donald? Because if so, I'd like to submit it
for the starfire quardboard driver.

--- starfire.c-old	Tue Apr 17 18:11:07 2001
+++ starfire.c	Tue Apr 17 18:12:37 2001
@@ -378,8 +378,12 @@
 #ifndef MODULE
 int starfire_probe(struct net_device *dev)
 {
+	static int done = 0;
+
+	if (done) return -ENODEV;
 	if (pci_drv_register(&starfire_drv_id, dev) < 0)
 		return -ENODEV;
+	done = 1;
 	printk(KERN_INFO "%s" KERN_INFO "%s", version1, version2);
 	return 0;
 }

Is there no implication with PCI latencies if multiple such cards
are loaded? I'm still having problems initializing more then 4
Quadboards.

Regards,
Roberto Nibali, ratz

-- 
mailto: `echo NrOatSz@tPacA.cMh | sed 's/[NOSPAM]//g'`

  reply	other threads:[~2001-04-17 16:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 15:58 Fix for Donald Becker's DP83815 network driver (v1.07) Steve Hill
2001-04-17 16:16 ` Roberto Nibali [this message]
2001-04-17 16:30   ` Steve Hill
2001-04-17 17:12     ` Roberto Nibali
2001-04-18 10:25     ` Ion Badulescu
2001-04-18 11:32       ` Steve Hill
2001-04-18 15:14         ` Tim Hockin
2001-04-18 20:33         ` Ion Badulescu
2001-04-18 20:40           ` Steve Hill
2001-04-19 10:54           ` Roberto Nibali
2001-04-19 13:06           ` Roberto Nibali
2001-04-20  5:48             ` Ion Badulescu
2001-04-20  6:30               ` Jeff Garzik
2001-04-20  7:09                 ` Ion Badulescu
2001-04-20  7:31                   ` Jeff Garzik
2001-04-20  9:49                     ` Ion Badulescu
2001-04-20  9:57                       ` Jeff Garzik
2001-04-20 10:05                         ` Ion Badulescu
2001-04-20 16:10                           ` Roberto Nibali
2001-04-20 16:19                             ` Jeff Garzik
2001-04-20 16:50                               ` Roberto Nibali
2001-04-20 19:27                                 ` Ion Badulescu
2001-04-20  9:03               ` Roberto Nibali
2001-04-20  9:42                 ` Ion Badulescu
2001-04-20 10:12                   ` Roberto Nibali

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=3ADC6C70.1590D9B7@tac.ch \
    --to=ratz@tac.ch \
    --cc=becker@scyld.com \
    --cc=harry@navaho.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maurizio.quadrio@polimi.it \
    --cc=steve@navaho.co.uk \
    /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.