> The PATA_PCMCIA driver does not work.
> The kernel version is 2.6.20.
> Does anyone test this driver?
Yes it gets regularly tested and works reliably on my test harware. I am
however using standards compliant hardware.
> [pata_pcmcia dmesg]
> ata1.00: CFA, max PIO0, 20480 sectors: LBA
> ata1.00: ata1: dev 0 multi count 0
> ata1.01: CFA, max PIO0, 20480 sectors: LBA
> ata1.01: ata1: dev 1 multi count 0
Do you have two cards here ?
> ata1.00: failed to set xfermode (err_mask=0x1)
This looks like you have both a CF adapter which does not properly handle
drive select, and a CFA card which incorrectly only allows a set
features/xfer mode to be done once.
The old IDE layer has a workaround to try and detect the former bug
(which sadly looks like it will be needed in libata), and through sheer
ignorance happens not to break in the second case.
Your card should work with the current -mm driver although not entirely
for the right reasons. Given you have such a marvellously buggy set of
hardware can I send you some test patches to try ?
Alan
On 2/11/07, Alan <[email protected]> wrote:
> > [pata_pcmcia dmesg]
> > ata1.00: CFA, max PIO0, 20480 sectors: LBA
> > ata1.00: ata1: dev 0 multi count 0
> > ata1.01: CFA, max PIO0, 20480 sectors: LBA
> > ata1.01: ata1: dev 1 multi count 0
>
> Do you have two cards here ?
I've seen this as well, on an ancient 4MB card. I'm pretty sure the
-CSEL signal on my test board is incorrectly routed, so I thought it
was because of that. I'll try to strap it tomorrow and see if it
really is the cause of the problem.
> Your card should work with the current -mm driver although not entirely
> for the right reasons. Given you have such a marvellously buggy set of
> hardware can I send you some test patches to try ?
In my current pile of four CF cards, it looks like three of them are
buggy, although in slightly different ways. I'd be happy to test a few
patches.
Haavard