From: Gianluca Anzolin <g.anzolin@inwind.it>
To: linux-kernel@vger.kernel.org
Cc: g.anzolin@inwind.it
Subject: [PATCH] remove a wrong release_region in eexpress.c
Date: Mon, 28 Jan 2002 14:06:19 +0100 [thread overview]
Message-ID: <20020128130619.GA652@fourier.home.intranet> (raw)
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
Hello,
I was trying the eexpress.c driver for my Intel EtherExpress 16 NIC
(isa) and I got some errors when I unloaded the module (kernel
2.4.18-pre7).
The problem was that it was trying to release an already released i/o
region. I'm attaching a patch to remove that release_region.
I have also a question: I'm reading Rubini's Linux Device Drivers (2nd
edition) and he writes that irq and regions should be registered when
the device is open (and not in the hw-probe function). Why network
drivers should register the resources they use only on open and not on
probe (like other drivers do) ?
I don't know if this is related but I had a problem few months ago when
the ISDN card (a pci one) tried to share the same IRQ of the Network
Card (isa). The result was the nic didn't work (the NIC was a 3c509b
ISA PNP card) and I had to explicitly change the nic irq via a kernel parameter
on boot. Now I wonder if this could have happened if the driver had
registered its irq on probe and not on open (i.e. after that the hisax
module was loaded).
Greeting,
Gianluca Anzolin
[-- Attachment #2: eexpress.patch --]
[-- Type: text/plain, Size: 242 bytes --]
--- eexpress.c.old Mon Jan 28 13:47:44 2002
+++ eexpress.c Mon Jan 28 13:48:19 2002
@@ -1674,7 +1674,6 @@
unregister_netdev(dev);
kfree(dev->priv);
dev->priv = NULL;
- release_region(dev->base_addr, EEXP_IO_EXTENT);
}
}
}
next reply other threads:[~2002-01-28 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 13:06 Gianluca Anzolin [this message]
2002-01-28 13:33 ` Alan Cox
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=20020128130619.GA652@fourier.home.intranet \
--to=g.anzolin@inwind.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®