On Thu, Jun 23, 2005 at 08:09:35PM +0200, Brice Goglin wrote:
> dmesg and dsdt are attached.
>
The host bridge resources being reported were fine. I think this
failure is a yenta bug exposed by the combination of the host
bridge resource collection patch and the patch to improve the
handling for transparent bridges. I think the yenta code thinks
there's a resource conflict for the ranges being decoded by the
cardbus bridge when in fact there isn't any conflict in this case.
It then claims and reprograms the cardbus bridge to IO resources
that are already programmed into another device (winmodem in this
case), causing problems.
Does the following patch to 2.6.12-mm1 fix the problem?
------------------------------
Index: linux-2.6.12-mm1/drivers/pcmcia/yenta_socket.c
===================================================================
--- linux-2.6.12-mm1.orig/drivers/pcmcia/yenta_socket.c
+++ linux-2.6.12-mm1/drivers/pcmcia/yenta_socket.c
@@ -562,9 +562,6 @@ static int yenta_try_allocate_res(struct
bus = socket->dev->subordinate;
res = socket->dev->resource + PCI_BRIDGE_RESOURCES + nr;
res->name = bus->name;
- res->flags = type;
- res->start = 0;
- res->end = run;
root = pci_find_parent_resource(socket->dev, res);
if (!root)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
