* 16-bit PCMCIA resource allocation
@ 2007-02-15 16:04 David Clark
2007-02-16 11:16 ` Asier Llano Palacios
2007-02-26 21:09 ` David Clark
0 siblings, 2 replies; 6+ messages in thread
From: David Clark @ 2007-02-15 16:04 UTC (permalink / raw)
To: linuxppc-embedded
I am having difficulty getting 16-bit PCMCIA cards to work on a custom
MPC8245-based board. I am running kernel 2.6.14.2 with pcmciautils-014.
I have successfully run the network off a 32-bit PCMCIA network card so
I am certain that the interface to the PCMCIA socket is functional. I'm
thinking it is just a resource allocation issue but I am having
difficulty understanding how it is supposed to work. When I insert the
card or call "pccardctl insert" I receive the error "cs: unable to map
card memory."
>From following the source I can tell that the error occurs when the
kernel is trying read the cards CIS and it fails to allocate/map memory
to do so. Do I need to tell the kernel to reserve a block of memory for
16-bit PCMCIA cards? I assume this would be from the PCI busses address
space. Is this done using the "/etc/pcmcia/config.opts" file? I was
under the impression that I didn't need this file for a Yenta socket in
a PPC environment. Could is be the way my PCIbus is setup? ...
Any hints are greatly appreciated.
David Clark
Below are a few relevant outputs.
******** pccardctl status ********
Socket 0:
5.0V 16-bit PC Card
******** dmesg ********
dmesg
oop registered
io scheduler deadline registered
RAMDISK driver initialized: 4 RAM disks of 32768K size 1024 blocksize
QS6612: Registered new driver
Linux Tulip driver version 1.1.13 (May 11, 2002)
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media 100baseTx (#3) described by a 21143 SYM PHY
(4) block.
tulip0: Index #1 - Media 100baseTx-FDX (#5) described by a 21143 SYM
PHY (4) bl
ock.
tulip0: Index #2 - Media 10baseT (#0) described by a 21142 Serial PHY
(2) block
.
tulip0: Index #3 - Media 10baseT-FDX (#4) described by a 21142 Serial
PHY (2) b
lock.
eth0: Digital DS21143 Tulip rev 65 at c9002c00, 00:40:42:07:00:04, IRQ
16.
Yenta: CardBus bridge found at 0000:00:14.0 [0000:0000]
PCI: Bus 2, cardbus bridge: 0000:00:14.0
IO window: 00000000-000001ff
IO window: 00000400-000005ff
PREFETCH window: bf8ff000-bfcfefff
MEM window: 80000000-803fffff
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:14.0, mfunc 0x00101000, devctl 0x66
Yenta TI: socket 0000:00:14.0 probing PCI interrupt failed, trying to
fix
Yenta TI: socket 0000:00:14.0 falling back to parallel PCI interrupts
Yenta TI: socket 0000:00:14.0 parallel PCI interrupts ok
Yenta: ISA IRQ mask 0x0000, PCI irq 19
Socket status: 30000410
pcmcia: parent PCI bridge I/O window: 0xfe000000 - 0xfebfffff
pcmcia: parent PCI bridge Memory window: 0x80000000 - 0xfcffffff
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
cs: memory probe 0x80000000-0xfcffffff:IP-Config: Complete:
device=eth0, addr=192.168.1.228, mask=255.255.255.0,
gw=255.255.255.255,
host=vx411c, domain=, nis-domain=(none),
bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 100k init
- nothing to change...
- nothing to change...
excluding 0x80000000-0xfcffffff
cs: unable to map card memory!
cs: unable to map card memory!
- nothing to change...
- data bits = 8
- parity = none
- stop bits = 1
- RTS/CTS is disabled
- baud rate = 57600<5>***CH DEBUG: s->callback->event() = 0xc0121b54
cs: unable to map card memory!
cs: unable to map card memory!
******** lspci -vvv ********
~ # lspci -vvv
00:00.0 Host bridge: Motorola MPC8245 [Unity] (rev 14)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort-
<MAbort+ >SERR- <PERR-
Latency: 64, Cache Line Size 08
Interrupt: pin A routed to IRQ 0
Region 0: Memory at <unassigned> (32-bit, prefetchable)
Region 2: Memory at <unassigned> (32-bit, prefetchable)
00:10.0 I2O: Anchor Chips Inc. AN3042Q CO-MEM Lite (rev 02) (prog-if 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 128, Cache Line Size 08
Interrupt: pin ? routed to IRQ 20
Region 0: Memory at 00000000bfff8000 (32-bit, non-prefetchable)
[size=32
K]
Region 1: I/O ports at bffff8 [size=8]
00:12.0 Ethernet controller: Digital Equipment Corporation DECchip
21142/43 (rev
41)
Subsystem: Unknown device 0400:0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 128 (5000ns min, 10000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at bfff00 [size=128]
Region 1: Memory at 00000000bfff7c00 (32-bit, non-prefetchable)
[size=1K
]
Expansion ROM at 00000000dfbc0000 [disabled] [size=256K]
00:13.0 PCI bridge: Texas Instruments PCI2250 PCI-to-PCI Bridge (rev 02)
(prog-i
f 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 128, Cache Line Size 08
Bus: primary=00, secondary=01, subordinate=01, sec-latency=128
I/O behind bridge: 00bfe000-00bfefff
Memory behind bridge: bfe00000-bfefffff
Prefetchable memory behind bridge: bfd00000-bfdfffff
Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:14.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller
(rev 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 168, Cache Line Size 08
Interrupt: pin A routed to IRQ 19
Region 0: Memory at 00000000bfcff000 (32-bit, non-prefetchable)
[size=4K
]
Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
Memory window 0: bf8ff000-bfcfe000 (prefetchable)
Memory window 1: 80000000-803ff000
I/O window 0: 00000000-000001ff
I/O window 1: 00000400-000005ff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
16-bit legacy interface ports at 0001
00:14.2 System peripheral: Texas Instruments PCI1620 Firmware Loading
Function (
rev 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 128 (1750ns min, 1000ns max), Cache Line Size 08
Interrupt: pin ? routed to IRQ 19
Region 0: I/O ports at bf9fc0 [size=64]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
******** lspcmcia -vvv ********
~ # lspcmcia -vvv
Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:00:14.0)
Configuration: state: suspended ready: yes
Voltage: 5.0V Vcc: 5.0V Vpp: 5.0V
Available IRQs: none
Available ioports: 0xfe000000 - 0xfebfffff
Available iomem: --none--
******** /proc/iomem ********
~ # cat /proc/iomem
80000000-fcffffff : PCI host bridge
80000000-803fffff : PCI CardBus #02
bf8ff000-bfcfefff : PCI CardBus #02
bfcff000-bfcfffff : 0000:00:14.0
bfcff000-bfcfffff : yenta_socket
bfd00000-bfdfffff : PCI Bus #01
bfe00000-bfefffff : PCI Bus #01
bfff7c00-bfff7fff : 0000:00:12.0
bfff7c00-bfff7fff : tulip
bfff8000-bfffffff : 0000:00:10.0
fc004500-fc004507 : serial
******** /proc/ioports ********
~ # cat /proc/ioports
fe000000-febfffff : PCI host bridge
fe000000-fe0001ff : PCI CardBus #02
fe000400-fe0005ff : PCI CardBus #02
febf9fc0-febf9fff : 0000:00:14.2
febfe000-febfefff : PCI Bus #01
febfff00-febfff7f : 0000:00:12.0
febfff00-febfff7f : tulip
febffff8-febfffff : 0000:00:10.0
~ #
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 16-bit PCMCIA resource allocation
2007-02-15 16:04 16-bit PCMCIA resource allocation David Clark
@ 2007-02-16 11:16 ` Asier Llano Palacios
2007-02-16 16:32 ` David Clark
2007-02-26 21:09 ` David Clark
1 sibling, 1 reply; 6+ messages in thread
From: Asier Llano Palacios @ 2007-02-16 11:16 UTC (permalink / raw)
To: David Clark
Cc: Miguel Ángel Álvarez Cabanes, Aitor Arzuaga,
linuxppc-embedded
I have exactly the same issue with a MPC5200-based board.
Working situations:
- kernel 2.6.10 with pcmcia-cs: Every card (cardbus and pcmcia).
- kernel 2.6.18 or 2.6.20 with pcmciautils-014: Some pcmcias do not
work.
We are investigating the reasons. We have tested the
same /etc/pcmcia/config.opts that we used with pcmcia-cs, but now
executed with pcmciautils-014 (pcmcia-socket-startup), and it writes the
files in /sys, but it doesn't seem to work at all.
We have 2 pcmcias that do not work, and another 2 that work. We have a
lot of cardbus and everyone works.
I'd like to keep in touch to share the results of the tests we are
performing in order to address this issue.
Asier Llano
El jue, 15-02-2007 a las 10:04 -0600, David Clark escribi=F3:
> I am having difficulty getting 16-bit PCMCIA cards to work on a custom
> MPC8245-based board. I am running kernel 2.6.14.2 with =
pcmciautils-014.
> I have successfully run the network off a 32-bit PCMCIA network card =
so
> I am certain that the interface to the PCMCIA socket is functional. =
I'm
> thinking it is just a resource allocation issue but I am having
> difficulty understanding how it is supposed to work. When I insert =
the
> card or call "pccardctl insert" I receive the error "cs: unable to map
> card memory."
>=20
> >From following the source I can tell that the error occurs when the
> kernel is trying read the cards CIS and it fails to allocate/map =
memory
> to do so. Do I need to tell the kernel to reserve a block of memory =
for
> 16-bit PCMCIA cards? I assume this would be from the PCI busses =
address
> space. Is this done using the "/etc/pcmcia/config.opts" file? I was
> under the impression that I didn't need this file for a Yenta socket =
in
> a PPC environment. Could is be the way my PCIbus is setup? ...
>=20
> Any hints are greatly appreciated.
>=20
> David Clark =20
>=20
> Below are a few relevant outputs.
>=20
> ******** pccardctl status ******** =20
> Socket 0:
> 5.0V 16-bit PC Card
>=20
> ******** dmesg ******** =20
> dmesg
> oop registered
> io scheduler deadline registered
> RAMDISK driver initialized: 4 RAM disks of 32768K size 1024 blocksize
> QS6612: Registered new driver
> Linux Tulip driver version 1.1.13 (May 11, 2002)
> tulip0: EEPROM default media type Autosense.
> tulip0: Index #0 - Media 100baseTx (#3) described by a 21143 SYM PHY
> (4) block.
> tulip0: Index #1 - Media 100baseTx-FDX (#5) described by a 21143 SYM
> PHY (4) bl
> ock.
> tulip0: Index #2 - Media 10baseT (#0) described by a 21142 Serial PHY
> (2) block
> .
> tulip0: Index #3 - Media 10baseT-FDX (#4) described by a 21142 Serial
> PHY (2) b
> lock.
> eth0: Digital DS21143 Tulip rev 65 at c9002c00, 00:40:42:07:00:04, IRQ
> 16.
> Yenta: CardBus bridge found at 0000:00:14.0 [0000:0000]
> PCI: Bus 2, cardbus bridge: 0000:00:14.0
> IO window: 00000000-000001ff
> IO window: 00000400-000005ff
> PREFETCH window: bf8ff000-bfcfefff
> MEM window: 80000000-803fffff
> Yenta: Enabling burst memory read transactions
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: socket 0000:00:14.0, mfunc 0x00101000, devctl 0x66
> Yenta TI: socket 0000:00:14.0 probing PCI interrupt failed, trying to
> fix
> Yenta TI: socket 0000:00:14.0 falling back to parallel PCI interrupts
> Yenta TI: socket 0000:00:14.0 parallel PCI interrupts ok
> Yenta: ISA IRQ mask 0x0000, PCI irq 19
> Socket status: 30000410
> pcmcia: parent PCI bridge I/O window: 0xfe000000 - 0xfebfffff
> pcmcia: parent PCI bridge Memory window: 0x80000000 - 0xfcffffff
> mice: PS/2 mouse device common for all mice
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
> TCP established hash table entries: 8192 (order: 3, 32768 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP reno registered
> TCP bic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> cs: memory probe 0x80000000-0xfcffffff:IP-Config: Complete:
> device=3Deth0, addr=3D192.168.1.228, mask=3D255.255.255.0,
> gw=3D255.255.255.255,
> host=3Dvx411c, domain=3D, nis-domain=3D(none),
> bootserver=3D255.255.255.255, rootserver=3D255.255.255.255, =
rootpath=3D
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 100k init
> - nothing to change...
> - nothing to change...
> excluding 0x80000000-0xfcffffff
> cs: unable to map card memory!
> cs: unable to map card memory!
> - nothing to change...
> - data bits =3D 8
> - parity =3D none
> - stop bits =3D 1
> - RTS/CTS is disabled
> - baud rate =3D 57600<5>***CH DEBUG: s->callback->event() =3D =
0xc0121b54
> cs: unable to map card memory!
> cs: unable to map card memory!
>=20
>=20
> ******** lspci -vvv ******** =20
> ~ # lspci -vvv
> 00:00.0 Host bridge: Motorola MPC8245 [Unity] (rev 14)
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Step
> ping- SERR- FastB2B-
> Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort-
> <TAbort-=20
> <MAbort+ >SERR- <PERR-
> Latency: 64, Cache Line Size 08
> Interrupt: pin A routed to IRQ 0
> Region 0: Memory at <unassigned> (32-bit, prefetchable)
> Region 2: Memory at <unassigned> (32-bit, prefetchable)
>=20
> 00:10.0 I2O: Anchor Chips Inc. AN3042Q CO-MEM Lite (rev 02) (prog-if =
01)
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Step
> ping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort-
> <TAbort
> - <MAbort- >SERR- <PERR-
> Latency: 128, Cache Line Size 08
> Interrupt: pin ? routed to IRQ 20
> Region 0: Memory at 00000000bfff8000 (32-bit, non-prefetchable)
> [size=3D32
> K]
> Region 1: I/O ports at bffff8 [size=3D8]
>=20
> 00:12.0 Ethernet controller: Digital Equipment Corporation DECchip
> 21142/43 (rev
> 41)
> Subsystem: Unknown device 0400:0001
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Step
> ping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort-
> <TAbort
> - <MAbort- >SERR- <PERR-
> Latency: 128 (5000ns min, 10000ns max), Cache Line Size 08
> Interrupt: pin A routed to IRQ 16
> Region 0: I/O ports at bfff00 [size=3D128]
> Region 1: Memory at 00000000bfff7c00 (32-bit, non-prefetchable)
> [size=3D1K
> ]
> Expansion ROM at 00000000dfbc0000 [disabled] [size=3D256K]
>=20
> 00:13.0 PCI bridge: Texas Instruments PCI2250 PCI-to-PCI Bridge (rev =
02)
> (prog-i
> f 00 [Normal decode])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Step
> ping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort-
> <TAbort
> - <MAbort- >SERR- <PERR-
> Latency: 128, Cache Line Size 08
> Bus: primary=3D00, secondary=3D01, subordinate=3D01, =
sec-latency=3D128
> I/O behind bridge: 00bfe000-00bfefff
> Memory behind bridge: bfe00000-bfefffff
> Prefetchable memory behind bridge: bfd00000-bfdfffff
> Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort-
> <TAbort
> - <MAbort+ <SERR- <PERR-
> BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
> Capabilities: [dc] Power Management version 1
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=3D0mA
> PME(D0-,D1-,D2-,D3hot
> -,D3cold-)
> Status: D0 PME-Enable- DSel=3D0 DScale=3D0 PME-
>=20
> 00:14.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller
> (rev 01)
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Step
> ping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort-
> <TAbort
> - <MAbort- >SERR- <PERR-
> Latency: 168, Cache Line Size 08
> Interrupt: pin A routed to IRQ 19
> Region 0: Memory at 00000000bfcff000 (32-bit, non-prefetchable)
> [size=3D4K
> ]
> Bus: primary=3D00, secondary=3D02, subordinate=3D05, =
sec-latency=3D176
> Memory window 0: bf8ff000-bfcfe000 (prefetchable)
> Memory window 1: 80000000-803ff000
> I/O window 0: 00000000-000001ff
> I/O window 1: 00000400-000005ff
> BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
> PostWrite+
> 16-bit legacy interface ports at 0001
>=20
> 00:14.2 System peripheral: Texas Instruments PCI1620 Firmware Loading
> Function (
> rev 01)
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Step
> ping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort-
> <TAbort
> - <MAbort- >SERR- <PERR-
> Latency: 128 (1750ns min, 1000ns max), Cache Line Size 08
> Interrupt: pin ? routed to IRQ 19
> Region 0: I/O ports at bf9fc0 [size=3D64]
> Capabilities: [44] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=3D0mA
> PME(D0-,D1-,D2-,D3hot
> -,D3cold-)
> Status: D0 PME-Enable- DSel=3D0 DScale=3D0 PME-
>=20
>=20
> ******** lspcmcia -vvv ******** =20
> ~ # lspcmcia -vvv
> Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:00:14.0)
> Configuration: state: suspended ready: yes
> Voltage: 5.0V Vcc: 5.0V Vpp: 5.0V
> Available IRQs: none
> Available ioports: 0xfe000000 - 0xfebfffff
> Available iomem: --none--
>=20
>=20
> ******** /proc/iomem ******** =20
> ~ # cat /proc/iomem
> 80000000-fcffffff : PCI host bridge
> 80000000-803fffff : PCI CardBus #02
> bf8ff000-bfcfefff : PCI CardBus #02
> bfcff000-bfcfffff : 0000:00:14.0
> bfcff000-bfcfffff : yenta_socket
> bfd00000-bfdfffff : PCI Bus #01
> bfe00000-bfefffff : PCI Bus #01
> bfff7c00-bfff7fff : 0000:00:12.0
> bfff7c00-bfff7fff : tulip
> bfff8000-bfffffff : 0000:00:10.0
> fc004500-fc004507 : serial
>=20
>=20
> ******** /proc/ioports ******** =20
> ~ # cat /proc/ioports
> fe000000-febfffff : PCI host bridge
> fe000000-fe0001ff : PCI CardBus #02
> fe000400-fe0005ff : PCI CardBus #02
> febf9fc0-febf9fff : 0000:00:14.2
> febfe000-febfefff : PCI Bus #01
> febfff00-febfff7f : 0000:00:12.0
> febfff00-febfff7f : tulip
> febffff8-febfffff : 0000:00:10.0
> ~ #
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded=20
=20
----------------------------------------- PLEASE NOTE =
-------------------------------------------
This message, along with any attachments, may be confidential or legally =
privileged.=20
It is intended only for the named person(s), who is/are the only =
authorized recipients.
If this message has reached you in error, kindly destroy it without =
review and notify the sender immediately.
Thank you for your help.
=B5SysCom uses virus scanning software but excludes any liability for =
viruses contained in any attachment.
=20
------------------------------------ ROGAMOS LEA ESTE TEXTO =
-------------------------------
Este mensaje y sus anexos pueden contener informaci=F3n confidencial y/o =
con derecho legal.=20
Est=E1 dirigido =FAnicamente a la/s persona/s o entidad/es rese=F1adas =
como =FAnico destinatario autorizado.
Si este mensaje le hubiera llegado por error, por favor elim=EDnelo sin =
revisarlo ni reenviarlo y notif=EDquelo inmediatamente al remitente. =
Gracias por su colaboraci=F3n. =20
=B5SysCom utiliza software antivirus, pero no se hace responsable de los =
virus contenidos en los ficheros anexos.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: 16-bit PCMCIA resource allocation
2007-02-16 11:16 ` Asier Llano Palacios
@ 2007-02-16 16:32 ` David Clark
2007-02-19 8:58 ` Asier Llano Palacios
0 siblings, 1 reply; 6+ messages in thread
From: David Clark @ 2007-02-16 16:32 UTC (permalink / raw)
To: a.llano
Cc: 'Miguel Ángel Álvarez Cabanes',
'Aitor Arzuaga', linuxppc-embedded
Asier,
Do you get the following message or similar during boot (dmesg output)?
"cs: memory probe 0x80000000-0xfcffffff:"
" excluding 0x80000000-0xfcffffff"
Note: in my dmesg output these where not on consecutive lines.
David Clark
Senior Software Engineer
C&H Technologies, Inc
Web: http:\\www.chtech.com
Phone: 512-733-2621
Fax: 512-733-2629
Email: dlclark@chtech.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: 16-bit PCMCIA resource allocation
2007-02-16 16:32 ` David Clark
@ 2007-02-19 8:58 ` Asier Llano Palacios
2007-02-26 21:07 ` David Clark
0 siblings, 1 reply; 6+ messages in thread
From: Asier Llano Palacios @ 2007-02-19 8:58 UTC (permalink / raw)
To: David Clark
Cc: 'Miguel Ángel Álvarez Cabanes',
'Aitor Arzuaga', linuxppc-embedded
I have the following lines:
PCI: Bus 1, cardbus bridge: 0000:00:18.0
IO window: 00001000-000011ff
IO window: 00001400-000015ff
PREFETCH window: 80000000-803fffff
MEM window: a0400000-a07fffff
Yenta: ISA IRQ mask 0x0000, PCI irq 1
Socket status: 30000410
pcmcia: parent PCI bridge I/O window: 0x0 - 0xffffff
pcmcia: parent PCI bridge Memory window: 0x80000000 - 0x9fffffff
pcmcia: parent PCI bridge Memory window: 0xa0000000 - 0xafffffff
...
...
pccard: PCMCIA card inserted into slot 0
cs: memory probe 0x80000000-0x9fffffff: excluding 0x80000000-0x9fffffff
cs: memory probe 0xa0000000-0xafffffff: excluding 0xa0000000-0xa07fffff
In fact the assigned resources are (the important one is the
pcmcia_socket0):
# cat /proc/iomem
80000000-9fffffff : PCI prefetchable memory
80000000-803fffff : PCI CardBus #01
a0000000-afffffff : PCI memory
a0000000-a0000fff : 0000:00:18.0
a0000000-a0000fff : yenta_socket
a0040000-a007ffff : 0000:00:1a.0
a0400000-a07fffff : PCI CardBus #01
a0800000-a0800fff : pcmcia_socket0
f0000900-f000097f : mpc52xx-mscan.0
f0000980-f00009ff : mpc52xx-mscan.1
f0000f00-f0000f1f : mpc52xx-spi
f0001000-f00010ff : ppc-soc-ohci
f0001200-f00012ff : mpc52xx-sdma
f0001200-f00012ff : mpc52xx-sdma
f0001300-f000130f : mpc52xx-bdlc
f0002000-f000209f : mpc52xx-psc.0
f0002000-f000209f : mpc52xx_psc_uart
f0002200-f000229f : mpc52xx-psc.1
f0002400-f000249f : mpc52xx-psc.2
f0002400-f000249f : mpc52xx_psc_uart
f0002600-f000269f : mpc52xx-psc.3
f0002600-f000269f : mpc52xx_psc_uart
f0002800-f000289f : mpc52xx-psc.4
f0002c00-f0002c9f : mpc52xx-psc.5
f0003000-f00033ff : mpc52xx-fec
f0003000-f00033ff : mpc52xx-fec
f0003a00-f0003aff : mpc52xx-ata
f0003d00-f0003d1f : fsl-i2c.0
f0003d40-f0003d5f : fsl-i2c.1
f0008000-f000bfff : mpc52xx-sdma
f0008000-f000bfff : mpc52xx-sdma
ff800000-ffffffff : physmap-flash.0
ff800000-ffffffff : physmap-flash.0
# cat /proc/ioports
00000000-00ffffff : PCI I/O
00000000-0000003f : pcmcia_socket0
00001000-000011ff : PCI CardBus #01
00001400-000015ff : PCI CardBus #01
That are not equal to the resources that were used by linux kernel
2.6.10:
~ # cat /proc/iomem
80000000-9fffffff : PCI prefetchable memory
80000000-803fffff : PCI CardBus #01
a0000000-afffffff : PCI memory
a0000000-a0000fff : 0000:00:18.0
a0000000-a0000fff : yenta_socket
a0040000-a007ffff : 0000:00:1a.0
a0100000-a0100fff : pcmcia_socket0
a0400000-a07fffff : PCI CardBus #01
f0002000-f000209f : mpc52xx_psc_uart
f0002400-f000249f : mpc52xx_psc_uart
f0002600-f000269f : mpc52xx_psc_uart
f0003000-f00033fb : mpc52xx_fec
f0003d00-f0003d1f : i2c-mpc
f0003d40-f0003d5f : i2c-mpc
~ # cat /proc/ioports
00000000-00ffffff : PCI I/O
00000100-0000013f : pcmcia_socket0
00001000-000010ff : PCI CardBus #01
00001400-000014ff : PCI CardBus #01
Maybe a better understanding of the resource allocation mechanism is
needed in order to know if the differences are important, or if it
should work also with this resource allocation table.
Thank you,
Asier Llano
El vie, 16-02-2007 a las 10:32 -0600, David Clark escribi=F3:
> Asier,
>=20
> Do you get the following message or similar during boot (dmesg =
output)?
>=20
> "cs: memory probe 0x80000000-0xfcffffff:"
> " excluding 0x80000000-0xfcffffff"
>=20
> Note: in my dmesg output these where not on consecutive lines.
>=20
> David Clark
> Senior Software Engineer
> C&H Technologies, Inc
> Web: http:\\www.chtech.com
> Phone: 512-733-2621
> Fax: 512-733-2629
> Email: dlclark@chtech.com
> =20
>=20
>=20
>=20
=20
----------------------------------------- PLEASE NOTE =
-------------------------------------------
This message, along with any attachments, may be confidential or legally =
privileged.=20
It is intended only for the named person(s), who is/are the only =
authorized recipients.
If this message has reached you in error, kindly destroy it without =
review and notify the sender immediately.
Thank you for your help.
=B5SysCom uses virus scanning software but excludes any liability for =
viruses contained in any attachment.
=20
------------------------------------ ROGAMOS LEA ESTE TEXTO =
-------------------------------
Este mensaje y sus anexos pueden contener informaci=F3n confidencial y/o =
con derecho legal.=20
Est=E1 dirigido =FAnicamente a la/s persona/s o entidad/es rese=F1adas =
como =FAnico destinatario autorizado.
Si este mensaje le hubiera llegado por error, por favor elim=EDnelo sin =
revisarlo ni reenviarlo y notif=EDquelo inmediatamente al remitente. =
Gracias por su colaboraci=F3n. =20
=B5SysCom utiliza software antivirus, pero no se hace responsable de los =
virus contenidos en los ficheros anexos.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: 16-bit PCMCIA resource allocation
2007-02-19 8:58 ` Asier Llano Palacios
@ 2007-02-26 21:07 ` David Clark
0 siblings, 0 replies; 6+ messages in thread
From: David Clark @ 2007-02-26 21:07 UTC (permalink / raw)
To: a.llano
Cc: 'Miguel Ángel Álvarez Cabanes',
'Aitor Arzuaga', linuxppc-embedded
Asier,
Our problem ended up being a hardware problem. We made a mistake when
designing the PCB. It is not likely that your issues are the same as
ours.
I wish you luck.
David Clark
Senior Software Engineer
C&H Technologies, Inc
Web: http:\\www.chtech.com
Phone: 512-733-2621
Fax: 512-733-2629
Email: dlclark@chtech.com
=20
-----Original Message-----
From: Asier Llano Palacios [mailto:a.llano@usyscom.com]=20
Sent: Monday, February 19, 2007 2:58 AM
To: David Clark
Cc: linuxppc-embedded@ozlabs.org; 'Aitor Arzuaga'; 'Miguel =C1ngel =
=C1lvarez
Cabanes'
Subject: RE: 16-bit PCMCIA resource allocation
I have the following lines:
PCI: Bus 1, cardbus bridge: 0000:00:18.0
IO window: 00001000-000011ff
IO window: 00001400-000015ff
PREFETCH window: 80000000-803fffff
MEM window: a0400000-a07fffff
Yenta: ISA IRQ mask 0x0000, PCI irq 1
Socket status: 30000410
pcmcia: parent PCI bridge I/O window: 0x0 - 0xffffff
pcmcia: parent PCI bridge Memory window: 0x80000000 - 0x9fffffff
pcmcia: parent PCI bridge Memory window: 0xa0000000 - 0xafffffff
...
...
pccard: PCMCIA card inserted into slot 0
cs: memory probe 0x80000000-0x9fffffff: excluding 0x80000000-0x9fffffff
cs: memory probe 0xa0000000-0xafffffff: excluding 0xa0000000-0xa07fffff
In fact the assigned resources are (the important one is the
pcmcia_socket0):
# cat /proc/iomem
80000000-9fffffff : PCI prefetchable memory
80000000-803fffff : PCI CardBus #01
a0000000-afffffff : PCI memory
a0000000-a0000fff : 0000:00:18.0
a0000000-a0000fff : yenta_socket
a0040000-a007ffff : 0000:00:1a.0
a0400000-a07fffff : PCI CardBus #01
a0800000-a0800fff : pcmcia_socket0
f0000900-f000097f : mpc52xx-mscan.0
f0000980-f00009ff : mpc52xx-mscan.1
f0000f00-f0000f1f : mpc52xx-spi
f0001000-f00010ff : ppc-soc-ohci
f0001200-f00012ff : mpc52xx-sdma
f0001200-f00012ff : mpc52xx-sdma
f0001300-f000130f : mpc52xx-bdlc
f0002000-f000209f : mpc52xx-psc.0
f0002000-f000209f : mpc52xx_psc_uart
f0002200-f000229f : mpc52xx-psc.1
f0002400-f000249f : mpc52xx-psc.2
f0002400-f000249f : mpc52xx_psc_uart
f0002600-f000269f : mpc52xx-psc.3
f0002600-f000269f : mpc52xx_psc_uart
f0002800-f000289f : mpc52xx-psc.4
f0002c00-f0002c9f : mpc52xx-psc.5
f0003000-f00033ff : mpc52xx-fec
f0003000-f00033ff : mpc52xx-fec
f0003a00-f0003aff : mpc52xx-ata
f0003d00-f0003d1f : fsl-i2c.0
f0003d40-f0003d5f : fsl-i2c.1
f0008000-f000bfff : mpc52xx-sdma
f0008000-f000bfff : mpc52xx-sdma
ff800000-ffffffff : physmap-flash.0
ff800000-ffffffff : physmap-flash.0
# cat /proc/ioports
00000000-00ffffff : PCI I/O
00000000-0000003f : pcmcia_socket0
00001000-000011ff : PCI CardBus #01
00001400-000015ff : PCI CardBus #01
That are not equal to the resources that were used by linux kernel
2.6.10:
~ # cat /proc/iomem
80000000-9fffffff : PCI prefetchable memory
80000000-803fffff : PCI CardBus #01
a0000000-afffffff : PCI memory
a0000000-a0000fff : 0000:00:18.0
a0000000-a0000fff : yenta_socket
a0040000-a007ffff : 0000:00:1a.0
a0100000-a0100fff : pcmcia_socket0
a0400000-a07fffff : PCI CardBus #01
f0002000-f000209f : mpc52xx_psc_uart
f0002400-f000249f : mpc52xx_psc_uart
f0002600-f000269f : mpc52xx_psc_uart
f0003000-f00033fb : mpc52xx_fec
f0003d00-f0003d1f : i2c-mpc
f0003d40-f0003d5f : i2c-mpc
~ # cat /proc/ioports
00000000-00ffffff : PCI I/O
00000100-0000013f : pcmcia_socket0
00001000-000010ff : PCI CardBus #01
00001400-000014ff : PCI CardBus #01
Maybe a better understanding of the resource allocation mechanism is
needed in order to know if the differences are important, or if it
should work also with this resource allocation table.
Thank you,
Asier Llano
El vie, 16-02-2007 a las 10:32 -0600, David Clark escribi=F3:
> Asier,
>=20
> Do you get the following message or similar during boot (dmesg
output)?
>=20
> "cs: memory probe 0x80000000-0xfcffffff:"
> " excluding 0x80000000-0xfcffffff"
>=20
> Note: in my dmesg output these where not on consecutive lines.
>=20
> David Clark
> Senior Software Engineer
> C&H Technologies, Inc
> Web: http:\\www.chtech.com
> Phone: 512-733-2621
> Fax: 512-733-2629
> Email: dlclark@chtech.com
> =20
>=20
>=20
>=20
=20
----------------------------------------- PLEASE NOTE
-------------------------------------------
This message, along with any attachments, may be confidential or legally
privileged.=20
It is intended only for the named person(s), who is/are the only
authorized recipients.
If this message has reached you in error, kindly destroy it without
review and notify the sender immediately.
Thank you for your help.
=B5SysCom uses virus scanning software but excludes any liability for
viruses contained in any attachment.
=20
------------------------------------ ROGAMOS LEA ESTE TEXTO
-------------------------------
Este mensaje y sus anexos pueden contener informaci=F3n confidencial y/o
con derecho legal.=20
Est=E1 dirigido =FAnicamente a la/s persona/s o entidad/es rese=F1adas =
como
=FAnico destinatario autorizado.
Si este mensaje le hubiera llegado por error, por favor elim=EDnelo sin
revisarlo ni reenviarlo y notif=EDquelo inmediatamente al remitente.
Gracias por su colaboraci=F3n. =20
=B5SysCom utiliza software antivirus, pero no se hace responsable de los
virus contenidos en los ficheros anexos.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: 16-bit PCMCIA resource allocation
2007-02-15 16:04 16-bit PCMCIA resource allocation David Clark
2007-02-16 11:16 ` Asier Llano Palacios
@ 2007-02-26 21:09 ` David Clark
1 sibling, 0 replies; 6+ messages in thread
From: David Clark @ 2007-02-26 21:09 UTC (permalink / raw)
To: linuxppc-embedded
This issue turned out to be a PCB design problem. Thank you for your
assistance.
David Clark
Senior Software Engineer
C&H Technologies, Inc
Web: http:\\www.chtech.com
Phone: 512-733-2621
Fax: 512-733-2629
Email: dlclark@chtech.com
-----Original Message-----
From: linuxppc-embedded-bounces+dlclark=chtech.com@ozlabs.org
[mailto:linuxppc-embedded-bounces+dlclark=chtech.com@ozlabs.org] On
Behalf Of David Clark
Sent: Thursday, February 15, 2007 10:04 AM
To: linuxppc-embedded@ozlabs.org
Subject: 16-bit PCMCIA resource allocation
I am having difficulty getting 16-bit PCMCIA cards to work on a custom
MPC8245-based board. I am running kernel 2.6.14.2 with pcmciautils-014.
I have successfully run the network off a 32-bit PCMCIA network card so
I am certain that the interface to the PCMCIA socket is functional. I'm
thinking it is just a resource allocation issue but I am having
difficulty understanding how it is supposed to work. When I insert the
card or call "pccardctl insert" I receive the error "cs: unable to map
card memory."
>From following the source I can tell that the error occurs when the
kernel is trying read the cards CIS and it fails to allocate/map memory
to do so. Do I need to tell the kernel to reserve a block of memory for
16-bit PCMCIA cards? I assume this would be from the PCI busses address
space. Is this done using the "/etc/pcmcia/config.opts" file? I was
under the impression that I didn't need this file for a Yenta socket in
a PPC environment. Could is be the way my PCIbus is setup? ...
Any hints are greatly appreciated.
David Clark
Below are a few relevant outputs.
******** pccardctl status ********
Socket 0:
5.0V 16-bit PC Card
******** dmesg ********
dmesg
oop registered
io scheduler deadline registered
RAMDISK driver initialized: 4 RAM disks of 32768K size 1024 blocksize
QS6612: Registered new driver
Linux Tulip driver version 1.1.13 (May 11, 2002)
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media 100baseTx (#3) described by a 21143 SYM PHY
(4) block.
tulip0: Index #1 - Media 100baseTx-FDX (#5) described by a 21143 SYM
PHY (4) bl
ock.
tulip0: Index #2 - Media 10baseT (#0) described by a 21142 Serial PHY
(2) block
..
tulip0: Index #3 - Media 10baseT-FDX (#4) described by a 21142 Serial
PHY (2) b
lock.
eth0: Digital DS21143 Tulip rev 65 at c9002c00, 00:40:42:07:00:04, IRQ
16.
Yenta: CardBus bridge found at 0000:00:14.0 [0000:0000]
PCI: Bus 2, cardbus bridge: 0000:00:14.0
IO window: 00000000-000001ff
IO window: 00000400-000005ff
PREFETCH window: bf8ff000-bfcfefff
MEM window: 80000000-803fffff
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:14.0, mfunc 0x00101000, devctl 0x66
Yenta TI: socket 0000:00:14.0 probing PCI interrupt failed, trying to
fix
Yenta TI: socket 0000:00:14.0 falling back to parallel PCI interrupts
Yenta TI: socket 0000:00:14.0 parallel PCI interrupts ok
Yenta: ISA IRQ mask 0x0000, PCI irq 19
Socket status: 30000410
pcmcia: parent PCI bridge I/O window: 0xfe000000 - 0xfebfffff
pcmcia: parent PCI bridge Memory window: 0x80000000 - 0xfcffffff
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
cs: memory probe 0x80000000-0xfcffffff:IP-Config: Complete:
device=eth0, addr=192.168.1.228, mask=255.255.255.0,
gw=255.255.255.255,
host=vx411c, domain=, nis-domain=(none),
bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 100k init
- nothing to change...
- nothing to change...
excluding 0x80000000-0xfcffffff
cs: unable to map card memory!
cs: unable to map card memory!
- nothing to change...
- data bits = 8
- parity = none
- stop bits = 1
- RTS/CTS is disabled
- baud rate = 57600<5>***CH DEBUG: s->callback->event() = 0xc0121b54
cs: unable to map card memory!
cs: unable to map card memory!
******** lspci -vvv ********
~ # lspci -vvv
00:00.0 Host bridge: Motorola MPC8245 [Unity] (rev 14)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort-
<MAbort+ >SERR- <PERR-
Latency: 64, Cache Line Size 08
Interrupt: pin A routed to IRQ 0
Region 0: Memory at <unassigned> (32-bit, prefetchable)
Region 2: Memory at <unassigned> (32-bit, prefetchable)
00:10.0 I2O: Anchor Chips Inc. AN3042Q CO-MEM Lite (rev 02) (prog-if 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 128, Cache Line Size 08
Interrupt: pin ? routed to IRQ 20
Region 0: Memory at 00000000bfff8000 (32-bit, non-prefetchable)
[size=32
K]
Region 1: I/O ports at bffff8 [size=8]
00:12.0 Ethernet controller: Digital Equipment Corporation DECchip
21142/43 (rev
41)
Subsystem: Unknown device 0400:0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 128 (5000ns min, 10000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at bfff00 [size=128]
Region 1: Memory at 00000000bfff7c00 (32-bit, non-prefetchable)
[size=1K
]
Expansion ROM at 00000000dfbc0000 [disabled] [size=256K]
00:13.0 PCI bridge: Texas Instruments PCI2250 PCI-to-PCI Bridge (rev 02)
(prog-i
f 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 128, Cache Line Size 08
Bus: primary=00, secondary=01, subordinate=01, sec-latency=128
I/O behind bridge: 00bfe000-00bfefff
Memory behind bridge: bfe00000-bfefffff
Prefetchable memory behind bridge: bfd00000-bfdfffff
Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:14.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller
(rev 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 168, Cache Line Size 08
Interrupt: pin A routed to IRQ 19
Region 0: Memory at 00000000bfcff000 (32-bit, non-prefetchable)
[size=4K
]
Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
Memory window 0: bf8ff000-bfcfe000 (prefetchable)
Memory window 1: 80000000-803ff000
I/O window 0: 00000000-000001ff
I/O window 1: 00000400-000005ff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
16-bit legacy interface ports at 0001
00:14.2 System peripheral: Texas Instruments PCI1620 Firmware Loading
Function (
rev 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 128 (1750ns min, 1000ns max), Cache Line Size 08
Interrupt: pin ? routed to IRQ 19
Region 0: I/O ports at bf9fc0 [size=64]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
******** lspcmcia -vvv ********
~ # lspcmcia -vvv
Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:00:14.0)
Configuration: state: suspended ready: yes
Voltage: 5.0V Vcc: 5.0V Vpp: 5.0V
Available IRQs: none
Available ioports: 0xfe000000 - 0xfebfffff
Available iomem: --none--
******** /proc/iomem ********
~ # cat /proc/iomem
80000000-fcffffff : PCI host bridge
80000000-803fffff : PCI CardBus #02
bf8ff000-bfcfefff : PCI CardBus #02
bfcff000-bfcfffff : 0000:00:14.0
bfcff000-bfcfffff : yenta_socket
bfd00000-bfdfffff : PCI Bus #01
bfe00000-bfefffff : PCI Bus #01
bfff7c00-bfff7fff : 0000:00:12.0
bfff7c00-bfff7fff : tulip
bfff8000-bfffffff : 0000:00:10.0
fc004500-fc004507 : serial
******** /proc/ioports ********
~ # cat /proc/ioports
fe000000-febfffff : PCI host bridge
fe000000-fe0001ff : PCI CardBus #02
fe000400-fe0005ff : PCI CardBus #02
febf9fc0-febf9fff : 0000:00:14.2
febfe000-febfefff : PCI Bus #01
febfff00-febfff7f : 0000:00:12.0
febfff00-febfff7f : tulip
febffff8-febfffff : 0000:00:10.0
~ #
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-02-26 21:09 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-15 16:04 16-bit PCMCIA resource allocation David Clark
2007-02-16 11:16 ` Asier Llano Palacios
2007-02-16 16:32 ` David Clark
2007-02-19 8:58 ` Asier Llano Palacios
2007-02-26 21:07 ` David Clark
2007-02-26 21:09 ` David Clark
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).