PCI1620 with an integrated memory card reader

[Cristian Onet]

> Either ide-cs or pcmcia_pata. You could try the latter driver and see
> if it works better, it is the future after all.

I have tried also with pata_pcmcia the result is slightly different :) even the led blinks with a changed rithm.

# pccardctl ls
Socket 0 Bridge:        [yenta_cardbus]         (bus ID: 0000:02:04.0)
Socket 1 Bridge:        [yenta_cardbus]         (bus ID: 0000:02:04.1)
Socket 1 Device 0:      [pata_pcmcia]           (bus ID: 1.0)

From dmesg:

tiumfwl: 0000:02:04.2: firmware successfully loaded
pccard: PCMCIA card inserted into slot 1
cs: memory probe 0xe8200000-0xe82fffff: excluding 0xe8200000-0xe820ffff
pcmcia: registering new device pcmcia1.0
ata1: PATA max PIO0 cmd 0x0001a100 ctl 0x0001a10e bmdma 0x00000000 irq 3
scsi0 : pata_pcmcia
ATA: abnormal status 0x18 on port 0x0001a107
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x2)
ATA: abnormal status 0x18 on port 0x0001a107
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x2)
ata1.00: limiting speed to UDMA7:PIO5
ATA: abnormal status 0x18 on port 0x0001a107
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x2)

Maybe I should contact the author of ide_cs.c or pata_pcmcia.c.
I also checked the windows driver distribution and from what I understood there is no "special" driver for the card reader. There is only the firmware loader. Once the firmware is loaded it should provide an ATA interface to any inserted memory card or at least this is what I understood after studying the issue and this point of view is confirmed by from my experience so far (in windows upon detection of a memory card a certain "pcmcia_atapi" is used). This problem was already signaled at http://bugzilla.kernel.org/show_bug.cgi?id=6991 but, I do not know why, the developers blamed the firmware loader. From what I can tell the firmware loader works just fine because if it would not (which would mean that we have a bad firmware loaded) the machine would freeze upon insertion of a card (I know from experience). My question is: Is there a problem with the pata_pcmcia implementation or there should be a separate pata_pcmcia_pci1620 implementation that would handle only this deviece?