[lkml]   [2002]   [May]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectcardbus/pcmcia/pci bridge problems?
I recently wrote the ALSA driver for the RME Hammerfall DSP, a
high-end audio interface. The H-DSP comes in a variety of
configurations, one of them involving a "pure" PCI interface, the
other a PCMCIA card. The PCI interface works fine. Users with the
PCMCIA card report major problems, the most representative of which

Case One (failure to make iomem available):
>May 16 09:54:57 satellite kernel: cs: cb_alloc(bus 3): vendor 0x10ee, device
>May 16 09:54:57 satellite kernel: PCI: Failed to allocate resource
>0(d2400000-d20fffff) for 03:00.0
>May 16 09:54:57 satellite kernel: PCI: Enabling device 03:00.0 (0080 -> 0082)
>May 16 09:54:57 satellite cardmgr[258]: socket 0: CardBus hotplug device

Case Two (failure to allocate IRQ):
>May 16 15:15:32 badass-bukvic kernel: PCI: Found IRQ 5 for device
>May 16 15:15:33 badass-bukvic kernel: Hammerfall memory allocator:
>buffers allocated for 1 cards
>May 16 15:15:33 badass-bukvic kernel: PCI: No IRQ known for interrupt
>pin A of device . Please try using pci=biosirq.
>May 16 15:15:33 badass-bukvic kernel: PCI: Setting latency timer of
>device to 64
>May 16 15:15:33 badass-bukvic kernel: ALSA
>../../alsa-kernel/pci/rme9652/hdsp.c:2984: unable to grab memory region

In both cases, the error comes from cardbus/pcmcia/pci code that runs
"below" and/or before the device driver itself.

The PCI profile of the device looks like:

03:00.0 Multimedia audio controller: Xilinx, Inc.: Unknown device 3fc5 (rev
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping+ SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
Region 0: [virtual] Memory at d2400000 (32-bit, non-prefetchable)

It appears to me that there may be some problems with the current
cardbus/pci bridge code in 2.4.X. can anyone with any involvement in
this code fill me in on how well it is thought to be working, and what
might give rise to either of the error cases shown above?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

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