From: Mikael Pettersson <mikpe@csd.uu.se>
To: Jens Taprogge <taprogge@idg.rwth-aachen.de>
Cc: zwane@holomorphy.com, bvermeul@blackstar.nl, ya@slamail.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] cardbus/hotplugging still broken in 2.5.56
Date: Wed, 15 Jan 2003 10:13:40 +0100 [thread overview]
Message-ID: <15909.9796.157927.447889@harpo.it.uu.se> (raw)
In-Reply-To: <20030115081109.GA3839@valsheda.taprogge.wh>
Jens Taprogge writes:
> The cardbus problems are caused by
>
> ChangeSet@1.797.145.6 2002-11-25 18:31:10-08:00 davej@codemonkey.org.uk
>
> as far as I can tell.
>
> pci_enable_device() will fail at least on i386 (see
> arch/i386/pci/i386.c: pcibios_enable_resource (line 260)) if the
> resources have not been assigned previously. Hence the ostensible
> resource collisions.
>
> The attached patch should fix the problem.
>
> I have send the patch to Dave Jones some time ago but did not hear from
> him yet.
>
> I am not subscribed to the list so please cc me on replys.
Thanks. Your patch fixed the cardbus hotplug issue perfectly on my laptop.
It survives multiple insert/eject cycles without any problems.
The patch posted by Yaacov Akiba Slama today also fixed cardbus hotplug
for me, but with his patch the kernel still prints "PCI: No IRQ known for
interrupt pin A of device xx:xx.x. Please try using pci=biosirq" when the
cardbus NIC is inserted; Jens Taprogge's patch silenced that warning.
/Mikael
next prev parent reply other threads:[~2003-01-15 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 8:11 Jens Taprogge
2003-01-15 9:13 ` Mikael Pettersson [this message]
2003-01-15 16:26 ` [PATCH] " Yaacov Akiba Slama
2003-01-15 19:47 ` Jens Taprogge
2003-01-15 20:23 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2003-01-11 16:05 Mikael Pettersson
2003-01-11 16:47 ` John Bradford
2003-01-11 22:01 ` Zwane Mwaikambo
2003-01-13 8:43 ` Bas Vermeulen
2003-01-14 12:34 ` Mikael Pettersson
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=15909.9796.157927.447889@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=bvermeul@blackstar.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=taprogge@idg.rwth-aachen.de \
--cc=ya@slamail.org \
--cc=zwane@holomorphy.com \
/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®