Compaq WL200 and pd6729

AM Drew aaron at cs.anu.edu.au
Wed Mar 23 21:55:32 EST 2005


On Thu, 24 Mar 2005 10:46 am, David Hinds wrote:
> On Thu, Mar 24, 2005 at 10:32:43AM +1100, AM Drew wrote:
> > 0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge
> > (rev a3) (prog-if 00 [Normal decode])
> >         Flags: bus master, 66Mhz, fast devsel, latency 0
> >         Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
> >         I/O behind bridge: 00009000-0000afff
> >         Memory behind bridge: d8000000-d9ffffff
> >         Prefetchable memory behind bridge: d4000000-d4ffffff
>
> Your PD6729 bridge is sitting behind this PCI bridge.  In your
> config.opts file, you should remove the default IO and memory windows
> and instead use:
>
>   include memory 0xd8000000-0xd9ffffff
>   include port 0x9000-0xafff

First, thanks for all your help Jar and David but this didn't work either. 

With these options in the file, loading pd6729 manually (modprobe pd6729) 
without anything else leaves the system as follows:

- two pccardd processes running that can't be killed
- pd6729 module can't be unloaded with rmmod (as its in use by the 2 processes 
I assume)
- The following dmesg output:

Linux Kernel Card Services
  options:  [pci] [cardbus] [pm]
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 12
PCI: setting IRQ 12 as level-triggered
ACPI: PCI interrupt 0000:01:0a.0[A] -> GSI 12 (level, low) -> IRQ 12
pd6729: Cirrus PD6729 PCI to PCMCIA Bridge at 0x9400 on irq 12
pd6729: configured as a 2 socket device.

I can't see any module options for configuring the pd6729 driver. Nor am I 
familiar enough with the kernel source to pinpoint where it might be getting 
stuck but I assume it must be either in pd6729 or pcmcia_core.

Its definately something more than the cardmgr memory ranges though..

- Aaron



More information about the linux-pcmcia mailing list