[lkml]   [2000]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: weird PCI problems...
Hi Tigran!

Sorry for the delay, I'm now finishing up for my final exams, so I get to
answering my mail once per day if I'm lucky.

> Yes, doing it like this works:
> --- linux/drivers/pci/pci.c Mon Sep 18 12:35:11 2000
> +++ work/drivers/pci/pci.c Mon Sep 18 13:12:20 2000
> @@ -714,7 +714,7 @@
> * We need to blast all three values with a single write.
> */
> pci_write_config_dword(dev, PCI_PRIMARY_BUS, buses);
> - if (!is_cardbus) {
> + if (is_cardbus) {
> /* Now we can scan all subordinate buses... */
> max = pci_do_scan_bus(child);
> } else {

> Martin, is this totally wrong? I.e. will it break the case of multiple
> peer PCI buses? Note that with the above I see absolutely all my devices,
> like this:

This fix is wrong -- the scanning of cardbus devices is done inside the cardbus
driver itself, the PCI layer should only allocate the bus. If you force the
scanning, it will work for devices present during system boot, but not if you
remove the card and insert it again.

Anyway, can you send me your /proc/ioports and /proc/iomem, please?

Have a nice fortnight
Martin `MJ' Mares <> <>
"People disagree with me. I just ignore them." -- Linus Torvalds
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.069 / U:3.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site