From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: bzolnier@gmail.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ide: don't set PIO mode on pre-EIDE drives
Date: Fri, 16 Nov 2007 20:19:19 +0300 [thread overview]
Message-ID: <473DD117.1090808@ru.mvista.com> (raw)
In-Reply-To: <20071116165629.6ba73708@the-village.bc.nu>
Alan Cox wrote:
>>>>Fix handling of the PIO modes for the pre-EIDE drives that did not support
>>>>the PIO Flow Control Transfer Mode value (00001 nnn) of the Set Transfer Mode
>>>>feature by skipping the actual mode programming.
>>>You also need to cater for CF 1.1 compliant devices which do not have set
>>>xfer mode.
>> Do they have IORDY support?
> Good question.
I thought you know. :-)
> CF 1.4 says set features supports 01/0A/55/66/81/8A/9A/BB/CC
> (with 69/96/97 NOP or not recommended)
Well, the same spec says IORDY may be supported and bit 11 of word 49 may
be set. Obviously, no PIO3/4 though.
> However it documents both the PIO mode and DMA word in identify. I've
So what? That's PIO2 at max, and *default* mode at that, not changeable.
> never seen a CF 1.x card which does DMA or PIO > 2.
That's something at least. I hope they also don't set bit 11 --
otherwise, bad luck. Or am I supposed to also check the CF signature? :-)
> CF 1.x is sort of ATA-2 ish but without some set features (eg its got
> idle immediate) and with some stuff that became general later (security
> features)
Well, at least CF 2.1 documents every imaginable feature value, it seems,
including Set Transfer Mode of all flavors.
> Alan
MBR, Sergei
next prev parent reply other threads:[~2007-11-16 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 13:26 [PATCH] ide: don't set PIO mode on pre-EIDE drives Sergei Shtylyov
2007-11-16 16:42 ` Alan Cox
2007-11-16 16:45 ` Sergei Shtylyov
2007-11-16 16:56 ` Alan Cox
2007-11-16 17:19 ` Sergei Shtylyov [this message]
2007-11-16 18:14 ` Alan Cox
2007-11-16 21:35 ` Bartlomiej Zolnierkiewicz
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=473DD117.1090808@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.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).