I've Debian PPC/unstable, kernel 2.4.16-ben with devfs running on my
Ti PowerBook G4 and like to read CF cards in my PCMCIA slot.
The modules I've loaded are:
i82092 7748 0 (unused)
ide-cs 3584 0 (unused)
ds 8720 0 [ide-cs]
yenta_socket 11088 1
pcmcia_core 42544 0 [i82092 ide-cs ds yenta_socket]
But I always get this messages while restarting pcmcia or (re)inserting
the card:
Yenta IRQ list 0000, PCI irq58
Socket status: 30000006
cs: memory probe 0x90000000-0x90ffffff: excluding 0x90000000-0x90ffffff
cs: unable to map card memory!
...
My bus looks like (from lspci -v):
01:1a.0 CardBus bridge: Texas Instruments PCI1211
Flags: bus master, medium devsel, latency 168, IRQ 58
Memory at a0000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=01, secondary=02, subordinate=05, sec-latency=176
Memory window 0: 90000000-9ffff000 (prefetchable)
Memory window 1: f3000000-f33ff000
I/O window 0: 00001000-00008fff
I/O window 1: 00009000-000090ff
16-bit legacy interface ports at 0001
----
/etc/pcmcia/config.opts : (I tried all the outcommented versions too)
# Local PCMCIA Configuration File
# System resources available for PCMCIA devices
# include port 0x100-0x4ff, port 0x1000-0x17ff
# include memory 0x80000000-0x80ffffff
# include port 0x1000-0x1fff
# include memory 0x90000000-0x90ffffff
include port 0x1000-0x8fff, port 0x9000-0x90ff
include memory 0x90000000-0x9ffff000, memory 0xf3000000-0xf33ff000
----
While booting I get this, not sure if this may be related:
...
Jan 2 15:51:56 charon kernel: PCI: Probing PCI hardware
Jan 2 15:51:56 charon kernel: Fixup res 1 (101) of dev 00:10.0: 400 -> 802400
Jan 2 15:51:56 charon kernel: Can't get bus-range for /[EMAIL
PROTECTED]/[EMAIL PROTECTED]
Jan 2 15:51:56 charon kernel: PCI->OF bus map:
Jan 2 15:51:56 charon kernel: 0 -> 0
Jan 2 15:51:56 charon kernel: 1 -> 0
Jan 2 15:51:56 charon kernel: 6 -> 0
Jan 2 15:51:56 charon kernel: PCI:00:10.0: Resource 0: b4000000-b7ffffff
(f=1208)
...
Note: the date is always one month in future after a restart:-( --
since the new kernel 2.4.16 or the last unstable update, I do not know
which was the cause, but this is a different topic.
looking for some help,
Percy
