16-bit PCMCIA resource allocation

[David Clark]

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 at chtech.com
 

-----Original Message-----
From: Asier Llano Palacios [mailto:a.llano at usyscom.com] 
Sent: Monday, February 19, 2007 2:58 AM
To: David Clark
Cc: linuxppc-embedded at ozlabs.org; 'Aitor Arzuaga'; 'Miguel Ángel Álvarez
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ó:
> 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 at chtech.com
>  
> 
> 
> 
 
----------------------------------------- PLEASE NOTE
-------------------------------------------
This message, along with any attachments, may be confidential or legally
privileged. 
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.
µSysCom uses virus scanning software but excludes any liability for
viruses contained in any attachment.
 
------------------------------------ ROGAMOS LEA ESTE TEXTO
-------------------------------
Este mensaje y sus anexos pueden contener información confidencial y/o
con derecho legal. 
Está dirigido únicamente a la/s persona/s o entidad/es reseñadas como
único destinatario autorizado.
Si este mensaje le hubiera llegado por error, por favor elimínelo sin
revisarlo ni reenviarlo y notifíquelo inmediatamente al remitente.
Gracias por su colaboración.  
µSysCom utiliza software antivirus, pero no se hace responsable de los
virus contenidos en los ficheros anexos.