From: Robert Hancock <hancockr@shaw.ca>
To: Zan Lynx <zlynx@acm.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-pcmcia@lists.infradead.org,
linux-ide@vger.kernel.org
Subject: Re: 2.6.24-rc4-mm1 and Very Slow PCMCIA Compact Flash
Date: Fri, 07 Dec 2007 22:47:57 -0600 [thread overview]
Message-ID: <475A21FD.6020009@shaw.ca> (raw)
In-Reply-To: <fa.5knWxRyOEvQSAwZoz5fEa2Krvko@ifi.uio.no>
Zan Lynx wrote:
> On Fri, 2007-12-07 at 15:22 -0800, Andrew Morton wrote:
>> On Fri, 07 Dec 2007 23:09:43 +0000
>> Zan Lynx <zlynx@acm.org> wrote:
>>
>>> On Fri, 2007-12-07 at 15:02 -0800, Andrew Morton wrote:
>>>> On Fri, 07 Dec 2007 20:38:24 +0000
>>>> Zan Lynx <zlynx@acm.org> wrote:
>>>>
>>>>> While I'm reporting problems I'll get this one out there.
>>>>>
>>>>> I normally use a USB-2 memory card reader but I also have a PCMCIA
>>>>> CompactFlash adapter that I use occasionally. During the MM series
>>>>> kernels 2.6.22 and 23 (I am pretty sure) this didn't work at all. I
>>>>> don't know about vanilla since I don't run that.
>>>>>
>>>>> Now with MM kernels 2.6.24 rc1-4 the PCMCIA adapter works again, but I
>>>>> only get read rates of 1.6 MB/s. When it used to work in 2.6.20 I got
>>>>> at least 16 MB/s. The card itself is capable of 30+ in the USB-2
>>>>> reader.
>>>>>
> [cut]
>> Oh, OK. Hopefully the ata guys can help out with this.
>>
>> I don't know if it actually strictly a regression? Did libata ever support
>> that device in any earlier kernels?
>
> That could be why it didn't work for a few kernel versions. I
> reconfigured for a libata-only system a while back. And, since I
> usually use the USB-2 flash reader I didn't care much about the PCMCIA.
>
> I will try reverting that patch later tonight, in a few hours.
It looks like pata_pcmcia is always PIO mode 0:
/**
* pcmcia_init_one - attach a PCMCIA interface
* @pdev: pcmcia device
*
* Register a PCMCIA IDE interface. Such interfaces are PIO 0 and
* shared IRQ.
*/
I assume that with old IDE this would use ide_cs.c, but I'm drawing a
blank on what modes that supports..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-12-08 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.9+cyQSoHqcg4p5BAdLi4beGvJ8E@ifi.uio.no>
[not found] ` <fa.es7DHARPOKbnzAqaEFBauYRpWjo@ifi.uio.no>
[not found] ` <fa.kwN53ZHLrpa2M5QIn+VR9hoaqjA@ifi.uio.no>
[not found] ` <fa.IgSJMFcov+qjLkhPpd1LhbCf93o@ifi.uio.no>
[not found] ` <fa.5knWxRyOEvQSAwZoz5fEa2Krvko@ifi.uio.no>
2007-12-08 4:47 ` Robert Hancock [this message]
[not found] <1197059904.15428.15.camel@localhost>
[not found] ` <20071207150251.a0dbae23.akpm@linux-foundation.org>
[not found] ` <1197068983.15428.29.camel@localhost>
2007-12-07 23:22 ` 2.6.24-rc4-mm1 and Very Slow PCMCIA Compact Flash Andrew Morton
2007-12-07 23:39 ` Zan Lynx
2007-12-08 5:01 ` Zan Lynx
2007-12-08 10:07 ` Andrew Morton
2007-12-09 3:02 ` Zan Lynx
2007-12-09 4:04 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=475A21FD.6020009@shaw.ca \
--to=hancockr@shaw.ca \
--cc=akpm@linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=zlynx@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).