From: Yaacov Akiba Slama <ya@slamail.org>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Re : [BUG] cardbus/hotplugging still broken in 2.5.56
Date: Tue, 14 Jan 2003 20:39:22 +0200 [thread overview]
Message-ID: <3E24595A.7040801@slamail.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
Hello all !
I have a xircom (RBEM56G-100) lan+modem, and it seems that the following
patch solves the problem of ressources collisions.
Now, I can use 2.5.58mm1 in my laptop and I am happy.
Yaacov Akiba Slama
[-- Attachment #2: cardbus.patch --]
[-- Type: text/plain, Size: 708 bytes --]
--- a/drivers/pcmcia/cardbus.c 2003-01-14 19:38:49.000000000 +0200
+++ b/drivers/pcmcia/cardbus.c 2003-01-14 19:57:13.000000000 +0200
@@ -285,18 +285,19 @@
dev->dev.dma_mask = &dev->dma_mask;
pci_setup_device(dev);
- if (pci_enable_device(dev))
- continue;
strcpy(dev->dev.bus_id, dev->slot_name);
/* FIXME: Do we need to enable the expansion ROM? */
for (r = 0; r < 7; r++) {
struct resource *res = dev->resource + r;
- if (res->flags)
+ if (!res->start && res->end)
pci_assign_resource(dev, r);
}
+ if (pci_enable_device(dev))
+ continue;
+
/* Does this function have an interrupt at all? */
pci_readb(dev, PCI_INTERRUPT_PIN, &irq_pin);
if (irq_pin) {
next reply other threads:[~2003-01-14 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 18:39 Yaacov Akiba Slama [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 8:11 [BUG] cardbus/hotplugging still broken in 2.5.56 Jens Taprogge
2003-01-15 9:13 ` Mikael Pettersson
2003-01-15 16:26 ` [PATCH] " Yaacov Akiba Slama
2003-01-15 19:47 ` Jens Taprogge
2003-01-15 20:23 ` Dave Jones
2003-01-15 20:13 Yaacov Akiba Slama
2003-01-15 20:31 ` jens.taprogge
2003-01-15 20:55 ` Yaacov Akiba Slama
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=3E24595A.7040801@slamail.org \
--to=ya@slamail.org \
--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